Terminal Services not working on a W2K3 R2 server

I am running a Exchange 2K7 on a Windows Server 2K3 R2 server, after reboot it last week; I cannot connect it with Remote Desktop Connection from my laptop.

It might work after I reboot it again but is it possible to fix it without rebooting?  I tried to reset the RDP-Tcp (Listener) in Terminal Service Manager on this server but no help.  Now, after reset the Listener, I cannot see it back.

If I tried to connect to this server from my Remote Desktop Connection, I got the message (see attached image)

thanks!
rdc.GIF
LVL 1
KANEWONGAsked:
Who is Participating?
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.

shairozanCommented:
If you have console access to the machine, try doing the following:

1. Click start
2. Click run
3. Enter "services.msc" and hit enter
4. Scroll down and find "Terminal services"
5. Select it and hit "Restart service"
6. Right click on that entry and hit properties
7. Make sure "startup type" is set to automatic
8.Click the third or "Recovery" tab
9. Set the first three options to "restart the service"
10. click Ok

This makes sure that terminal services starts with the server and that in it will automatically attempt to restart if a failure occurs.
0
Glen KnightCommented:
I would also try simply right clicking my computer select properties then remote turn off remote desktop, click apply then turn it back on and click apply.

Uninstall any virus software on the computer? Disable the firewall does that resolve it?
0
AkhaterCommented:
it might be as simple as an update that was installed turned on the firewall on your windows box and that's what is blocking the RDP
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Glen KnightCommented:
Indeef and disabling RDP then re-enabling it should put the exceptions in.
0
shauncroucherCommented:
You won't be able to restart Terminal Services in 2003, it isn't possible.

Look in event log on 2003 server, any errors? Can you telnet to port 3389 from your laptop? Can you RDC to anywhere else from your laptop?

Shaun
0
KANEWONGAuthor Commented:
Hi;

I was trying to follow the steps given by shairozan but I cannot restart the Terminal Services, it does not let me to restart.
0
AkhaterCommented:
yea Terminal services services is not a service you can stop at start.

Can you make sure the firewall is off on your windows box ?

i take it that the TS service is started
0
Glen KnightCommented:
Have you tried what i suggested?

As shauncroucher said you will not be able to restart the service, this is normal
0
KANEWONGAuthor Commented:
I cannot telnet to port 3389 on the server.  It said "Could not open connection to the host..."

I can Remote Desktop to all other server, just this one because I was rebooting it last week.  May be some service was not starting up properly.
0
AkhaterCommented:
If you have a firewall blocking then you won't be able to telnet nor RDP.

why don't you just check up the Firewall thing or do what :demazter told you to do
0
KANEWONGAuthor Commented:
The firewall is not enable on this server.
There is no anti-virus software installed.

I also tried to disable/enable the RDP but no help either.
0
Glen KnightCommented:
On the server navigate to:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

find the key called fDenyTSConnections and make sure it is set to 0 (zero)
0
shauncroucherCommented:
Event log?

Do you have alternative access to the server? Can you access physically at the moment / do you have VNC or some other software installed? If so, can you check event log / can you try doing telnet from server to itself on port 3389 and then run this command:

netstat -anbp tcp > c:\ports.txt

Search ports.txt for 3389 - anything?

Shaun
0
KANEWONGAuthor Commented:
Yes, it is zero

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections
0
Glen KnightCommented:
Have you tried restarting it?

What did the netstat command bring back?
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
Glen KnightCommented:
Has the server by any chance got 2 network cards?
0
KANEWONGAuthor Commented:
Hi;

I ran the netstat -anbp tcp command but no 3389 there.

I have not rebooted the server yet until end of the day, that's why I tried to find a solution to fix it without rebooting the server.
0
shauncroucherCommented:
I think you may find yourself out of luck here.

Event log? Any errors there at all?

What is the state of the services, open services.msc --> Sort by startup type --> For all those that have startup type of Automatic, is the status Started? Any exceptions, if so, list them here.

Does a restart always fix this error? How long has this happend for? Any new software installed recently?

Shaun
0
KANEWONGAuthor Commented:
1. no new software installed recently, just did a restart last week.
2. no error found in event logs.
3.
                                                                                  Status                   Type
Remote Access Auto Connection Manager               Stopped               Manual
Remote Access Connection Manager                        Started                 Manual
Remote Procedure Call (RPC)                                     Started                 Auto
Remote Procedure Call (RPC) Locator                       Stopped                Manual
Terminal Services                                                       Started                 Manual

I compared other servers, the Remote Access Connection Manager on the other working server is stopped with Manual.
0
KANEWONGAuthor Commented:
The Terminal Services resumed to work after reboot server.
0
KANEWONGAuthor Commented:
expect to solve it without rebooting server.
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
Exchange

From novice to tech pro — start learning today.

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.