Mach03
asked on
Windows 2000 Client doesn't connect to Windows 2000/2003 domain correctly
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????
Thanks
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i think i may have missed something when i first read this post,,, is this happening for just one machine, or on all machines in the non-DC subnet?? If it is happening on just one machine i would remove it from the domain, reboot it, rename it, reboot it, and then re-add it to the domain, reboot. This will give this computer a whole new account in AD.
ASKER
Good point, it's happening with all the computers on that subnet. One machine I did remove it, rename it, and rejoin it. Still nothing.
ASKER
Okay, now I'm getting a DCOM 10003 error. "Access denied attempting to launch a DCOM Server using DefaultLaunchPermission. The server is {00020906-0000-0000-C000-0
I've search the internet, but I haven't found any REAL descriptions to this probme or how to fine the {0002~46} server.
I've search the internet, but I haven't found any REAL descriptions to this probme or how to fine the {0002~46} server.
ASKER
The printers are a standard IP share from on the DC's and yes they can ping that server. Since it's on of the DC's it running DNS and I have it set to my primary DNS. When I run Nslookup it connected and gives my various IPs of sites all over the world.
The method I did was a default action that the Windows 2003 setup did when I ran dcpromo on the 03 server. It detected that my 2000 domain (yes native mode) wasn't prepaired for the 2003 server and it asked me to upgrade the domain before I did. I shifted the Domain Naming Master & RID Master FSMO's to the server running 2000 (PDC) and ran the "prepair 2000 domain for 2003" wizard. Once that was done, I ran dcpromo on the 03 server and sync the AD.
I'm back over in the non-dc subnet, brought the machine back and it's still not working properly. The good news is I ran netdiag.. no errors. I ran dcdiag on both of my DC's.. not errors neither. However, printer and file shares are still giving me issues. If I have all the settings the exact same, but just move the pc from one building to the next, how can this be? The DNS servers, WINS server, and gateway are all connected and pingable (is that a word?) but still no method to the madness.