Upgraded server from NT4 to 2000: Problem joining domain

  • Thread starter Thread starter Thommas
  • Start date Start date
T

Thommas

I have upgraded a Windows NT4 box to Windows 2000 with
Active Directory. When upgrading I chose another domain
name that was more like the name of my company.

Everything works fine the way it is right now. But things
are a bit slow when logging on and the domain is still
called by the old domain name. I guess this is because in
AD it still says that the old domain name is for Pre-
Windows 2000 computers (or similar) :)

But when I try to join a new computer into the new domain
I get an error message that directs me to
http://go.microsoft.com/fwLink/?LinkId=5171. I have tried
everything that is on here, but nothing has worked. I have
searched the net several times and tried everything, but
no luck. However, if I try to join the domain with the old
name - this works fine. And when I have rebooted - the
domain name appears as the NEW domain name...

I have enabled dynamic updates, DNS *seems* to work fine,
but I'm not sure... might it have something to do with the
fact that the clients doesn't reach a DNS server and
insted use TCP/IP over NetBIOS or something? This might
also be the case with the slow logons?

Anybody got a clue what this can be? This is quite
annoying.. :)

I have bought a brand new server that I want to migrate
the users to... is this the right way to go at all?
 
When you changed the name of the domain, you actually only changed the AD DNS name of the domain. The netbios name of
the domain stayed the same. This accounts for the inconsistancies you are seeing. You should be able to add machines to the
domain using the AD domain name. Just make sure that you are using the full domain name when you enter it. Also, all clients
and servers must point at a AD DNS server only. Do not point at any other DNS servers.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
In
Thommas said:
I have upgraded a Windows NT4 box to Windows 2000 with
Active Directory. When upgrading I chose another domain
name that was more like the name of my company.

Everything works fine the way it is right now. But things
are a bit slow when logging on and the domain is still
called by the old domain name. I guess this is because in
AD it still says that the old domain name is for Pre-
Windows 2000 computers (or similar) :)

But when I try to join a new computer into the new domain
I get an error message that directs me to
http://go.microsoft.com/fwLink/?LinkId=5171. I have tried
everything that is on here, but nothing has worked. I have
searched the net several times and tried everything, but
no luck. However, if I try to join the domain with the old
name - this works fine. And when I have rebooted - the
domain name appears as the NEW domain name...

I have enabled dynamic updates, DNS *seems* to work fine,
but I'm not sure... might it have something to do with the
fact that the clients doesn't reach a DNS server and
insted use TCP/IP over NetBIOS or something? This might
also be the case with the slow logons?

Anybody got a clue what this can be? This is quite
annoying.. :)

I have bought a brand new server that I want to migrate
the users to... is this the right way to go at all?
Click to expand...

The usual suspect is that you have your ISP's DNS in your TCP/IP properties,
you should only use your local DNS server address.
But since this is an NT4 upgrade there is another problem that we see a lot,
a disjointed name space due to an incorrect primary DNS suffix. On NT4
upgrades it draws the primary DNS suffix from the domain suffix in TCP/IP
properties in NT4.

If you will post an unedited ipconfg /all from your DC AND the actual name
of your domain from ADU&C I can verify this and advise you as to a fix.
 
Thank you for your answer.

I have set the DNS address to be the local DNS-server and
not the ISP on the computers I am testing. There are still
other computers in my network pointing to the ISP DNS
server, but this shouldn't affect this problem should it?

I have checked several thing regarding the disjointed
namespace problem with things I have looked up on the
Internet with no luck. Here is my ipconfig /all on my DC:

---[ipconfig /all]----


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : server1
Primary DNS Suffix . . . . . . . : LAV.local
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : LAV.local

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : LAV.local
Description . . . . . . . . . . . : Compaq NC3163
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-EA-1B-
76

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 172.17.77.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 172.17.77.1

DNS Servers . . . . . . . . . . . : 172.17.77.3

---[end ipconfig /all]---

When I open ADU&C I see LAV.local in the top of the tree.
However if I right click and choose Properties it
says: "Domain name (pre-Windows 2000): VG-SKOLE" .. this
is the old domain name from NT4.. this works fine..

Did this help you? :)
 
Thank you for your answer :)

I feel I am a bit beyond this. I have tried this several
times with no luck..

Got any more suggestions? :)
-----Original Message-----
When you changed the name of the domain, you actually
Click to expand...
only changed the AD DNS name of the domain. The netbios
name of
the domain stayed the same. This accounts for the
Click to expand...
inconsistancies you are seeing. You should be able to add
machines to the
domain using the AD domain name. Just make sure that you
Click to expand...
are using the full domain name when you enter it. Also,
all clients
and servers must point at a AD DNS server only. Do not
Click to expand...
point at any other DNS servers.
Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from
 
In
Thomas said:
Thank you for your answer.

I have set the DNS address to be the local DNS-server and
not the ISP on the computers I am testing. There are still
other computers in my network pointing to the ISP DNS
server, but this shouldn't affect this problem should it?

I have checked several thing regarding the disjointed
namespace problem with things I have looked up on the
Internet with no luck. Here is my ipconfig /all on my DC:

---[ipconfig /all]----


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : server1
Primary DNS Suffix . . . . . . . : LAV.local
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : LAV.local

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : LAV.local
Description . . . . . . . . . . . : Compaq NC3163
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-EA-1B-
76

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 172.17.77.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 172.17.77.1

DNS Servers . . . . . . . . . . . : 172.17.77.3

---[end ipconfig /all]---

When I open ADU&C I see LAV.local in the top of the tree.
However if I right click and choose Properties it
says: "Domain name (pre-Windows 2000): VG-SKOLE" .. this
is the old domain name from NT4.. this works fine..

Did this help you? :)
Click to expand...


VG-SKOLE is the NetBIOS name of the domain, which is OK. Your ipconfig /all
looks good and the primary DNS suffix LAV.local matches your DNS domain
name, it might confuse you a little since the names are so different, just
make sure all Win2k and later domain members use only the DC for DNS, this
is required.
It is advisable, just for the sake of reducing confusion that all machines
point to the DC for DNS. Then, when or if they are upgraded there won't be
any problems.
 
Back
Top