Dcdiag error 67 on several tests

[luckdog]

Out of the blue I started experiencing some odd network lags, problems logging on, etc. Netdiag runs smooth on bold dcs. Dcdiag shows the following errors on 1st dc:

Starting test: MachineAccount
Could not open pipe with [URSALA]:failed with 67: The network name cannot be found.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN null)
* Missing SPN null)
......................... URSALA failed test MachineAccount

Starting test: Services
Could not open Remote ipc to [URSALA]:failed with 67: The network name cannot be found.
......................... URSALA failed test Services

Starting test: frssysvol
[URSALA] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
......................... URSALA passed test frssysvol

Starting test: kccevent
Failed to enumerate event log records, error The network name cannot be found.
......................... URSALA failed test kccevent

Starting test: systemlog
Failed to enumerate event log records, error The network name cannot be found.
......................... URSALA failed test systemlog

The other dc shows the same errors for this server including a failed Advertising test with the following error:
Starting test: Advertising
Fatal ErrorsGetDcName (URSALA) call failed, error 1707
The Locator could not find the server.
......................... URSALA failed test Advertising

I have been searching all day for any information on the error. Any help would be greatly apprecaited.

Thanks

 

[technome]

Post over on this site, under active directory...

http://x220.win2ktest.com/forum/default.asp

 

[vbrocks]

On the machine called Ursala do this ...

ipconfig /flushdns

ipconfig /registerdns

 

[luckdog]

vbrocks

I ran
ipconfig /flushdsn
ipconfig/registerdn

both ran - no errors but also no change to the stituation.

 

[vbrocks]

Check to make sure all dns settings are correct and the correct dns records are there.
Do an ipconfig /all on the dcs to make sure everything is set correctly...