G
Guest
We have a Windows 2000 Domain which has been running fine for over a year
now. DNS is AD-integrated and has also been working fine. We just added a
2003 AD Server following all the directions. I prep'd the primary 2000 DC
first before promoting the 2003 Server. Everything seemed to go just fine.
But...
Now on the 2000 Server which is the primary holder of the FSMO roles, if I
try to open AD it get: "Naming information cannot be located because:
The specified directory service attribute or value does not exist.
Contact your system administrator to verify that your domain is properly
configured and is currently online."
If I reboot the server all is fine again for another day or two.
When this happens I cannot do any DNS lookups because the server cannot
resolve it's own IP. The server had the primary DNS pointed to itself and
secondary to the 2003 server. I swapped them around but that didn't help.
Also the clients CAN authenticate and use DNS on this server just fine. It's
just the server itself that cannot do any DNS.
I do not have any ISP DNS entries in my configuration but in the DNS
forwarder which is where it should be. I cannot browse the net either from
this server.
Of course file replication doesn't happen. Once I reboot replication works
just fine until this problem comes up again in a day or two.
FRS event logs report 1350events... Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/26/2004
Time: 10:08:24 PM
User: N/A
Computer: SERVERA
Description:
The File Replication Service is having trouble enabling replication from
SERVERB to SERVERA for c:\winnt\sysvol\domain using the DNS name
SERVERB.domain.local. FRS will keep retrying.
My only guess is that it's something the prep'ing of 2000 AD has done
because no changes have been made elsewhere.
Hopefully I've given enough info and maybe someone can help. I have been
reading nothing but newsgroups with no fix so far.
now. DNS is AD-integrated and has also been working fine. We just added a
2003 AD Server following all the directions. I prep'd the primary 2000 DC
first before promoting the 2003 Server. Everything seemed to go just fine.
But...
Now on the 2000 Server which is the primary holder of the FSMO roles, if I
try to open AD it get: "Naming information cannot be located because:
The specified directory service attribute or value does not exist.
Contact your system administrator to verify that your domain is properly
configured and is currently online."
If I reboot the server all is fine again for another day or two.
When this happens I cannot do any DNS lookups because the server cannot
resolve it's own IP. The server had the primary DNS pointed to itself and
secondary to the 2003 server. I swapped them around but that didn't help.
Also the clients CAN authenticate and use DNS on this server just fine. It's
just the server itself that cannot do any DNS.
I do not have any ISP DNS entries in my configuration but in the DNS
forwarder which is where it should be. I cannot browse the net either from
this server.
Of course file replication doesn't happen. Once I reboot replication works
just fine until this problem comes up again in a day or two.
FRS event logs report 1350events... Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/26/2004
Time: 10:08:24 PM
User: N/A
Computer: SERVERA
Description:
The File Replication Service is having trouble enabling replication from
SERVERB to SERVERA for c:\winnt\sysvol\domain using the DNS name
SERVERB.domain.local. FRS will keep retrying.
My only guess is that it's something the prep'ing of 2000 AD has done
because no changes have been made elsewhere.
Hopefully I've given enough info and maybe someone can help. I have been
reading nothing but newsgroups with no fix so far.