3 replies
by garo Accepted solution
by Former member Accepted solution
Finally managed to solve an issue that has been bugging me for months. A user was logging onto the Terminal server but two of their network drives would not connect as part of the login script. However doing a net use and providing username and password in the prompts would connect (which is how they've been connecting for a while). Logging into a local pc worked fine, but logging in via terminal services always had this problem - so it had to be something to do with the roaming terminal service profile.
Eventvwr was showing events Userenv 1030 - Windows cannot query for the list of Group Policy objects, Userenv 1006 - Windows cannot bind to domain.com domain (Invalid Credentials), MsGina 1010 Failed to set the user's home directory,
I tried debugging using KB221833:
http://support.microsoft.com/kb/221833
which gave me 43 pages of logs to read through.
Eventually I logged into the Terminal server as the user, went into control panel, stored passwords and lo and behold - there was someone elses username (and password). Deleted this stored account, logged off and back on again and got all their network drives connected.
control keymgr.dll is a shortcut to this screen that users might be able to use to clear this themselves.
Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.
by shreedhar_pattar Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending