Forum Home
Press F1
 
Thread ID: 106681 2010-01-19 01:28:00 Server 2003 RDP has stopped working aidanmaz (7180) Press F1
Post ID Timestamp Content User
849805 2010-01-19 02:50:00 No AV/firewall software running that could suddenly be blocking RDP? CYaBro (73)
849806 2010-01-19 02:50:00 can you telnet to that port on the server? Telnet Servername PortNo. If it works then you should get a blank black box. If you dont then something is blocking the communication with the server. Barnabas (4562)
849807 2010-01-19 02:52:00 I had that same error on a win2k3 box, it was some sort of common problem, could not RDP into it.
Sorry can't remember what the fix I used was, will go through my notes.
FAB (6923)
849808 2010-01-19 02:54:00 Sorry doubled up a message somehow. FAB (6923)
849809 2010-01-19 03:09:00 What error message are you getting?, unable to reach server, refusal? SolMiester (139)
849810 2010-01-19 03:27:00 Error: Client could not connect to the remote computer. Remote connections might not be enabled or the computer is too busy to accept new connections.

Im using Eset NOD32 for A/V and havent had issues in the past. telnet failed to port 3389 on the local machine.
aidanmaz (7180)
849811 2010-01-19 03:41:00 Are you using remote admin as opposed to terminal services?, so not a licensing issue!

Checked the tcp/ip config?

edit - try from another pc, i have had a pc refused for no reason before when it used to work....
SolMiester (139)
849812 2010-01-19 03:47:00 On the actual server can you do a netstat -an does it show that 3389 is listening? Barnabas (4562)
849813 2010-01-19 03:51:00 Using remote admin, not T/S environment. netstat -an doesnt mention 3389 in any of the listings. Using any machine i get the same rdp error. aidanmaz (7180)
849814 2010-01-19 03:56:00 Can you check this reg key HKEY_LOCAL_MACHINE'SYSTEM'CurrentControlSet'
Control'Terminal Server'WinStations'RDP-Tcp portnumber and see if it is set to 3389
Barnabas (4562)
1 2 3