• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 963
  • Last Modified:

Terminal Server Users Disconnected

We recently migrated one of our clients from dual load blanced Windows Server 2003 Citrix/Terminal Server, into three load balanced Windows Server 2008 Terminal Servers.  The Citrix component is installed but not being, discontinuing Citrix this year.  They have been migrated for a solid week, and today they are starting to get random disconnects.  It was just a few users this morning and then all users that were logged into Server 1 were disconnected.  The load balance feature has been working well at login but the local dropped users didn't reconnect to their orphaned session, the ones working from remote did.  

Any input is appreciated!
0
sqlBarth
Asked:
sqlBarth
1 Solution
 
ajpowell74Commented:
Are you getting error messages on the affected Terminal Server?
Or are they showing that the users are successfully logging in and then being immediately logging off?
0
 
sqlBarthAuthor Commented:
On the affected TS I found a System Event Log error stating:

"The Remote Desktop Services service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service."

This error was logged about a minute before I received my first email on the matter.
0
 
Robert Sutton JrSenior Network ManagerCommented:
Are you using FQDN or Netbios?
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.

 
sqlBarthAuthor Commented:
It was a combination of both.  The external users were using FQDN and when I test that internally I reconnect to my abandoned session every time.  The internal users were using netbios and are failing to reconnect to their abandoned sessions.  It's just about closing time and I'm going to make a sweep through the office and correct that.

I still have the qustion as to why users are getting disconnected from their sessions.
0
 
Robert Sutton JrSenior Network ManagerCommented:
I see, you can try this as a workaround:
The network shares on Windows 2008 R2 (working as a Terminal Server) are dropping randomly. Using FQDN does not always work. It is going in a cycle. After a fresh reboot, \\servername\Share works. After a while, it does not work and we need to use \\servername.domain\Share or \\ip-address\share. Then after a while, that does not work again, and we have to go back to \\servername\Share.  


So for the time being, just put 2 lines (instead of 1) in the drive mapping scripts in order to workaround it.


 net use U: \\servername.domain\Share
 net use U: \\192.168.1.1\Share

0
 
sqlBarthAuthor Commented:
I think we are drifting a part on this topic.  When I say disconnected sessions, I don't mean mapped drives to network shares.  I'm referring to their entire terminal server login session is disconnected.  Forcing them to log back into the server.  

Does this make sense?  We will be applying some changes to the network adaptors tonight.  Specifically turning off any network offload features.  We've seen these types of problems before when trying to use a non-legacy network adaptor on a pre-Windows 2008 guest O/S in a hyper-v environment.  

I should also mention this is a hyper-v environment.
0
 
sqlBarthAuthor Commented:
No solution was provided.
0
 
cplitCommented:
Just wondering if you ever resolved this issue (full Session Disconnects) we are having a similar issue and I am trawling for any help i can get!
0

Featured Post

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.

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