Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a 2003 server which was a member of an NT4 domain.
I have moved it into a Windows 2000 domain.
However, since the move the logon time has gone from approx 2-3 seconds to 30 seconds.
I have no group policies being applied and any machine that has not been moved from another domain but is in the windows 2000 domain, the logon takes 2-3 seconds.My DNS and WINS are all pointing to the correct location. The domain change appears to have worked yet it takes extra long to logon.
Interestingly, if I logon with an account from the old domain it only takes a couple of seconds.
ANyone have any ideas?
Did you properly remove the server from the old domain and then join it properly to the new one?
It sounds like it's binding up while looking for the old domain.
0 
i placed into a workgroup.
then rebooted.
joined new domain
rebooted again. I think is still referencing old domain somewhere but not sure where
0
I believe you're correct. That's why I asked if you removed it from the old domain correctly. To be honest, I don't think you did.
If you still can, bring it back up in the old domain and remove it correctly. You'll have to access MS's site for proper removal procedure though as I don't remember offhand since it's been over a decade since I touched NT4
0
It appears to me the transfer was done correctly. Don't forget we are talking NT not AD.
The 2003 server was a member server of the NT domain. Joining a workgroup was correct. To join the Ad domain you would run dcpromo on the 2003 server and add it as a DC or member server
Did you run dcpromo?
Next area to check is DNS. This 2003 server tcp/ip properties should list the AD DNS server by ip. In DNS there should be host and ptr records for this 2003 server.
0
The DNS on the 2003 server is pointing to the 2000 domains DNS. There is a PTR record in the reverse lookup zone under the subnet which the 2003 server resides. I cannot locate a host record. I thought these related to WINS?
I didnt run DCPROMO. I simply added it to the domain from MY Computer properties under the computer name tab. I thought this was sufficient as didnt want 2003 server to be a DC.
When I type SET command, I can see that it has found the nearest DC which is a Global catalog. I think it may be going around the houses before it finds the right DC. Is there a tool which shows what machine is doing during logon process?
0
Its pointing to one of the DNS servers on the new domain which is also on the same subnet.
This DNS server incidentally is the same DC which is authenticating me when I logon.
This is a manual entry - not through DHCP.
0
manual host entries are just fine. You would have to do that since this "server" should not be on dhcp but have a static ip entry.
You say you can logon to the nt domain. Is this from the same workstation that connects to the 2000 domain?
How about sharing what servers you have, their functions, if all in the same subnet and which are your wins/dns servers.
Also have you updated the wins entries for this 2003 server?
BTW I have never added a server by joining it to the domain the way you did. I have never read of adding a server this way. I can't even find a chapter on it in my 2003 server books on the topic. It has always been as a DC or member using dcpromo so I believe AD sees this server just as a workstation. Which means it should not have any effect on logons to the 2000 domain.
Make sure you have removed all referances to this server from the nt domain especially the wins server.
0  |
 |
 |
| Login or Register to Reply | |
| Login | Register |
| Ads by Google |
