General discussion

Locked

NT4 Upgraded to w2k AD

By mikesummers1 ·
1. Was nt4 now 2k AD.
2. 2 different networks on the one server:
"olddomain" and "server1.domain.com.
3. He has the old domain on the upgraded server as well as the new site.
They had 1 pdc, and 2 bdc's all NT4, now only one BDC is nt4. The other 2 have 2k on them and I am trying to install AD on the non PDC AD server and make it a member server of the new "server1.domain.com" site on the new PDC. In AD when I get to the point it asks me for a user and pass and domain to log in to it tells me it is not an AD domain or the domain cannot be found. I can ping the new PDC and it resolves the name. I can ping the server I am putting AD on from the new PDC as well. I am new to this, so if I have not explained everything I am sorry.
This is all on an internal network. This was done before I got there and I am now in charge of fixing it. Thanks for any help.

Mike

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by p.j.hutchison In reply to NT4 Upgraded to w2k AD

Make sure Client for MS Networks is installed and TCPIP is configured correctly esp DNS settings to allow you to join the AD domain.

Collapse -

by mikesummers1 In reply to

Client is installed and TCPIP is configured correctly. I can authenticate from a 2000 pro workstation, but I cannot authenticate from the other 2k server. It tells me the domain "domain.com" is not an active directory domain or it cannot be located. Thanks for the help.

Mike

Collapse -

by p.j.hutchison In reply to NT4 Upgraded to w2k AD

Try running 'netsh winsock reset' to reset TCPIP stack to a clean state.
Also check Event Logs for any errors.

Collapse -

by mikesummers1 In reply to
Collapse -

by mikesummers1 In reply to NT4 Upgraded to w2k AD

This question was closed by the author

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

Related Discussions

Related Forums