Link to home
Start Free TrialLog in
Avatar of kellysteevens
kellysteevens

asked on

RDP won't work - just hangs (Windows XP and SP3 installed)

I am banging my head against the wall here.  I feel like I've tried everything!  I have 2 Dell dual monitors (model e248wfp) and an ATI Radeon HD 4350 video card.

I previously remoted into my computer all of the time and now when I try, it just hangs at the login screen.  My computer got a virus and I had to re-image.  After the re-imaging, everything is great but RDP won't work.

A week ago, when I attempted to fix this issue, I downloaded the newest video card drivers and logged in and it totally worked.  Since then I have tried a million other times and it never works.

I am in desperate need of this for my job as I have to remote in a lot.

Any help is greatly appreciated.  I wish I could offer 10,000 points as this is what a resolution is worth to me!!!!  Plus, I've spent probably 10 hours on this issue, so if anyone can figure it out, I will consider you a genius.

Kelly
Avatar of dmwynne
dmwynne
Flag of United States of America image

What actually happens?  Do you get a login prompt at all?

have u tried doing rdp using single monitor
disable 2nd monitor and try rdp
Avatar of Bryon H
depending on what actually happens, you might be interested in some command-line switches
(these can be put into start > run)


sorry, the attach didnt actually attach:

http://img141.imageshack.us/img141/3675/mstsc.png

mstsc.png
Nvidia Video Card on teh remote PC?

Whats in the Event Logs, under the source Terminal Services?
You could try disbling all of the mapped devices in RDP like printers, drives, and ports. It could be hanging trying to install a printer driver or something that doesn't exist on the remote machine.
Avatar of kellysteevens
kellysteevens

ASKER

Thank you for the posts.  It isn't an Nvidia card.  It's an ATI card.  I have tried disabling all of the devices.  No luck.  I have tried only a single monitor.  No luck.  What happens is that the login box pops up, I login and click "Ok" and the login screen just sits there (freezes).

I did have a minor breakthrough this morning.  I tried logging in as another user on my machine and I can totally get in!!  Also, I had a ghost backup of my machine that was pretty bare bones and I rolled back to that.  No luck though.

My theory is that there is some application installed only for my user that is keeping me from remoting in??  We have SBS 2003 and husband deleted my user from server and re-added it, but same problem.

Any ideas?
I will try the command line switches a little later.  I have to remind myself how to do all of that.  :o)
It could be a group policy or login script attached to your user account causing issues. You could move your user account into the default user container, do a gpupdate and then try again.
Update:  I've found that I'm able to log in via RDP when using a different user account(s), just not my own. If connected via RDP with another account I can disconnect and RDP in using my account successfully (kicking off the other account).   If I'm logged off locally I'm able to RDP using my account.  The only time I'm unable to RDP in is when my account is already logged in.

Ideas?
I just found that if logged in via RDP with my account, I'm unable to log in locally with my account until I either log off via RDP or log in locally with another account (then log off and log in with my account).  In essence the exact opposite of what I described above.  In short, my account in unable to kick itself off.
You should see some Userenv/User32 errors in the Event Logs.....
Do you have this same issue on other PC's?
No, we've never had this issue before and I use RDP every single day.
ASKER CERTIFIED SOLUTION
Avatar of Encrypted1024
Encrypted1024
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Create an other user for you self, and delete the old one. Maybe your local profile is corrupted. Maybe your local and on the server. Try to create anonther user .