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

x
?
Solved

2x Terminal Services Disconnect

Posted on 2014-04-01
5
Medium Priority
?
1,232 Views
Last Modified: 2014-04-12
I have a client with the following:

1) Server 2008 R2 running SQL Databases

2) Server 2008 R2 Terminal Server that runs Lytec MD

3) Using 2x Application Server 10.6 Build 1544

4) Client workstation has 2x Client 11 build 1886 (Latest)

5) Terminal Server uses TerminalWorks TS Print for printing

All that being said, the user logs into the Terminal Server via 2x.  They use an application called LytecMD.  The user will click a button in LytecMD to print an encounter form for a patient and the program will disconnect.  This happens randomly but enough during the day to become very annoying.  Sometimes the users gets "The remote computer has ended the connection" from the 2x Client when they are disconnected.  When they are able to log back in they sometimes get "You are already logged into this practice on (SERVER). Please choose another practice."  It almost seems like a disconnect in transit.  The Terminal Server was given enough resources that it doesn't even yawn.  I've checked the Terminal Server logs and the Windows logs on the client machine and the only thing I have been able to find is where the user authenticates to log back in to the Terminal Server.  I have worked with the user and found that when they get kicked from the program the program closes on the Terminal Server but and there is no process running anymore.  I appreciate any suggestions on what should be checked to stop the disconnects.  If there are any questions I will answer to the best of my knowledge.
0
Comment
Question by:aando
  • 3
5 Comments
 
LVL 84

Expert Comment

by:David Johnson, CD, MVP
ID: 39970718
Are you using terminal services or 2x ? Why are you using a 3rd party tools ?
0
 

Author Comment

by:aando
ID: 39970721
We are using 2x based off the Terminal Services.  The 3rd party tool is for printing through Terminal Services due to widely used USB printers.
0
 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39970878
Not to be a Debbie Downer, but this sounds exactly like the problem you had a month or so ago with TSPlus, and as I mentioned at that time, if you try to bypass MS on terminal services, you'll have problems.

2x is actually not bad (I still prefer Citrix) but you can't *just* install it and expect things to work. Their application server is meant to either manage VDI scenarios or sit on top of a properly installed and configured RDS server with the MS RDS role and licensing server role installed.

The problem you describe is often what happens when a TS application is being run, but MS TS (now RDS) was not enabled and RDS licensing server and CALs were not installed. The underlying OS doesn't realize it is sharing resources and so different users clobber each other, and the application server (whether it is 2x or another) can't replace that core functionality.

Since you've had this problem with multiple products now, I think it is safe to say that you definitely need to revisit your underlying terminal server architecture. You need to get RDS deployed in a supported configuration, properly licensed, look for RDS events, and *then* deploy any advanced application services like 2x or Citrix XenApp/Receiver/etc.
0
 

Accepted Solution

by:
aando earned 0 total points
ID: 39984933
Thanks for commenting.  We have found that the issue was not an issue with the Terminal Services or the 2x.  What was happening was that because the application was being run through 2x we weren't seeing the real problem.  The connection to the Terminal Server would remain active after the application would crash.
0
 

Author Closing Comment

by:aando
ID: 39995860
Issue was not with Terminal Services but with application.  This was found after logging in directly to the server without Terminal Services.
0

Featured Post

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple.  The final solution for this task involved creating a custom text parser and then reading…
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

971 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