Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 134
  • Last Modified:

remote desktop services stopped working with no event viewer errors

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
AJNS
Asked:
AJNS
  • 4
  • 2
1 Solution
 
Spike99On-Site IT TechnicianCommented:
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
 
AJNSAuthor Commented:
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
 
Spike99On-Site IT TechnicianCommented:
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
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
AJNSAuthor Commented:
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
 
AJNSAuthor Commented:
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
 
AJNSAuthor Commented:
Found the answer myself and it was not really related to the product being discussed.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now