Windows Forum

Ask something
Discussion Locked

AD Migration Woes !

0 helpful
5 replies

by azamup

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

Hello All!

I have upgraded my NT4.0 to 2K Standard Server & successfully migrated all users with Dcpromo. One think I have only changed is the domain name first it was "HO" but now have entered FQDN i.e "HO.COM" all users are working fine they are getting authontication and other services very well.

Here comes the painful part, now when i wana add a user sitting on a workstation in pwr users group choosing it from domain "HO.COM" for giving him pwr user group membership it do shows the domain members but after choosing specific user the error occured that "The Specifield domain either does not exist or could not be contacted" the domain usr cudn't get into the pwr users group. if v repeat the same it just didn't show the domain "HO.COM". I cudn't understand what to do coz on this server their's all applications running v can not change it at once any idea/ solution will be greatly helpful.

Regards,

Azam

5 replies

by brianaaa12

This is a name resolution problem. Your workstation is not recognizing the FQDN. In my situation, I have DNS and DHCP running on my server. In addition I have all workstations pointing to the server for DNS resolution. At a command prompt on the workstation, do a "ipconfig /release" then do "ipconfig /renew". In addition, just to be safe, I added the server to the locals HOSTS file. Once the workstation was able to properly "see" a FQDN, all worked well.

Brian

by hard_yakka

Azam,
This is almost certainly a DNS resolution problem.
(In case you didn't know DNS is essential for AD to work properly)

Server Side
* Are there any errors in the server DNS event logs?
* Check the DNS admin tool. Can you see both the server and the client listed as hosts in Both in Foreward and Reverse lookup zones?

* Ensure the server is running the latest service pack. (i've seen DNS problems with service pack 2 and below)

Client Side
* Try the nslookup tool on the client to ensure you can resolve the server correctly

99.9% of problems like you are describing are DNS related. Get it right and you are likly to have few problems with AD. Let me know how you go. If you are still having difficulties give me more details and I troubleshoot further.

This discussion is closed to new replies.