User is a member of Domain Admin group cannot log on to out Windows 2003 file server.
I'm a domain admin in a windows 2008 R2 domain and have no difficulty logging onto any servers via RDP within our domain. However, my coworker who is in the same domain security groups as I am can not log into our windows 2003 sp2 file server with his domain credentials. When he attempt to log into the server using RDP the display screen says "loading personal settings" and it hangs for ever and never really makes the connection. How can I resolve this issue?
Paul MacDonald
Can he log into the machine locally? My guess would be something wrong with his profile on that machine.
Try deleting the profile from the server it seems to be corrupted.
You'll probably have to reboot the system prior to deleting or renaming the old profile, but doing so should fix the issue like stated above.
ASKER
Well, he has deleted his profile and renamed it and that did not work either. In fact its generating alot shstat.exe processes in task manager and the same thing started happening for me. We can not log into locally (either) as ourselves but we can log into into locally as domain admin.
How certain are you this machine is clean (of viruses)?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've done full antivirus scan on it too and that came back clean.
Okay. I concur with waiting - maybe as long as a week - until you establish you can (or can't) reliably log in to the machine.
ASKER
So, far everything has continued to look normal. There are NO excessive instances of shstat.exe processes in task manager. In addition, myself and my coworker can also log into the server via RDP without any difficulty.
ASKER
Well, it clearly seems that rebooting the server resolved the issue although it does not tell me what caused it and how to prevent it from happesning again.
Yes, I hate when that happens.
ASKER
Everything is still functioning fine/normally. So I'm going to go head and close this question.
ASKER
It resolved the issue. At least it got the server functioning normally eventhough I was unable to find the route cause of the generation of the numerous shstat.exe processes.