• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4811
  • Last Modified:

VMware ESX 3.0.1 No Ping

I have a Dell PowerEdge 6850 that came preinstalled with Winddows Server 2003.  I have removed Windows Server 2003 and installed VMWare ESX Server 3.0.1.  The problem that I am having is that I am unable to ping the ESX Server, or on the ESX Server, I am unable to ping the gateway.  The ESX Server has a static IP, and it has a Broadcom NetXtreme network adaptor.  How do I configure the network card correctly?
0
pepsi_cola
Asked:
pepsi_cola
  • 4
  • 4
1 Solution
 
BrucematCommented:
if you issue an ifconfig command do you get back any useful info there should be an eth0 or something like that with an address bound to it.
Failing that an out put from your /var/log/messages file from a clean boot would be helpful in fixing this problem
0
 
pepsi_colaAuthor Commented:
I do get an output when I run the ifconfig command.  it just shows me the IP Address, Subnet Mask, Default Gateway, etc.; basically the values I used to configure the host network card.
0
 
BrucematCommented:
can you ping from the esx server the localhost and the ip of the internal nic
also can you post the output of the command route.
also the contents of I think the file is /etc/network/interfaces would be useful.
If these are live internet ip's please coment the ip's out like this 1**.2**.***.***
Cheers
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
pepsi_colaAuthor Commented:
I believe I have figured out the problem.  The ESX can't connect to the domain.  So, how do I get the ESX server connected to a Windows network?
0
 
BrucematCommented:
you shouldnt need to conect the esx to the domain the virtual servers on the esx can conect to the domain but the esx server its self is only a cut down os just enough to host the vm's
0
 
pepsi_colaAuthor Commented:
I believe the problem lies in the OS and the poorly written instructions provided by VMWare on how to configure the network interface card.  I reinstalled VMWare ESX Server and used a 10.10.20.X IP and connected a laptop with VMWare Infrastructure Client to console into the ESX Server and everthing is working fine that way.  I went ahead and reinstalled it as intended and still no go.  The nic card is showing up as vswif0 instead of eth0, which tells me that the nic si showing up as a Virtual Switch.
0
 
BrucematCommented:
If it can bind to one ip it should bind to them all weird.. what subnet is the ip going to be on and what mask does it have. could you not build the server with the 10.10 ip and change the ip after install if its a buggy script?? you can bind another ip to the nic using ifconfig vswif0:1 10.0.0.3 (or what ever ip you want) to see if you can see the second bound address. This will be lost after a reboot though so its only a test nothing permanent.
0
 
pepsi_colaAuthor Commented:
I have managed to solve the problem on my own.  During the installation process, when setting up the network, I entered in a value for the VLAN that I was using.  Somehow that was causing the NICS not to work properly.  When I reinstalled ESX server without a VLAN value, everthing worked like a charm.

Thank you for your time and help, here are your points.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now