Unable to connect to system via remote desktop

jeffster1 is right, Disabling Firewall sounds like a good idea. Are you using an admin or remote desktop users account? Did you enable remote desktop from System properties screen?

Firewall is disabled for both Windows and SEP.

I did enable remote desktop from the system properties screen.

Thanks!

In reading my comment it looks like I accepted a solution - it is still an issue. I have a bad habit of putting Thanks! at the end of whatever I type.

We also did have a reverse lookup issue with the dns - it listed 2 systems names with the same ip - that has been resoved, but still not able to remote desktop to the system.

Does it come back immediately with an error or does it take some time?

Are you able to connect through remote desktop by specifying the IP instead of the hostname?

Are both PC's on the same network subnet?

Jeffster1 - it never generates an error - it stays grayed out and tries to connect for a long time  - eventually the computer name becomes editable again - but never connects.

I have tried to connect via ip - same results.

I have tries from the same subnet and from different subnets to no avail.

Thanks!

The fact that it doesn't give an error message is suspicious.  This sounds stupid, but is there another dialog box opening, maybe with a prompt to type in credentials and it's opening behind some other windows so that you're not seeing it?

From the offending machine, can you remote desktop to itself?  By hostname and IP?

There are no dialog boxes opening - I tried it with nothing else open.

How can it connect to itself? I didn't know that was possible - I thought if you are connected to the console that you couldn't remote to the same system. I did try remoting to other systems from that system and it worked.

All of our systems are routed through a voip Avaya phone. I wouldn't think that it would be the issue since it is the same phone that she had with her old system.

If the computer is a workstation joined to an Active Directory domain, that this can happen for some reason.  Try disjoining the computer from the domain and join it to the domain again to reset the group policy applied to the system.  

It does sound like a group policy problem.  If nothing else then go into that system and manage and add your Domain Admins into Remote Desktop Users on that box.

I would scan port 3389 of the computer in question to see if it is really listening for an RDP connection at all.

http://www.download.com/Scan-Port/3000-2381_4-10155407.html

If port 3389 says filtered than the firewall is still blocking RDP.

Sorry for the delay - I was out of the office yesterday and didn't have a chance to work on the issue.
I tried removing the system from the domain then readded to domain - same issue. I also tried gpupdate with the same result. I will try the port later today. Thanks!

Port 3389 is listening - can telnet and it answers. RDP still does not work on it. I will probably end up reimaging the system.

Reimaging did not work - still getting the same issue. The only thing I can think of to try is using a differet nic.

Using a different nic I still experienced the same issue.

I now have a second system with the exact same issue. We have deployed ~30 systems using the same image - so far it is just the 2 systems with the problem. Any help would be appreciated.