Discussion Locked

XP Pro client on Win2K network

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

I'm managing a Win2k network with about 70 Win98 clients. Recently purchased several XP Pro machines & am able to log in to the domain, & the logon script (to map drives) runs fine. After logging on to the domain I get the following messages:
1stmessage

click OK and the next message pops up
2nd message

We don't use roaming profiles & any user can log on to any Win98 computer without a problem, I just can't get anyone logged on to any of the XP Pro desktops, even if they have a local profile set up.
What am I missing? Is the problem on the server-side or client-side?
I don't have enough space to list everything I've tried -- help!

4 replies

by mike o

Are you getting it on every client workstation? If so, I would say the problem is on your server. I would comb through the roaming profiles settings again and make sure something hasn't been accidentally turned on.

by bjordon

Not that I could find. Can anyone walk me through the steps that need to be taken to set up a W2K or XP Pro client on a W2K server? I've followed Microsoft's instructions, and numerous other suggestions, but am still getting the same message. Whyis it searching for a roaming profile when I log on after joining the domain, and why doesn't it find the local profile that exists on the PC?

by ctmoore1998

Have the XP machines been successfully joined to the domain??? If so then unjoin from the domain change the computer's name then rejoin the domain. Also before doing this make sure the domain user has been added to the XP machine. If you logon to the XP workstation as Administrator then you should be able to see the 'domain users' to add the appropriate user(s) to the XP workstation.

by bjordon

Yes, the machines have successfully joined the domain. The user is added locally, and also as a domain user. I have tried the unjoining & name-changing process and am still having the same problem.

This discussion is closed to new replies.