General discussion

Locked

Can't Join XP Machnies to Domain

By cridley ·
Just put in a nice new W2K server, replaced an aging NT Box, is the single PDC and DNS server for a network of 170 PCs. 95, 98, 2K & MAC boxes are happy - log onto the PDC, get network resouces & etc, all is well. None of the 45 XP boxes can log on to the 2k server, stating the domain is not available. In the event viewer on the server I find the following:
The computer xyz tried to connect to the server \\SERVER using the trust relationship established by the ABC domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.
Have added these PCs to "AD Users & Computers", and one could log on, but only once, then no more. When trying to estab the trust, it returns the error that it is not able to.
Could ot migrate the Users, Groups & SIDs over from the NT svr, rebuilt from scratch on the new one. Suggestions?

This conversation is currently closed to new comments.

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

All Comments

Collapse -

Can't Join XP Machnies to Domain

by bohicam1 In reply to Can't Join XP Machnies to ...

On the XP boxes, under DNS settings, is the DNS server the first choice listed? If not, try that.
I don't think there needs to be any kind of "trust" relationship here as they are all in the same domain.
Good luck!

Mike

Collapse -

Can't Join XP Machnies to Domain

by cridley In reply to Can't Join XP Machnies to ...

It is the only DNS listed. I did not think there needed to be a trust relationship as in the type you set up btween domains & etc. The problem has to be with the settings in the XP boxes, specifically, the SIDs it previuosly provided to the old server.

Collapse -

Can't Join XP Machnies to Domain

by stahler In reply to Can't Join XP Machnies to ...

I had similar problems, specifying DNS helped all the time.
Is your domain by chance called SERVER? Mine was, I had to call Microsoft because I couldn't figure out what was going on with trust between A B and Server domains. If it is, there is anissue with the name SERVER in a W2K domain. Server is a reserved word in AD. I am not sure if you can have the server named server either. Anyway, good luck!

Collapse -

Can't Join XP Machnies to Domain

by stahler In reply to Can't Join XP Machnies to ...

I did not read your questions correctly. please disreguard my comments!

Collapse -

Can't Join XP Machnies to Domain

by cridley In reply to Can't Join XP Machnies to ...

Problem solved. It is usually the obvious that we miss. On the XP boxes, remove them from the domain, assign to a workgroup, then reboot, rejoin them to the domain again with the new server up and all is well. The XP boxes use and keep SIDs (Security IDs?) as an extra measure of security, for authenticating. When they tried to access the domain on the new 2K server, the SIDs they were providing were proper credentials for the old NT box, thus the server said, "Ptoooy, not in here ya don't!" as the 2K server wanted to assign it's own SID and the XP boxes would not budge. Also, had to uninstall all the printers on the XP boxes and reinstall. So much for XP being seemlessly integrated to anything but itself. BTW, you are right about thename server for the domain or the actual name of the server. I tried this on my own small network, just playing around and it caused all sorts of grief. Shame it doe not tell you this during the AD config. The name of the server in this incident was not server, I just did not want to post the actual server name on the net. Anyway, 6 wasted hours reonfiguring XP boxes later and it works.

Collapse -

Can't Join XP Machnies to Domain

by cridley In reply to Can't Join XP Machnies to ...

This question was closed by the author

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

Related Discussions

Related Forums