Oh... sorry I missed that line in your description.
Sorry.
:-)
Main Topics
Browse All TopicsHello guys,
here's the issue I've been trying to resolve for the past 4 days with no luck...
We have a Win Server 2003 that is configured as Terminal Server. There are 6 users configured to connect to it (1 administrator and 5 Remote Desktop users). All users are able to log in without any issues except one particular user. When he tries to log in (either at the server itself or through another computer), he can see the gray bar with "Applying your personal settings..." thingy and then a gray box titled "Personalized Settings" appears in the upper left corner of the screen (showing nothing inside it) and that's all...
I've red several topics regarding this issue and dowloaded few hotfixes from Microsoft, but still cannot solve anything. I even waited about 3 hours hoping that it will eventually pass this (as some suggested that they are still able to log, although very slow), but nothing happened. I added the reg-key for the userenv debbuging mode, and there are few constantly repeating lines (I've attached the userenv.log file) :
"GetUserDNSDomainName: Computer is running standalone. No DNS domain name available."
and
"ImpersonateUser: Failed to impersonate user with 5."
The server logs no errors, everyone else is working fine. I've tried deleting the user (including reg cleanup) and then adding it again, but still nothing.
The machine is Windows 2003 Server, Standard Edition with SP2
Tried to log from several machines (most of them with XP SP2, one with XP SP3)
Can you please give me any idea what to do at least what is causing this?
P.S.: I forgot to mention that the server is freshly recovered from a Winsock corruption, maybe this has something to do with the whole issue...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
No, no roaming profiles. As a matter of fact, I've tried creating an entirely new profile, and it has the same problem. Very odd... Seems like something is wrong with the winlogon or some other process that is responsible for loading the user's profile. Btw, the other users seem to be working as fine as ever.
P.S. I did a full antivirus and anti-spyware scan this morning but I found nothing...
At this point, I'd suggest that you use the User Profile Hive Cleanup Utility:
http://www.microsoft.com/d
Jeff
TechSoEasy
Thanks for the idea Jeff!
But unfortunately I was forced to reinstall because one scoop of the CPU fan broke and the whole chassis started vibrating violently, wich triggered the HDD's safe positioning several times, wich screwed the whole Windows. So it's problem solved (one way or the other...). Thaks for the help x)
Business Accounts
Answer for Membership
by: TechSoEasyPosted on 2008-09-05 at 19:12:37ID: 22405221
Have you tried deleting his local profile and allowing it to rebuild?
Jeff
TechSoEasy