Cannot ping or access vm once moved onto new VSphere server

[firestartah]

Hi

I have setup up a new vsphere server here in my dev environment. I set it up as usual and with step by step guides. Everything seems to be working fine and i can vmotion machines onto the esx node no problem but when i try to access the server via remote desktop or ping it it cannot be accessed. If i move the machine back to one of my 3.5 servers it is pingable again. I have checked with the networking guy and all teaming and vlan etc are all up and running. The esxnode is pingable itself also.

Anyone have any ideas? Do you have to open a firewall in vsphere to allow inbound access?

Thanks

Gregg

MCSE, MCSA, MCTS,MCITP

[weinstein5]

I would first take a close look at the configuration of the virtual switch on the vSphere host used by the VM - if all that checks then the issue will have to be with the physical network -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

[firestartah]

The vswitch all looks correct and i have recreated it to make sure. The link and vlan is right as the vmotion vmkernel runs on the same vlan as the service console.

[firestartah]

It seems it was a basic error of the network cables not teaming correctly. I removed all the vlans and machines on it then i rebooted it. Once it was back up i broke the teaming by removing one of the network adapters from the service console, then readded it, removed the second one and readded it and this seems to have done the trick.