I have a problem. I support many computers for a Govt. agency. Our login domain server is controlled by another seperate entity. We have no control over this domain and have to live by thier policies. We have installed Windows XP on %50 of our computers. All have been working fine until today. Now when we try and join a new XP install to this W2k Domain server we get trust relationship cannot be established. or the domain server is not available, try again later. We call up the govt. guys that control that domain server and thier out was "they don't support XP" end of story. Windows 2000 only. It does not mess with existing XP computers only new ones we try to setup after today. My long question is this: Can the domain server guys actually lock out new XP setups from being slaved on the domain and only allow 2000 pro? The domain guys know that this is a problem, but are unwilling to correct it. Either that or it is a problem they have created and wish not to solve it to force us to use only windows 2000 pro. Ideas?

Can you still join new 2K machines to the domain? I would guess that the domain administrators restricted your rights to join PC's to the domain. If they somehow found a way to exclude XP boxes it would seem strange that the old ones would stick. Anyway, I would bet on new security policy from the domain guys. Keep posting I am curious to see how this plays out.

After many hours of harassing these guys, it seems there was a type of driver that had been corrupt on the W2K server that was preventing access of shares and new workstations of XP boxes from being added or accessed on the W2K domain. They fixed it over the weekend and now all is back to normal. How and what file this is I haven't got a clue. Interesting how it didn't affect W2k machines, only XP. I wonder if it was someway of reading the kernel version that would prevent it from accessing the W2K domain?