General discussion

Locked

Upgrade NT4 to 2003 AD

By mark_lt ·
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?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by FatUncleAL In reply to Upgrade NT4 to 2003 AD

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.

Collapse -

by mark_lt In reply to

Poster rated this answer.

Collapse -

by mfischer In reply to Upgrade NT4 to 2003 AD

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.

Collapse -

by mark_lt In reply to

Poster rated this answer.

Collapse -

by mark_lt In reply to Upgrade NT4 to 2003 AD

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums