Unfortunately the guest won't work in a bridged configuration. God knows why. It also can't be configured with a second network card for some reason, which again reduces my options :-(
Hazen emailed me offline to try using VMWare's own internal NAT port forwarding to see if we could push the traffic through by forwarding it to the host first, as you've suggested also. I'm giving that a try now. Cheers, JR On 25 January 2013 12:17, Ben Scott <[email protected]> wrote: > On Fri, Jan 25, 2013 at 5:36 AM, James Rankin <[email protected]> > wrote: > > I'm trying to configure my home router to do some port forwarding onto a > > device on my internal network. However, this is a VMWare Workstation > guest > > using NAT networking so it has an address on a different range > > (192.168.183.x) rather than the home network's default range > (192.168.1.x) > > I presume the VMware host is doing the NAT for the guest. If so, as > far as BT router is concerned, the VMware host *is* the guest. The > host translates the guest's packets so they appear to be coming from > the host itself. That's the whole point of NAT, after all. :) > > You would need to forward the port on the BT router to the VM host, > and then have VMware's internal router forward the packets again to > the guest. I don't know if VMware's router implementation can do port > forwarding. > > Can you change the IP address and net on the guest without breaking > things? If so, is it okay to switch VMware to bridged mode and just > put it on your home LAN? If feasible, that's likely the easiest > solution. > > If not: You could prolly do this with a cheap home router (like a > LinkSys WRT* box) and a second network interface in the host. On the > host, unbind all the OS (Windows) protocols from the second interface. > In VMware, bridge the second interface to the guest, no NAT or DHCP. > Plug the "Local" side of the new router into the second interface. > Plug the "Internet" side of the new router into your main home LAN. > On the BT router, port-forward from the Internet to the new router's > main home LAN address. On the new router, port-forward from the main > home LAN to the guest. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > -- *James Rankin* Technical Consultant (ACA, CCA, MCTS) http://appsensebigot.blogspot.co.uk ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
