Archived from groups: microsoft.public.windowsnt.domain (More info?)
I stumbled into this problem last night when trying to help someone out.
They had one NT4 PDC with one Win2K client as a member of the domain. They
also had 5 NT4 workstations that were set up on a workgroup. Their plan was
to upgrade all of their client pcs to WinXP and join the domain. After
performing the client upgrades, they were unable to join any of the pcs to
the domain. So in a panic this person renamed the domain without giving it
a second thought.
When I got there to try to help out, there was connectivity between all
computers and server only by IP address - no name resolution. The thing is,
I don't know how it was setup in the first place when it was working. I
added DNS and WINS to the server with no luck. I am in no way a DNS/WINS
expert, however. Win2k/2003 sets it up automatically, is there anything you
must do manually in NT?
Any tricks on adding an XP client to an NT domain?
I stumbled into this problem last night when trying to help someone out.
They had one NT4 PDC with one Win2K client as a member of the domain. They
also had 5 NT4 workstations that were set up on a workgroup. Their plan was
to upgrade all of their client pcs to WinXP and join the domain. After
performing the client upgrades, they were unable to join any of the pcs to
the domain. So in a panic this person renamed the domain without giving it
a second thought.
When I got there to try to help out, there was connectivity between all
computers and server only by IP address - no name resolution. The thing is,
I don't know how it was setup in the first place when it was working. I
added DNS and WINS to the server with no luck. I am in no way a DNS/WINS
expert, however. Win2k/2003 sets it up automatically, is there anything you
must do manually in NT?
Any tricks on adding an XP client to an NT domain?