CAW Terminal Services

[ Follow Ups ] [ Post Followup ] [ Forum ]

Posted by Doug Pegg on April 07, 2014 at 15:27:46:

Another random problem.

Win2008R SP1 virtual server running terminal services with 1 CAW host.
27 sessions split across 7 workstations with multiple sessions (mix of WinXP and Win7). All sessions assigned using TSRALL and each session fires up an RDP connection.

Once or twice a day a session will 'lock up' i.e. seem to lose the cursor and keyboard response (sometimes the mouse responds and sometimes not). The only out from this is for the operator to 'X' the RDP screen to disconnect and we log on to the server and 'log out' the user so they can reconnect. If the user reconnects to a disconnected session, it returns to the original program and problem.
All of the other sessions for this machine continue running and the operator can switch between them OK. No program errors associated with this. The IT guy checked the processes for the user profile and said the xapplication was 'running away' and eating memory.

We are running another virtual server (Win2008R) with 20 full comet clients for about a year and have had no connection problems.
Any differences in full comet and CAW I should be checking?

Thanks in advance,


Follow Ups:

Post a Followup



What is the name of the main Signature System's Product?  


Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Forum ]