VMware Cloud Community
Rose_Holland
Contributor
Contributor

VM DNS Connection Issues

Hi all,

So I have an issue with one of our new systems. Basically, we had a 2012 R2 VM become inaccessable because it can't connect to a logon server. We can ping it from the DC and every other system on our network. We don't have the local credentials due to a lack of continuity, but this isn't the only system having this issue. We have a web proxy that's returning the same error, it can't connect to a logon server, again same issue with a local logon unfortunately.

I deployed a new system because we can't get a recovery tool to work, and despite having correct gateway and DNS addresses configured and being able to ping from the DNS server to this new system and vis versa, we can't get the DNS server to respond. The timing is right, Windows Firewall is disabled, and we can ping the default gateway.

I looked into the virtual networking settings, and this is where stuff looks a bit funny. We have 4 physical NICs servicing 6 network adaptors, two for a file server and 4 for that web proxy server I mentioned earlier. The 2012 system and my new 2016 system I deployed don't have MACs when I look at the ESX host's network configuration. I'm thinking that the vswitch is saturated and can't actually support all the connections and that I need to migrate my 2012 machine or my 2016 machine to another of our ESX hosts. If anyone has some ideas that would be super helpful, I put together a different recovery tool for our 2012 system to try and troubleshoot from in there too.

 

Thanks loves :red_heart:
Rosé

Reply
0 Kudos
1 Reply
Alex_Romeo
Leadership
Leadership

Hi,

Try this test: remove the card's network parameters (IP, DNS, GW, Subnet). Unplug it and add a new network card, enter the correct parameters on the new card.

 

regards,

ARomeo

Blog: https://www.aleadmin.it/
Tags (1)
Reply
0 Kudos