Solved

remote desktop services stopped working with no event viewer errors

Posted on 2014-11-03
6
126 Views
Last Modified: 2015-01-19
I have a small office running 2008 r2. This is their only server and is running AD, file and print, DHCP etc. They purchased a line of business application that required thin clients so RDS was added.

It worked perfectly for a couple years but now all of a sudden you can not connect to the server using RDP. The thin clients fail as well as RDP clients. Everything else is working fine, desktop users can still login and access the server, applications on the server work.

There are zero events in the event viewer that have to do with remote desktop services. The only one I found was a vss error for writerName TermServLicensing but I think I resolved that one and I don't think it would prevent logins to rds.

I checked the licensing server and it does have an error that is has zero licenses but we only use five thin clients and five issues licenses so that should be fine.

I have saved and cleared the logs and when I attempt to connect and fail there are no new log entries to show why. Any ideas where I can look for further information on troubleshooting this?
0
Comment
Question by:AJNS
  • 4
  • 2
6 Comments
 
LVL 16

Expert Comment

by:Spike99
ID: 40420264
Do the users get any sort of error when their attempts to connect via RDP fail?

Which model thin client are you using & what's the OS or firmware version?
0
 

Author Comment

by:AJNS
ID: 40421572
Just a generic RDP not available. They are using wyse s10's. I tested it as well using remote desktop from various windows machines and it won't connect either. Just the usual error that the server is not responding, verify it is on....

Also to add to this I can remote desktop from the server to another server and I can connect if I remote from the server to itself using 127.0.0.1

Still nothing at all in the event viewer related to this.
0
 
LVL 16

Expert Comment

by:Spike99
ID: 40421935
Can you ping the server from the Thin Clients or PCs that are having trouble connecting?

The RDP protocol uses port 3389.  Running a network analyzer on one of the PCs might help you pinpoint the issue (like Wireshark).
0
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 

Author Comment

by:AJNS
ID: 40421950
Haven't tried a ping from the thin clients but definitely can from the desktops. In fact they can log into AD and access shares on that server just fine. Everything except RDP works.

I'll check if port 3389 is getting to the server, I know it can leave the server because I can RDP out of the server. I'll get back to you.
0
 

Accepted Solution

by:
AJNS earned 0 total points
ID: 40549080
I apologize for the delay here. I didn't even realize this wasn't closed.

What solved the problem was rebooting a switch. It had nothing to do with the RDP server.
0
 

Author Closing Comment

by:AJNS
ID: 40557294
Found the answer myself and it was not really related to the product being discussed.
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Let’s list some of the technologies that enable smooth teleworking. 
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now