Windows 2008 R2 server (vm server) not communicating with network

Hey EE!  I have three VM hosts that several Windows servers are balanced on.  One of the datastores was near full so I shutdown one of the virtual servers (for some reason, we didn't purchase the vmotion license).  After shutting it down, I moved the vm server using vCenter from host 1 to host 2.  There were no errors during this move and the server came right up after the move.

However, the server now shows that it is connected to an "unidentified network" and can't be reached via RDP or by ping.  I did the following with no luck:

verified the IP was correct
disabled and re-enabled the network card on the vm
uninstalled and re-installed the nic on the vm
unchecked the boxes "connected" and "connect at power on"
checked the boxes after the server was restarted

I restarted the server after performing each step.  I'm at a loss as to how to proceed.  The other Windows servers that sit on that host are having none of these problems.  Suggestions (vmware 5.1)?
LVL 9
samiam41Asked:
Who is Participating?
 
samiam41Connect With a Mentor Author Commented:
@Colst, what a PITA!  I did remove the nic the way you suggested in the beginning but it appears I had to dig a little deeper.

I had to uninstall the nic from the server > turn the vm off > from the "edit settings" on the vm, remove the nic again > turn the vm on > log into server and shut it down again > add the nic in the vm "edit settings" > turn vm on > allow server to install nic > bingo!

I have no idea which of these steps can be skipped but those are what I had to do to get the server to be accessible again.  

Thanks for sticking through this!
0
 
colstCommented:
In vCenter, under the VM properties, verify that the appropriate network is selected.
0
 
samiam41Author Commented:
Thanks for the reply.  The correct vm network is selected.  It is the same one used by the other vm's.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
colstCommented:
Are the hosts at the same version? If not, I would check the VM tools next to make sure those are up to date.
0
 
samiam41Author Commented:
All hosts are the same version.

I set the server to get the IP via DHCP and could ping the IP it grabbed.  If I switch the IP back to static, no response.  I turned the FW off on the server with the same non-responsive results.
0
 
colstCommented:
How did unintall/reinstall the NIC? If you haven't, try it from Computer Management >> Device Manager and then refresh.
0
 
colstCommented:
Glad you got it resolved. I remember a couple of years back I had a similar issue and those were about the steps I took.
0
 
samiam41Author Commented:
While I appreciate the expert's time and involvement, I was able to resolve the issue myself.
0
All Courses

From novice to tech pro — start learning today.