17 replies
by ejsotillo
by lkane
by whitney597
by lkane
by dheupel
It sounds like there could be a combination of problems...
1) The NT Workstation is set up to not log into a domain (or a different domain), therefore, all logins are locally on the workstation only. If there is no user account on the local workstation, a user will get this error message.
2) The workstation login process is looking for a roaming profile, but cannot attach to the network share containing the user's profile. Check permissions set on the network share containing user's profiles.
3) The workstation is incorrectly registered in Server Manager/Workstations, and/or WINS. You might want to delete the workstation entries in WINS, and delete then re-add the workstation name in Server Manager.
Good luck.
by lkane
by hitesh.patel
by lkane
by redshift
by lkane
by bill cassada
by lkane
by ejsotillo
by lkane
by mckaytech
I had a problem similar to this recently and in that case, the problem turned out to be that someone had deleted the Default User profile so the operating system could create the new profile, but not populate it.
Something to take a look at, perhaps. But it also occurs to me that this problem could result from a system policy that, for whatever reason, was configured to apply to that workstation only.
regards!
paul
by lkane
by lkane
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending