I've searched high low and sideways for a discussion on this issue and, having found none, am hoping users well versed in networking can help.
Simple description: we have a "web edition" program (TimeClocks Plus) that under Boot Camp we can access:
1) within the local network (so employees can post their work times) by addressing the (iMac Intel) machine directly in most any browser (i.e., 192.168.xx.xxx/tcpwebedition);
or 2) externally by addressing the machine and program again through any browser by entering the router's ISP-given ip address and (router assigned) port number (i.e.,
27.132.xxx.xxx:80/tcpwebedition). This is important: It took a simple port assignment on the router, but that those port assignments only use the 192.168.xx.xxx local network series of addresses..
As I said, if the machine is in Boot Camp, no access problems. That's not the case in Parallels. We use that Boot Camp partition under Parallels and everything else works fine; but trying to access that web program under Parallels results in networking issues I just don't know how to handle.
One advantage Boot Camp has is that it uses the Intel iMac's router assigned local address -- so we can use the same 192.168.xx.xxx number to access the machine whether it is in Mac OSX or Windows (Boot Camp) mode.
Parallels introduces NAT addressing, however, and a different local network assignment (10.xxx.xx.xxx). I have tried all avenues I can think of to access the program in Parallels.
If I manually assign (through TCP/IP in the Windows Control Panel) the same 192.168.xx.xxx number to the parallels Windows machine that works in Boot Camp, the system complains that number already exists and is in use; if I give it a unique number (but still using the 192.168.xx.xxx set-up), it is invisible externally, even if I assign that unique number to a port. I've tried DHCP'ing under the Windows TCP/IP, but then it seems to adopt the 10.xxx.xx.xxx series of numbers, which the router can't address. Etc Etc Etc.
I've tried to keep this bare-bones but would gladly expand on my attempts should anyone have some suggestions.
Again, simply put, we are trying to access that Web program (Timeclocks Plus) via a browser address both on the local network and externally when that program is runninng in Windows under Parallels.
Thanks for your attention.
-- samlhall
Simple description: we have a "web edition" program (TimeClocks Plus) that under Boot Camp we can access:
1) within the local network (so employees can post their work times) by addressing the (iMac Intel) machine directly in most any browser (i.e., 192.168.xx.xxx/tcpwebedition);
or 2) externally by addressing the machine and program again through any browser by entering the router's ISP-given ip address and (router assigned) port number (i.e.,
27.132.xxx.xxx:80/tcpwebedition). This is important: It took a simple port assignment on the router, but that those port assignments only use the 192.168.xx.xxx local network series of addresses..
As I said, if the machine is in Boot Camp, no access problems. That's not the case in Parallels. We use that Boot Camp partition under Parallels and everything else works fine; but trying to access that web program under Parallels results in networking issues I just don't know how to handle.
One advantage Boot Camp has is that it uses the Intel iMac's router assigned local address -- so we can use the same 192.168.xx.xxx number to access the machine whether it is in Mac OSX or Windows (Boot Camp) mode.
Parallels introduces NAT addressing, however, and a different local network assignment (10.xxx.xx.xxx). I have tried all avenues I can think of to access the program in Parallels.
If I manually assign (through TCP/IP in the Windows Control Panel) the same 192.168.xx.xxx number to the parallels Windows machine that works in Boot Camp, the system complains that number already exists and is in use; if I give it a unique number (but still using the 192.168.xx.xxx set-up), it is invisible externally, even if I assign that unique number to a port. I've tried DHCP'ing under the Windows TCP/IP, but then it seems to adopt the 10.xxx.xx.xxx series of numbers, which the router can't address. Etc Etc Etc.
I've tried to keep this bare-bones but would gladly expand on my attempts should anyone have some suggestions.
Again, simply put, we are trying to access that Web program (Timeclocks Plus) via a browser address both on the local network and externally when that program is runninng in Windows under Parallels.
Thanks for your attention.
-- samlhall