RDP Connects Via iPad but not Windows

[Debunker13]

I apologise if this question has already been asked. I have a problem with one of my client computers, we've configured their stand-alone Win XP Pro machine as a file-share. This machine also has video surveillance software.

Now I've managed to get the customer to connect via his iDevices, but he still wants to connect via RDC from within Windows. The remote listening port is 1235, but every time he or I try to connect via another XP/Win7 machine we get the following.

Remote Desktop can’t connect to the remote computer for one of these reasons:

1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

I'm not sure how to proceed, the remote listening port works, as attested by the iDevices connecting...Any suggestions?

Jean-Marc

[The Silent Hobo]

are you attempting to connect via local IP? ex: 192.168.x.x? normally when not using a standard port number, it's 192.168.x.x:<nonstandard port> from what i've used and seen.

through RDC anyways

[Debunker13]

Yes and no, I'm trying to connect both locally and externally, but I hadn't thought of using the port number. That did fix the issue. Thanks.

[The Silent Hobo]

glad to be of service. I tend to use RDC when i'm at my inlaws and I need to get on my server for a file or two.

[drpcfix]

in general you should not change the port, didn't you have to hack it in the registry to do that??

There is no reason to, ever..

You can port forward from their internet connection a different series of external ports to the same :3389 port on multiple LAN computers..

ie - able to connect to many computers via one external IP, which would be the only reason to ever change a port, because you need to put many services on one IP..

[The Silent Hobo]

If your system has Remote Desktop enabled, it is listening for connections on port 3389. Since this port is both well known and can be used to attack accounts, it is low hanging fruit for script kiddies and bots looking for an easy target.

changing port #'s is a good idea from what i've read so far and has a logical reasoning behind it.

Source: http://tweaks.com/windows/50743/chan...ktop-rdp-port/