NIC issue?

[SovietRussia]

Got a couple of machines, gone a bit mad:

 

 

• Can ping IP of DC
  
• Cannot ping hostname of DC
  
• Cannot do nslookup of anything
  
• Cannot even browse the internet on them (IE - proxy server is not responding)
  

 

And because it cannot resolve the DC hostname, it isn't getting Group Policy updates etc. What is even weirder:

 

 

• Can connect via SMB to the DC using its hostname, and authenticate...
  

 

What is going on?! Could it be the NIC of the machines?

[mikes]

I had a similar issue with our laptops that was down to MS's DirectAccess not working properly, the laptops thought they were off the corp domain and so tried to use the IPHTTPS tunnel for DNS lookups and would fail.

We could ping by IP but not by hostname. That however wouldn't explain why you can connect via SMB and authenticate though (we couldn't do that, if we tried browsing via hostname via SMB, it would bring an Offline Files cached version up)

 

 

Do you use MS DirectAccess at all? If you put your servers in the HOSTS file, can you ping them then? (we could, but still couldn't GPUPDATE)

I would say probably not a hardware issue, maybe something wrong with DNS on the machines?

[SovietRussia]

I popped the servers into the hosts file, and it refused to return them, so its like skipping the hosts file which is bizzare!

 

I did ipconfig /displaydns and the entries in the hosts file show there, so I have no idea!

 

No not using DirectAccess.

[pete]

If the Windows firewall is on, where does it think it is? Domain network, home/work network or public network?

[SovietRussia]

No firewall is disabled across the network

[SYNACK]

No firewall is disabled across the network

Eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeep!

 

But one problem at a time, it just sounds like DNS is squiffy, can you ping your DNS server and see if dhcp is setting it as a DNS server, if nslookup is working this is probably a DNS fail. SMB shares may still be running by name thanks to windows falling back to NetBIOS or something similar.

[3s-gtech]

It's my network, so I'll take responsibility for that decision. It has been off for over eight years now, but yes I am aware that it's a bad idea! In testing to re-enable it, we just found it to be a real dog. It's well secured otherwise, but we know!

 

DNS centrally is working nicely. This is on a few isolated workstations. Once reimaged, they're fine so we'll nuke them today.

[skell]

Is the time off on them?

[3s-gtech]

Nope. It honestly looks as if some networking components of the OS are stuffed. It's very odd. I suspect it's not a coincidence that I pushed out an upgrade to AB TC v7 through the tutor program at the time they went south - but who knows how that happened.

[MordyT]

Try a cmd... Netsh winsock reset and a reboot