wasabikev
asked on
RDP error : The client could not establish a connection to the remote computer
I am rolling out a new batch of laptops, and for some reason they are all unable to RDP into one of the servers on my network. When trying to RDP to this server, the following error results:
Title Bar: Remote Desktop Disconnected
The client could not establish a connection to the remote computer.
The most likely causes for this error are:
1) Remote connections might not be enabled at the remote computer.
2) The maximum number of connections was exceeded at the remote computer.
3) A network error occured while establishing the connection.
The troubleshooting details...
-RDP into this sever from other machines on the network works fine. This is only impacting recently imaged & deployed machines. (imaging via RIS & Riprep)
-RDP into any other server in the internal network works fine. Only this server is impacted.
-Laptop can ping the server, tracert is 1 hop, and can telnet into 3389 on server.
-Server has been rebooted.
-Connection limit is not being exceeded.
-There are no entries in the event logs on the client side.
-There are no entries in the event logs on the sever side.
-Clients are all fully patched XP w/ SP2
-Server is fully patched MS 2003 w/ SP2
I'm out of ideas... I'd very much appricate any insight you can provide.
Title Bar: Remote Desktop Disconnected
The client could not establish a connection to the remote computer.
The most likely causes for this error are:
1) Remote connections might not be enabled at the remote computer.
2) The maximum number of connections was exceeded at the remote computer.
3) A network error occured while establishing the connection.
The troubleshooting details...
-RDP into this sever from other machines on the network works fine. This is only impacting recently imaged & deployed machines. (imaging via RIS & Riprep)
-RDP into any other server in the internal network works fine. Only this server is impacted.
-Laptop can ping the server, tracert is 1 hop, and can telnet into 3389 on server.
-Server has been rebooted.
-Connection limit is not being exceeded.
-There are no entries in the event logs on the client side.
-There are no entries in the event logs on the sever side.
-Clients are all fully patched XP w/ SP2
-Server is fully patched MS 2003 w/ SP2
I'm out of ideas... I'd very much appricate any insight you can provide.
Check to make sure that the Allow Remote Connections is checked on the remote computer. Also make sure the Terminal Services service is running.
ASKER
tsmvp:
There is not a licensing server set... this particular server is in our DMZ as a stand-alone server in its own workgroup, and all internal users login to it via the same username/password. (I know...not my design. That's another issue.) This is done only infrequently- so the standard 3 concurrent administrative logins have been adequate for it's task.
When trying to connect, it never even gets to the login screen, it pops the error instantly. :(
AnthonyP9618:
Please re-read master post. "RDP into this sever from other machines on the network works fine." Many thanks.
There is not a licensing server set... this particular server is in our DMZ as a stand-alone server in its own workgroup, and all internal users login to it via the same username/password. (I know...not my design. That's another issue.) This is done only infrequently- so the standard 3 concurrent administrative logins have been adequate for it's task.
When trying to connect, it never even gets to the login screen, it pops the error instantly. :(
AnthonyP9618:
Please re-read master post. "RDP into this sever from other machines on the network works fine." Many thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
Vee_Mod
Community Support Moderator
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services