Node Name Wasn't Found

[Arreks]

Macs.. the bane of my life.

 

So we have our Macs joined to our Windows network via AD and OD - there's always been issues but nothing that can't be fixed through rebinding or rebuilding!

 

Over Easter it seems that a new problem has popped up randomly despite none of us changing any configurations!

 

Basically, a Mac will no longer allow a domain user to log in (which is fine generally, rebuild or rebind to AD fixes this usually) - this time however, if you try and rebind to AD it says "Node Name Wasn't Found".

 

Google tells me this means there's a communication or DNS error but like I said, nothing has changed!

 

Is there any terminal commands I can run while logged in locally to see where the issue lies? It's randomly happening to Macs which renders them unusable.

Edited April 16, 2015 by Arreks

[jlucas]

Sorry I haven't got any solutions for you but I've had this exact thing!

Its driving me round the bend.

 

When unbinding it can't talk to AD and insists there is a time discrepancy. All the macs pull their time from the main DC and ts never out of sync.

 

Force unbinding works but then you have to reboot the machine a couple of times to re-bind and sometime even delete the machine from AD before it'll work.

 

I'll add a "Me too!" to this one!