0

I have 2 windows 2012 R2 servers in a production environment. Both are VM's and configured same with the ip address as different. I haven't recieved alert of any kind of network failure for one machine. But second machine fails intermittently.

When I try to connect through rdp, it never connects. No pinging too.. But telnet to 3389 works perfectly. I login to that machine through console, and looked the network adapter settings and I could find no change in already configured settings, but I could find an exclamation mark near to the network icon in the taskbar.

Tried troubleshooting and the result was "your computer appears to be correctly configured but the device or resource (www.microsoft.com) is not responding"

When I disable and then re-enable the network interface card, then it will work fine. I can take RDP as well as pinging works perfect.

Googled and found this post, but when I checked, no updates have been installed in that server. Have anyone experienced this kind of issue yet??

Any help would be really appreciated..

1 Answer 1

1

I'm assuming that the VMs are running in a Hyper-V environment (on server 2012 R2)?

Depending on what nics your host is using, and how you've configured them, this is a known issue.

See more details here:

http://www.hyper-v.nu/archives/mvaneijk/2013/11/vnics-and-vms-loose-connectivity-at-random-on-windows-server-2012-r2/

4
  • Sorry.. It is not... It is in VMWare Environment.. Commented Mar 28, 2014 at 11:16
  • 1
    Usually you have two NIC types to choose from in VMware. Which one are you using? I've seen similar issues, when using the legacy E1000 adapter. Try to switch to the VMXNET3 adapter instead. Make sure to update the vmtools on your guest first. See more info here: vmwarebits.com/content/… Commented Mar 28, 2014 at 13:02
  • Great...I think you are right... Anyway I will have a check and if it is correct...Will mark your answer correct..Thanks... But one question too.. This machine is up now. So, if I have to change the adapter type, I believe it must be shut down. Also, can I connect to same network label and give this same static IP? Any other precautions to be taken? Commented Mar 31, 2014 at 12:09
  • Imagine it was a physical machine, and the network adapter somehow broke, so you had to replace it - it's basically the same operation you are doing. - So yes, you can connect to the same network label and reuse the static IP. I'd uninstall the E1000 from the OS, before you shut it down and remove the adapter. This way the OS will look at it, like the card was never there. Commented Apr 4, 2014 at 10:37

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.