Discussion Locked

NTto Server 2003 upgrade

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Built an NT4.0 BDS, replicated with PDC, promoted BDC to PDC, took offline, performed in place upgrade to Server 2003.
When installing AD and DNS chose first domain in forest and gave name 123.local, old NT domain was 123.
Made sure DHCP giving new DC as primary DNS.
Is above correct?
Now client pc's can't log onto the new 2003 DC. There are 300 client's and rejoining to new domain not practical.
I'm thinking maybe there is a problem with the domain name in 2003.
Any suggestions would be appreciated.

6 replies

by curlergirl

What kind of error do they get when trying to log on? You can't log on directly to a domain from a workstation that is not a member of the domain, unless your workstations are Win9x, in which case domain membership is moot and it should work fine. For Win2K/XP workstations, when the computer is joined to the domain, a SID is assigned to the computer, and a trust relationship is created between the computer and the domain, and that is missing in your scenario. The old SIDs from the NT domain will not work on your new AD domain - the workstation has to be rejoined even if the domain name is the same.

You could have the users log on locally to the workstation and then access the domain through Network Places. The first time they try to open a domain resource, they will get a logon request at that time. Then, once their credentials are established for that session, they probably will not have to log on again until they log off or reboot.

Hope this helps!

by adent888

Turns out DHCP was incorrect. I tried assigning new DC as static DNS server and all worked. Spoke to tech who manages DHCP server and had scope recreated and all worked.
The SIDs were migrated during the upgrade. Thank you both for your suggestions.

This discussion is closed to new replies.