Server 2003 remote desktop = what the heck ?

Soldato
Joined
12 May 2005
Posts
12,631
Hey,

Cutting a massively long story short, my company has a remote server (in the USA) which will eventually be used to hopefully host a online training program.

Aforementioned program isn't installing correctly, an one of the techs in the USA who wrote the program offered to logon to the server via RDP and have a look for me.

Ok, I can RDP fine (I live in the UK) and indeed, it is how I installed the program in question, problem is - he can't.

He is getting the error message:

"the client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are prevent your connection.

Please try connecting later, if problems persist contact your administrator"


He can connect to the Plesk control panel, but for some reason the windows 2003 RDP won't accept him - it will only give him access to Plesk.

I have given him the exact same admin username and password as I have BTW, but he isn't even getting to the stage where he can enter them, it won't even let him get to the logon prompt.

Anyone have any suggestions ?
 
Ask him if he can telnet the server (preferably the IP to avoid any DNS confusion) on port 3389. That's the port Remote Desktop listens on.

If he can't, then it's more than likely a firewall problem and he'll have to get the port opened.
 
Hmmm,

I called someone just now and asked them if they could use RDP to the server (I didn't give them the password / username - just wanted to see if they could even connect to the RDP).

They did so flawlessly - odd :/

The guy in the USA having the issues even tried connecting from a server they have in California too.
 
Back
Top Bottom