Hi,
I'm having the following problem with my ESX server: when my NIC is configured in DHCP, all works fine: I can conenct to both internal as external addresses.
However, when I put in a static IP, i can connect to local addresses but not to internet addresses. What I did to configure the IP was:
esxcfg-vswif -i 192.168.10.10 -n 255.255.255.0 vswif0
then added gateway in /etc/sysconfig/network
and finally added DNS servers in /etc/resolv.conf
After doing service network restart, I can ping local addresses. But when I do a tracepath to e.g. www.google.com the address resolves fine but trace stops on the default gateway?
Nothing is wrong with the default gateway as it works fine if configured with DHCP. If I compare ifconfig and route under DHCP and static I see no differences.
Anyone have an idea?
Can you ping the default gateway when static?
If yes can you ping external IP addresses?
What is your default gateway i.e. DSL router, ISA firewall etc etc
what is your DHCP source? is it the same as your gateway?
Is there a way to clear the ARP cache on your default gateway?
Try to add the VMkernel default gateway with "esxcfg-route ".
Open all ports on the ESX Console with "esxcfg-firewall allowIncoming" and "allowOutgoing" (for testing only, of course. Then it should work.
If you found this information useful, please consider awarding points for "Correct" or "Helpful" replies. Thanks!!
AWo
VCP / vEXPERT 2009
Edited by AWo
Yes, when in static I can ping the gateway fine. But nothing beyond that.
Default gateway is a Watchdog Firebox firewall.
DHCP source is a windows server on the same subnet.
Not sure if I could clear the arp on the Firebox...
the esxcfg-route command didn't work at first:
esxcfg-route 192.168.10.1
Error: Cannot set gateway or routes until kernel TCP stack has at least 1 IP address
I searched for this error and found I had to add a VMkernel first through the client UI. After doing that, the command worked.
esxcfg-route
VMkernel default gateway is 192.168.10.1
However, still no way to pass the gateway of my network:
tracepath www.google.com
1: ESX.local (192.168.10.10) 0.198ms pmtu 1500
1: 192.168.10.1 (192.168.10.1) 1.444ms
2: no reply
3: no reply
PING www.l.google.com (209.85.227.99) 56(84) bytes of data.
--- www.l.google.com ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9012ms
And still it works when configured with DHCP...
you will find it much easier if you use "reservations" in your pdc's dhcp server.
OK, problem was with firewall indeed. It was out of client licenses and not letting any additional connections pass through... grmbl.