VMWare client cannot ping gateway

Im having troubles with VMWare clients being unable to access the default route.

My router has an internal IP address of:
59.166.231.89 (this is the default route I want to use)

My VMWare host has the following:
192.168.1.1
Secondary IP 59.166.231.90
The host can ping the router IP.

A standalone IP host:
PubIP: 59.166.231.91
IntIP: 192.168.1.100
This host can ping the router IP.

My VMWare client has the following:
192.168.1.98
59.166.231.92
This client can ping 59.166.231.91 and 59.166.231.90
This client CANNOT ping 59.166.231.89
network adapter is set to bridged mode on the same interface the host uses for 59.166.231.90

I'm totally stumped. Please help.
djclarksonAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
djclarksonConnect With a Mentor Author Commented:
Thanks all. I ended up trying something completely differnet. Thanks for the effort, but I was never able to solve it.
0
 
ArtellosCommented:
Wich subnets are used?

I Assume the router is a physical one.
Also, assumed the VMWare Host is running something that needs to be accessed by the VMWare Client.
Are the VMWare Host and Client on the same Hosting PC?

Also,what does the A standalone IP host: do?
If you could do "ipconfig /all" on the pc's and post those here aswell i'll try to help you :)


Olrik
0
 
djclarksonAuthor Commented:
Subnets:
192.168.1.0/24
59.166.231.88/28

When I say VMWare host and client I am referring to the Windows 2003 server which runs the VMWare software and the client is the virtual machine on that Windows 2003 server.

The Standalone host is the gaming rig. It has no vmware installed.

The router is a hardware based router. Open iConnect 625w.

The VMWare virtual machine has one physical ethernet interface and three CentOS virtual interfaces as follows:

eth0: 59.166.231.92
eth0:0 59.166.231.93
eth0:1 59.166.231.94
eth0:2 192.168.1.98

0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
ArtellosCommented:
On the win2k3 server

Go to start
Run
CMD
type: "ipconfig /all"
right click in the screen and click "Mark"
Select the whole screen and press enter.

If you could mail this to me at "o.lenstra@gmail.com"
0
 
djclarksonAuthor Commented:

 Connection-specific DNS Suffix  . :
 Description . . . . . . . . . . . : D-Link DUB-E100 USB 2.0 to Fast Ethernet
apter
 Physical Address. . . . . . . . . : 00-80-C8-38-58-D1
 DHCP Enabled. . . . . . . . . . . : No
 IP Address. . . . . . . . . . . . : 59.166.231.90
 Subnet Mask . . . . . . . . . . . : 255.255.255.248
 IP Address. . . . . . . . . . . . : 192.168.1.1
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . : 192.168.1.254
 DNS Servers . . . . . . . . . . . : 192.168.1.1

hernet adapter Net:

 Connection-specific DNS Suffix  . :
 Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
 Physical Address. . . . . . . . . : 00-30-1B-BA-92-63
 DHCP Enabled. . . . . . . . . . . : No
 IP Address. . . . . . . . . . . . : 10.1.1.2
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . :
 DNS Servers . . . . . . . . . . . : 203.2.193.124
0
 
ArtellosCommented:
Ok, i see you're not using DHCP, but what confuses me is that you have 2 ip adresses on 1 NIC? or do you have more NICs in that win2k3 server?
The default gateway is set to 192.168.1.254, where is that located?
And why is there an ip of "59.166.231.90" being used as an internal IP.

Take a look at http://www.rhebus.com/techinfo/iprange.htm 
Although i'm not really familiar with CentOS and how the virtual interfaces is done the network looks a bit more complex then it actually has to be.

Olrik
0
 
djclarksonAuthor Commented:
I have given my system two ip addresses. The 192.168.1.0/24 network is private. The 59.167.x.x network is public. The gaming machine needs both as one of the games doesn't behave with NAT.

Still none of this explains why the vmware virtual machine cant ping the router.

192.168.1.254 is located on the same switch as the vmware server and the gaming server.
0
 
ArtellosCommented:
Is the VMWare Host also using Bridged?
Could it be a possibility to use NAT instead of Bridged?
0
 
djclarksonAuthor Commented:
If I did that I wouldnt be able to use the individual public addresses.
0
 
ArtellosCommented:
Just noticed the following:
The VMWare client's second IP is 59.166.231.92
The VMWare host's second IP is 59.166.231.90
They are being run on the same PC (The Win2k3 srv)
(some enlightment here?)

Also, 59.166.231.88/28 should be 59.166.231.88/29 if i'm not mistaken seeing that the Subnet you had on the win2k3 server was 255.255.255.248?

Are the addresses configured for the client correct?
0
 
djclarksonAuthor Commented:
When you use bridging the client network IP is on the same network as the physical interface of the host. So having the two IPs on teh same net shouldnt be a problem. And it wouldnt explain why the client can ping the gaming servers public IP address and not the router.

You're probably right about the mask, though it wont have any effect on this test either as the router is on the same network either way.
0
 
ArtellosCommented:
I suggest you do change the subnet mask though. You're using public IP's not private ones. There could be other devices on the other subnet that has the same IP as the router to collide.
0
 
djclarksonAuthor Commented:
That doesnt make sense. The ISP will route my public subnet via the CPE IP address. The only thing it could effect is the ability of one of my public IP addresses to connect to an IP address in the other subnet. Very unlikely, though I will change it nonetheless.
0
 
ArtellosCommented:
I'm sorry i'm not able to help.
I'll send a mail to war1 and Lrmoore asking if they can help.

Olrik
0
 
djclarksonAuthor Commented:
Thanks for trying though. :)
0
 
HalindarCommented:
Hi,

Still having this problem?

If so, did you check your guest OS network settings with 4 interfaces only one should have a default gateway setting and for the other interfaces you should set up a routing table.
Are the 3 virtual CentOS interfaces not VMware virtual NICs but additional virtual IPs next to the primary IP on the (Virtual) physical NIC?

Maybe you should check the routing tables on the CentOS VM and on your Win2003 host, it sounds like there is a route set somewhere that makes the ping not arrive at the physical router.
Also to double check routing you could do a traceroute to the .90 and .91 addresses to see if somewhere it gets routed over the 192.168.1.x network.
0
All Courses

From novice to tech pro — start learning today.