Windows Forum

Ask something
Discussion Locked

Upgrade NT4 to 2003 AD

0 helpful
5 replies

by mark_lt 2 views

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

Hiya

I have a nt4 network, and we are creating a new wan link via a ipsecvpn, we decided that this was the opportunity we needed to start the slow upgrade to w2k3 domains.

We staged a server, PDC nt4, then upgraded to 2003, dcpromo was used to create the pdc in the existing domain etc.

Before the upgrade, we used a few spare systems to join the NT4 domain.

The domain name was "yamot" and the fqdn we gave it as part of dcpromo was "yamot.com", but keeping the netbios name.

After upgrade, the workstations that had joined the nt domain, could not log into the new upgraded ones as the machine name was not valid, if they are removed from the netbios domain, then added to the fqdn it worked fine. Any ideas what we are doing wrong?

5 replies

by fatuncleal

Have you configured your DNS? Is your New DC a DNS server? What OS are your spare systems that joined the new domain? Need more info please.

by mfischer

When you renamed the domain by adding the .com you changed all of the machine accounts on the DC. Adding the .com was the issue. You will have to remove all of the clients that are NT based (from the and add them to the domain again. The netbios name of the server isn't really relevant to the machine account. Even if an NT client can't authenticate to the domain (because the name is different) it can still access the server using the unc and authenticate to the share by using yamot\user.name and the password.

This discussion is closed to new replies.