Windows 2000 Client doesn't connect to Windows 2000/2003 domain correctly
Posted on 2005-05-10
This is a really odd situation which is why I'm having a hard time finding any documentation to resolve it. I have two DC's one running Windows 2000 and the other running Windows 2003. All my client machines are running Windows 2000, but they are located in two subnets. One subnet is the same as the servers is running just fine, but the other subnet clients can't connect to the printers and they get "Disk Full" errors when trying to save on the file server. This is really bazarr but this issue surfaced about the same time as I upgraded AD to accomindate the 2003 server. Just for kicks, I brought one machine from the other subnet over plugged it in and everythign works fine. This rules out any updates or viruses for the time being. I've even configured the network cards exactly the same as my test machine in the working subnet... no change. One of the machines is receiving a 5789 DNS error "Access Denied" but the others are not. This machine is giving me an LDAP error while running NetDiag, but DCDIAG is passing. The LDAP is the "SPN registration is missing", but I've unjoined this computer and joined it multiple times and still nothign. Is there another program here that I'm missing, somethign that shows me I don't have a complete connection or somethign????