Solved

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

Posted on 2014-04-09
8
947 Views
Last Modified: 2014-04-15
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)?
0
Comment
Question by:samiam41
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 2

Expert Comment

by:colst
ID: 39989269
In vCenter, under the VM properties, verify that the appropriate network is selected.
0
 
LVL 9

Author Comment

by:samiam41
ID: 39989274
Thanks for the reply.  The correct vm network is selected.  It is the same one used by the other vm's.
0
 
LVL 2

Expert Comment

by:colst
ID: 39989281
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
Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

 
LVL 9

Author Comment

by:samiam41
ID: 39989516
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
 
LVL 2

Expert Comment

by:colst
ID: 39989633
How did unintall/reinstall the NIC? If you haven't, try it from Computer Management >> Device Manager and then refresh.
0
 
LVL 9

Accepted Solution

by:
samiam41 earned 0 total points
ID: 39989842
@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
 
LVL 2

Expert Comment

by:colst
ID: 39989986
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
 
LVL 9

Author Closing Comment

by:samiam41
ID: 40001140
While I appreciate the expert's time and involvement, I was able to resolve the issue myself.
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question