remote desktop problem

**CableDude** · 08-13-12, 06:51 PM

I get this when I try to connect to a PC remotely:

1. It is not a SERVER. It is a desktop PC. XP sp3 all updated
2. The remote computer was ON when I tried to connect.
3. The remote computer IS available as far as I can tell. I can connect to the internet, do windows updates. It is NOT on the DOMAIN. (That shouldn't be an issue)

Any ideas? by chance am I missing a service? I checked the Windows Firewall and remote desktop is an EXCEPTION (In fact, the Windows Firewall was DISABLED when I tried to connect.)

Remote access is ENABLED

***YeOldeStonecat*** · 08-13-12, 07:43 PM

Trying to connect to it via IP address? If so...are you sure the IP is correct?
Trying to connect to it via netbios host name? If so...are you resolving it to the correct IP?
Is it enabled on the remote host? Even if leftover from a domain with old group policies still in effect...check the registry to ensure it's enabled
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections
value of 0 because you want it to not deny

Local Administrator account is not blank, right? Else...remote desktop host cannot/will not enable

Assume you're doing this from across the same LAN? Or are you doing it to a different subnet or part of a WAN with firewall rules?

**CableDude** · 08-13-12, 08:11 PM

Tried via IP address - No go
Tried via Netbios host name - No go

Will check registry

Administrator account is NOT blank.

Across the same LAN.

***YeOldeStonecat*** · 08-13-12, 08:28 PM

Double check software firewall rules too.
Was the host customized in the past to answer RDP on a custom port?

**CableDude** · 08-14-12, 05:53 PM

Look at Registry - It is set to what you suggested already.
Checked Windows Firewall - The settings compare with another XP machine that I can REMOTE into.

Very strange.....Could it be something in the network jack that goes back to the switch?

***YeOldeStonecat*** · 08-15-12, 06:26 AM

It could if it was a managed switch and it had some ACls on it.
Did you check the port number for the RDP host to ensure it's default?

If you ping via IP, does it reply?
If you ping via host name, does it reply?

**CableDude** · 08-15-12, 06:42 AM

I know when I did ping via IP and host it did reply.

Will check the port number. I believe it was TCP 3389

**CableDude** · 08-16-12, 05:33 PM

Cat,

I pulled out another XP machine (both Dell optiplexes, btw) and CAN NOT remote into it as well. Can remote in with TightVNC on both.

**RaisinCain** · 08-16-12, 05:42 PM

Sounds like a firewall issue or RDP not being enabled on the PC (as well as the user name not being added to RDP to connect on the remote system.

***YeOldeStonecat*** · 08-17-12, 08:54 AM

I second...check RDP being enabled...don't forget that second check box for the specific user....and don't forget to check if it's locked down to NTLM security newer RDP client only (not enabled by default).

Are you connecting with the user account credentials..or not?
Is there a GPO that governs remote desktop users?
Do employees connect to their desktops via TSGateway?

**CableDude** · 08-22-12, 08:03 PM

Originally Posted by YeOldeStonecat

I second...check RDP being enabled...don't forget that second check box for the specific user....and don't forget to check if it's locked down to NTLM security newer RDP client only (not enabled by default).

Are you connecting with the user account credentials..or not?
Is there a GPO that governs remote desktop users?
Do employees connect to their desktops via TSGateway?

I'll give it a look again..... Never seem to have an issue with 7 or Vista (Or 2003 & 2008)