Terminal Services Remote App loses connection with local drives and printers
We deploy a hosted FileMaker based application to users to users using Windows Server 2008 Terminal Services Remote App.
It is much faster and more secure than users connecting directly to FileMaker Server using FileMaker Pro over the web. Instead of SSL secured data packets going back and forth over the web, only pixels, keystrokes and mouse clicks are sent across the web until the user wants to interact with local drives or printers. The user experience is enhanced as speed is significantly faster. Unfortunately, it is a Windows-only deployment. Mac users can connect via Remote Desktop, but that isn’t a solution for vertically deployed apps.
Sometimes, Remote App users loose connection with their local drives and printers. We have not been able to re-create the error internally. When logged-into the Remote App, we can not see local drives or printers, but Remote Desktop with the same credentials can. Weird.
Currently, our only resolve is to delete and re-create the Terminal Services User account using the same credentials.
We have seen patterns of this error in companies that run older database applications, primarily dBase and older versions of Act!. Have you experienced this? Please let us know!





One Comment, Comment or Ping
Posted by Surinder on Sep 6th, 2011 at 10:27 pm
dear Sir,
Faceing problem while accessing Remote App.. i loose my connection with local drives and printers.
Reply to “Terminal Services Remote App loses connection with local drives and printers”