Windows

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.

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

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.