I have a Virtual Machine setup, windows 2003 web VM running on VMWare Server Console 1.0.8 on the parent server (running windows2003 server). The VM is setup using one NIC that is bridge to VMNet4 (which is setup to use the parent server NIC that has access to the network). The VM is setup using an assigned IP on the same subnet as the parent server. I can ping the VM without any issue on and off the parent server from a web server.
Previously I had the VM setup to use two NICs, one to VMnet0, and the other was setup to NAT. I had found that I could not access the VM outside of the parent server having VM NICs setup this way, so changed it to use VMnet4 (on the parent's NIC that has network access).
Since making this change to use a single NIC on VMnet4 I have found is that all applications such as RDP and the main client app I am using on the VM are all setup to listen on 0.0.0.0 vs. the assigned IP of 192.168.100.125.
Is there any reason why the applications are listening on 0.0.0.0 vs. the IP assigned since making the NIC change?
I had added a route and found that I could use RDP for about 2 minutes. Not sure if this was just a blip or not. Any suggestions are welcomed!