Windows Server 2008 R2 Thread, Terminal Server intermittent error messages in Technical; Shamelessly stolen from my colleague Andrew Brookes on the RM Communities forum:
I'm hoping someone can help with ...
13th October 2011, 02:49 PM #1
Terminal Server intermittent error messages
Shamelessly stolen from my colleague Andrew Brookes on the RM Communities forum:
I'm hoping someone can help with this. Sometimes when a user logs on to one of our four terminal servers using the IGEL thin clients we have, the server will refuse to allow them to log on with the message:
"The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Other users may be able to log on."
The servers (which are running Win 2008R2) aren't stressed or overloaded. We've googled until our eyes bled, but every solution doesn't seem to apply or help. So far we've tried:
The suggestions here: http://social.technet.microsoft.com/...4aeece-4c91-4e 6d-9093-cc8ac0d5573c
Changing the Rss, autotuning and chimney settings on the NICs
Forcing disconnected sessions to close after one minute
Changing the print processors to winprint/RAW
Checking DNS and Replication (all working as expected)
The message is intermittent - it will affect a user one day, then not the next (although when it happens they will consistently be unable to log on for an hour or two). The servers automatically restart in the early hours, so I guess that could be clearing whatever is causing this temporarily. Some sites said Zonealarm can cause it, but we don't have that or any other firewall switched on.
I may have missed something but I think that's everything. It's very frustrating! If anyone has ideas please post and I'll try them out.
14th October 2011, 10:46 PM #2
Are they logging off properly ?
17th October 2011, 09:53 PM #3
We think the users are logging off correctly and sessions are ending correctly (none or few left hanging). We think we have found the solution for us. We use IGEL thin clients across the site and found that they were offering their smartcard port to the terminal server (although they didn't have one). We have disabled this and testing the result. Fingers crossed, 4 weeks in!
18th October 2011, 01:24 AM #4
- Rep Power
Have you checked how many free licenses you have? Are you using user or device licensing?
21st October 2011, 03:45 PM #5
Sorry for the late reply, we have plently of licenses left in fact over 50 and for reference we use the per device model. We are now however getting a different error:
Randomly when a user logins in it can take between 20-40minutes, nothing is wrong with DNS as this is setup the same for workstation and laptops, yet only the terminal servers have this issue. Anyone got any ideas?
By thesk8rjesus in forum Windows Server 2000/2003
Last Post: 5th June 2009, 04:30 PM
By flashsnaps in forum Windows
Last Post: 8th December 2008, 09:59 PM
By wellscs in forum Windows
Last Post: 23rd September 2008, 09:11 PM
By TechSupp in forum Wireless Networks
Last Post: 19th March 2008, 11:52 AM
By Cowman in forum Windows
Last Post: 11th October 2006, 05:20 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)