Link to home
Create AccountLog in
Avatar of jamills
jamills

asked on

Microsoft, Server 2003 R2, Terminal Services Conncection and/or manipulation in snap-in console

I am working with a MS Server 2003 R2.  It was setup as an application server using Terminal Services and Remote desktop. My workstations can no longer connect to it through remote Desktop. They all get the error:

The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to acceptnew connections
It is also possible that network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur, contact your administrator

So I logged into the the Server in question, and went into the terminal services manager to check on it.  It appears that everything is fine, everything was green.  There were no connections for me to log out or disconnect. So I went into the services.msc and checked to make sure the services were in fact runnig. They were, but when I right clicked on them to try and restart or stop and start everything was greyed out so that I could not perform any of those task. I also attempted the Net Start and Net Stop on it but could not perform this on them either.

I found that it is default that I can not start or stop these services.  So, I need to know what I can do to correct the connection issue.
SOLUTION
Avatar of dlangr
dlangr

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of jamills
jamills

ASKER

I found that it is by design also....
I have found that a reboot does not fix the problem, though it did happen once before in the past and the admin did a last known good config at start up and it fixed itself, Well at least up until now.
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of jamills

ASKER

I found what the issue was  but I will tell you what I did before I found the issue .Yes i was able to log into the server.... I could ping it. I tried  telnet and was unsuccessful, so I used VNC and was able to remote into it. I tried checking the virus and firewall software but all are configured to allow port 3389. I was stumped so I looked in the registry... The local admin, who was not available to speak to ( I work for a support company) had changed the default port to 3395, I guess to allow for remote access from outside for multiple servers and workstations. Once I realized this I was able to remote desktop in by pointing at that port. Then set up the client to all point there. Problem solved.Thanks for the responses though.