JLManhattan
asked on
Unable to access ports on a VM outside of the VM
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!
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!
ASKER
The end goal here for this VM is to allow access to a specific port range (13000-13999), and RDP (3389) from outside the parent server. With this configuration I can at least ping the VM from a web server in the network that is not a VM on the parent server.
From the VM at 192.168.100.125 are you able to ping the gateway at .1? Can the Gateway ping .125?
If you are certain this adapter is in bridge mode, do you still have the other adapters assigned to this vm? If so remove them leaving just the VMNet4 (bridged).
If you are certain this adapter is in bridge mode, do you still have the other adapters assigned to this vm? If so remove them leaving just the VMNet4 (bridged).
Don't worry about the services listening on 0.0.0.0 - this just means they are listening on all IPs assigned to the machine and is perfectly normal behaviour.
Make sure the adapter is indeed bridged and not NAT or host-only. Where are you trying to RDP from?
Make sure the adapter is indeed bridged and not NAT or host-only. Where are you trying to RDP from?
ASKER
I just tried pinging the gateway from the VM, it times out pinging 192.168.100.1. No other adapters are set on this VM. Previously I had a second NIC, but removed it prior to the current VM setup. Im not sure how to ping the VM IP from the gateway since I dont have access to the gateway serveror switch.
The single adapter is set to Custom: Specific virtual network, set to VMnet4 (Bridge) which is the parent server NIC for access.
Trying to just RDP to the VM from the parent server to test.
The single adapter is set to Custom: Specific virtual network, set to VMnet4 (Bridge) which is the parent server NIC for access.
Trying to just RDP to the VM from the parent server to test.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After pinging the VM from the parent server the following is produced from the arp -a command:
Interface: 192.168.100.24 --- 0x10005
Internet Address Physical Address Type
192.168.100.1 00-a0-8e-9a-8c-34 dynamic
192.168.100.20 00-19-b9-eb-ec-eb dynamic
192.168.100.21 00-19-b9-eb-eb-67 dynamic
192.168.100.25 00-1e-4f-fb-f4-98 dynamic
192.168.100.51 00-0c-29-c9-a3-84 dynamic
192.168.100.125 00-0c-29-49-4b-78 dynamic
Interface: 128.11.167.236 --- 0x10006
Internet Address Physical Address Type
128.11.167.225 00-a0-8e-7c-a3-a7 dynamic
Interface: 4.34.117.101 --- 0x10007
Internet Address Physical Address Type
4.34.117.1 00-00-0c-07-ac-01 dynamic
What is very odd (and not being a network admin of course this is odd to me!) is that for a brief 5 minutes or so I was able to telnet to other ports on the VM, and establish an RDP session. After about 5 minutes as noted I was no longer able to RDP or telnet to other ports on the VM.
Interface: 192.168.100.24 --- 0x10005
Internet Address Physical Address Type
192.168.100.1 00-a0-8e-9a-8c-34 dynamic
192.168.100.20 00-19-b9-eb-ec-eb dynamic
192.168.100.21 00-19-b9-eb-eb-67 dynamic
192.168.100.25 00-1e-4f-fb-f4-98 dynamic
192.168.100.51 00-0c-29-c9-a3-84 dynamic
192.168.100.125 00-0c-29-49-4b-78 dynamic
Interface: 128.11.167.236 --- 0x10006
Internet Address Physical Address Type
128.11.167.225 00-a0-8e-7c-a3-a7 dynamic
Interface: 4.34.117.101 --- 0x10007
Internet Address Physical Address Type
4.34.117.1 00-00-0c-07-ac-01 dynamic
What is very odd (and not being a network admin of course this is odd to me!) is that for a brief 5 minutes or so I was able to telnet to other ports on the VM, and establish an RDP session. After about 5 minutes as noted I was no longer able to RDP or telnet to other ports on the VM.
Yes, that is indeed very strange! The arp entries show that all machines are present and able to communicate - I assume you did this before or during the time when the RDP session was up?
If so, it would be interesting to see the results of arp -a when you are unable to connect via RDP.
If so, it would be interesting to see the results of arp -a when you are unable to connect via RDP.
ASKER
I noticed after that 5 minutes or so the VM IP is no longer in the arp listing from the parent server. Is there a way to make that permanent? I tried the ping again and arp -a on the parent server, I was only able to reproduce being able to telnet to other ports on the VM and RDP that one time. Each time I try since it fails.
ASKER
OK, and what is even wierder (or so my brain says), regardless of what I change or do, I can always telnet to the VM on port 80 from the parent server (but not outside the server). But if I telnet to any other ports it still fails.
Ok, if there is no arp entry for the server in question then connectivity is not possible as layer 2 has failed - this can be caused by physical NICs being disabled or by a bad install of VMware.
Check to make sure that your NICs are not configured to be allowed to shut down by your PC's power configuration and re-install VMWare - what you are seeing is not normal behaviour.
Check your Windows System Logs to see if there are any services crashing / erroring.
Check to make sure that your NICs are not configured to be allowed to shut down by your PC's power configuration and re-install VMWare - what you are seeing is not normal behaviour.
Check your Windows System Logs to see if there are any services crashing / erroring.
ASKER
Thanks for the info! Could be a bad install of VMWare, or possibly my host provider is allowing the IPs to stick (not sure) as now the VM IP is remaining int he ARP table and I can RDPto it from the VM. It has been up for about 15 minutes without problem. Will monitor and see if it fails again.
ASKER
OK, maybe this has soemthing to do with my host provider not letting me keep the IP address assigned to the VM. The VM stayed up for about 30-40 minutes (RDP session was open for about that long), then disconnected from the network (was no longer present int he ARP table on the parent server).
If there are anyother recommendations for this that wouldbe appreciated. If not, thanks for the help, will assign points as needed.
If there are anyother recommendations for this that wouldbe appreciated. If not, thanks for the help, will assign points as needed.
ASKER
OK, just confirmed, the reason why I keep losing the connection is due to my host provider. They are trying to assign the IP I have set to another device - go figure.
Thanks again!
Thanks again!
ASKER
Windows IP Configuration
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.153.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.204.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VPN:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.100.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
VM Server
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.100.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
The VM is setup using a single NIC that is on VMNet4 which is using the VPN Nic in the parent server's Ipconfig.