Remote Desktop -- Unable to connect

Since restarting after patching firmware / drivers for a server's RAID controller, I've been unable to connect with the Remote Desktop Connection Client from any computer.  The Windows Firewal is disabled and the "Enable remote Desktop on this computer" setting within "Remote" properties of "My Computer" is checked, but grayed out.  The console can be accessed using other remote applications (Dameware).
benchmarkITAsked:
Who is Participating?
 
willettmeisterConnect With a Mentor Commented:
RDP still uses the Terminal Services Service.  Chances are that you need to reboot the server but something more may be going on.  Give it a reboot though and see if that starts the service.
0
 
jckingjcCommented:
Hi benchmarkIT,

What error messages you got? I had same problem before. It is more like your Terminal Services stops.

Press "Start" go "Run" and check your "Terminal Services" it sould turned on. Try to restart your your sevices or just restart your machine.

Good luck.
0
 
jckingjcCommented:
Hi benchmarkIT,

Sory...Type in services.msc in your "run" window to check your services.....
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
benchmarkITAuthor Commented:
Sorry, I forgot to mention the error message.  Remote desktop Connection client errors out almost immediately (very little delay) after choosing 'connect' with the following message: This computer can't connect to the remote computer.  Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.  

Pings to the machine receive replies.
The "Terminal Services" service shows "Started" with a Startup Type of "Manual", but doesn't give options for Stop, restart, etc.
0
 
willettmeisterCommented:
Run netstat -n from the command line of the server and ensure that port 3389 is listening.  Then use a port scanner like nmap from a client to ensure that the port is opened outside.  http://nmap.org/zenmap/  

Just runa quick scan against the ip in nmap and if you need help reading the output post it here.  If it says that it is filtering ports you have a firewall blaocking something.  If it says closed the the port is not enabled.  Double check your services.
0
 
Valentin NikolovSystem and Network AdministratorCommented:
HI  

1.try RDP connection from the server to the same server

2.you can preinstall terminal server ,deinstall first and then install it
from add/remove wind

3.check terminal the server licensing server. do you hava available license


luck
0
 
Valentin NikolovSystem and Network AdministratorCommented:
you can restart teminal server with

net stop termsrv
net start termsrv        

comands
0
 
benchmarkITAuthor Commented:
port 3389 was not listed in the results of a netstat -n.  I did not run the port scanner from a client as I assume we now know the result if the server isn't listening at that port...
Net Stop Termsrv gave an error -- "The specified service does not exist".  But a Net Stop "Terminal Services" gave a more useful error:  "The requested pause, continue, or stop is not valid for this service."  This seems to match up with what I see in the Services MMC -- the options for stop, pause, etc. are grayed out.
RDP from the same server was unsuccessful with an error similar to that shown on the workstation clients.
Terminal Server components are not currently installed on this server.  I'm not  looking to install the "Terminal Server" Windows component that makes this computer accessible by multiple users.  I only need to use RDP services for administration of the server
0
 
benchmarkITAuthor Commented:
I was able to get a reboot in early this morning -- and it looks like that fixed the problem.  Any idea what caused this, or how to keep it from happening again?
0
 
willettmeisterCommented:
Terminal services has this problem from time to time when a user does something while connected via RDP that causes an exception to the server.  It is hard to tell after the fact exactly what happened usless it was caught by the event log.  I would check teh event log and see if you have an application errors in the past day or so.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.