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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
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
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

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
willettmeisterCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.