RDS 2008 R2 stop working but keep connexion actives

Hi everyone,

first of all, forgive my english i'm from Belgium,

here is my problem :

whe have a new client that had already his networks configurated by another society.
In the infrastrucutre there is a active directory server with roles file server and print server and another server RDS. The users in the office and outside the office connect on the RDS to work.

Sometimes, the RDS refuse new connections, the rdp can contact the server, i type my credentials, the connections is in configuration but it's look like a time out and can't connect.
with this happen, there is no error in the event viewer, no informations and the service is still workng.
The users who are connected can still working normally.

The error i can see in the RDS appear to be some error with the printer drivers and the printer redirection, there are 20 printers on the printserver, every user had 3 to 7 printer connected, and for the users who work at home they have they're own printer.

2 days ago i saw there was a GPO that desactivated the "EasyPrint", so i removed this GPO and the problem seem solved, there is no time out again since this modification, but the users can't print since...

i'm thinking of moving the printserver on the RDS and desactivate again the "EasyPrint", maye be a issue to solve the problem, can someone tell me if it's a good idea or have a solution to solve the problem.

Who is Participating?
Ratnesh MishraConnect With a Mentor Commented:
Firstly you need to delete the entry "TSxxx" as these are the once not required and causes many complexity . Dont delete anything else other than thses entry mentioned and shown in the pic . Do take backup of the registry entry before doing any deletion.
Make it sure that there is no user connected to the TS server while you perform this.
Once this is done we will thereafter work on EasyPrint part.
Ratnesh MishraCommented:
Had you checked with "orphan ports" , if its increasing or high in number in registry .You may face such situation. Registry location for the orphane oprts are :-

The entry of the key reference count should be 0 and there should not be any key unless any active RDP session is going on.
This increases because of abrupt closure of RDP session [not logging off].

This is one of the method.

As you have already mentioned that the issue gets resolved by disabling Easy print option from the group policy. So need to understand what kind of setup and group policies you have created or is set up.
GPP is one of the tool which you can use for making printing preferences in better way for all the users.
7-8 printers for a user seems odd to me in an RDP session. What kind of infrastructure you are supporting. If users are using network printer you can give one of the default printer used for printing not all as this increases load while loading profile in RDP session.
Even you can give re-directed printer as only printer to the user .
Are you preferring Clint side rendering or not .
Honestly , it includes much of information to make a redesigned model in order to get things working in smooth way. However at present I would suggest to go and delete orphane ports and see if it helps you or not.

Based on the question , moving printer server to RDS server is not a good idea but even not a bad idea. I will suggest if load on RDS is not high then you may transfer the load else it may consume your resources.
Neo-NetworkAuthor Commented:
Thank you for your response,

the registery look like this, is it normal ?

Enabling the easyprint temporarily resolved the problem, the remote connexion stopped to work this morning...

I'm according with you for this many printers, but there is some laptops and the users have the printers at work and the printer when they are outside the enterprise.
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.

Neo-NetworkAuthor Commented:
Thanks for your reply,

i disconnect all users, cleaned the registery of all those TSXXX, but after a few hour, the same problem.
Neo-NetworkAuthor Commented:
Hi, i solved the problem by restraining the redirection of the printers, i only authorized the redirection of the client's default printer, since that the server didn't stop again.
Neo-NetworkAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Neo-Network's comment #a39876175

for the following reason:

it's not a final solution
Neo-NetworkAuthor Commented:
it helped me to clean the registry
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.

All Courses

From novice to tech pro — start learning today.