Crucial Domain Problem

@MLF
Did that hundred of times but no use.

@dinowuff
Getting error "The computer did not resync because no time data is available"

There is a DNS error in the event log Event id 6702.

"DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code."

Also when i try to access the GP for any OU i get attached error messages.

So can you ping 127.0.0.1???

Sounds like you have a hardware connection issue...either NIC, cable, switch.

MLF

@MLF
Yes i can ping my loopback and i am doubtful its hardware issue.

When i run dcdiag, i get error: -

Server MYSERVER resolved to this IP address OLDIP,
but the address couldn't be reached(pinged), so check the network.
The error returned was: Error due to lack of resources.
This error more often means that the targeted server is
shutdown or disconnected from the network
Done gathering initial info.

I have removed the DNS re-install it but issued remains there, when i run arp -a i found the old ip with 00 as mac address and invalid as type, removed the cached and now i am not seeing that IP but still DC resolving its name to OLDIP.

I belive some record in AD or my router (acting as DHCP) is not refreshed and server gettin updates from there.
Is there a way i can check the current DC record in AD?

Ok...so you can ping your self...means the NIC is working...but doesnt you are actually connected to anything
can you ping anything else??

MLF

Did someone add the ip address of that server to the hosts file? check in %windir%\system32\drivers\etc\hosts for a static entry in the host file.

nslookup would show the correct address because you are asking the dns server for it's host record of the particular machine. resolution is a bit different. it will look to your hosts and lmhosts file before it uses dns

I suffered through this ordeal some time ago. Sad part? I completely forgot what caused my issue and how I fixed it. In any event, I vistited some sites I had boomarked and ran across this:

Quote:

---

The mandatory Connectivity test is executed on every DCdiag test run. This test verifies the most important functionalities of a domain controller: whether all DNS resource records are registered on the preferred DNS server, and whether DCs are pingable and have LDAP/RPC accessibility. For example, using /a or /e parameters, you can quickly find all DCs that are not responsible

---

This was an elaboration of the DCDIAG message you received.

They then suggested running netdiag /test:DNS

This all came from here

It's killing me because as I re-read this stuff, I vaguely remember cursing alot and spending late nights staring at DCDIAG results.