New server 2003 machine introduced into an existing 2000 domain - TechRepublic
General discussion
May 4, 2005 at 07:29 AM
pauld

New server 2003 machine introduced into an existing 2000 domain

by pauld . Updated 21 years, 2 months ago

Hello all, we recently purchased a new server with 2003 standard pre-installed. Currently we have a server 2000 setup on our network. There is a PDC and an additional DC both running server 2000. When the new server arrived I brought it up off the network. After I had logged into the new server I shut it down and connected it to the network. I ran adprep /forestprep then /domainprep on the PDC and it ran flawlessly. Now, with the new server connected to the network I added the role of domain controller to it. It appeared to go fine. The AD has replicated and the server seemed to be functioning properly. I went into the machine that is the pdc, opened AD and looked in the domain controllers container. It shows itself and the second 2000 dc in the container but not the new 2003 machine. I then went into AD on the second DC and looked in the domain controllers container on that machine. It shows itself, the pdc AND the new 2003 server machine as domain controllers. That is strange in itself. The issue is that no machine on the domain can access the new 2003 servers share except that secondary domain controller. It’s as if the new 2003 machine isn’t recognizing it’s own AD. In any case I’m stumped and need some help fairly quickly with this. Any help would be greatly appreciated.

This discussion is locked

All Comments