Child Domain Access Problems

[Guest]

I have 2 Win2k domains in 2 different locations which I will call PARENT.COM
and CHILD.PARENT.COM. Each domain has 2 Domain Controllers. I recently
retired the PDC/Global Catalog server for CHILD.PARENT.COM and replaced it
with a new server. Initially all network access worked in both
directions...ie. clients in PARENT.COM could access resources in
CHILD.PARENT.COM and clients of CHILD.PARENT.COM could access resources in
PARENT.COM. About 1 1/2 months after the install of the new server in
CHILD.PARENT.COM, all clients in PARENT.COM lost access to a mapped drive on
the new server in CHILD.PARENT.COM after a reboot and when I try to recreate
the drive mapping I get the error "There are currently no logon servers
available to service the logon request." The PARENT client can still ping
the CHILD server, as well as even remote desktop into the server, but no file
and directory access can be made.

Clients on the CHILD domain have had no disruption in connectivity.

The way I am currently getting around it is to log into the PARENT domain
client machine as the CHILD domain administrator, log off (NOT RESTART) then
log back on to the machine as any PARENT domain user and the access to the
CHILD domain resources is restored until the next reboot.

Any ideas or suggestions would be greatly appreciated!

 

[Steven L Umbach]

This probably is dns related or network connectivity. When you retired the
old domain controller I assume you transferred the 5 fsmo and global catalog
server role to another domain controller and made changes to dns client
entries [ including other domain controllers] to reflect any changes in a
new IP address that the new domain controller has versus the old including
DHCP scopes. Also check your dns zone records for ns entries to make sure
they are correct including the delegation for the child zone if used.

Look in Event Viewer on the domain controllers in each domain for any
pertinent errors and run first the netdiag and then dcdiag support tool on
the domain controllers looking for errors that will point you in the right
direction. My guess is you will find some errors. Post them here in a reply
if you need any help. Review the KB article below for AD dns to make sure
you are following it. If you make any changes to dns configuration of a
domain controller make sure you run ipconfig /flushdns, then ipconfig
/registerdns, then netdiag /fix, and then restart netlogon on the domain
controller where you make the change. For non domain controller use
ipconfig /flushdns, then ipconfig /registerdns. The client dns will cache
negative lookups which will make changes to dns look like they are not
working. The nslookup tool also comes in handy when troubleshooting dns
issues. If you use nslookup you will get an error message if you do not have
a reverse zone configured, but nslookup should still be able to find your
dns server and resolve names. ---- Steve


http://support.microsoft.com/default.aspx?scid=kb;en-us;291382