We've been running some WYSE S50 terminals for the past year or so. Everything works fine except our database client (CDS TIGER). Basically whenever it has an error, all the other terminal users start having database client problems until they all log off the client (not the terminal session) and log back in. All our other applications work without problems, unfortunately this program is central to our business process. I've complained to the vendor on numerous occasions without much luck. They claim to have plenty of other clients with terminals who don't experience any problems and essentially hint that it's a problem on my end. The terminal server is running win2k advanced server, and the sybase database is running on a w2k3 x64 standard server. I know we've got some terminal server guru's here, can anyone think of some things I might check? Possibly my terminal server settings need to be adjusted or something? At this point it's gotten bad enough we may have to stop buying terminals and get workstations instead, which isn't a cheery thought as they're twice as much and take way more maintenance. -- Chris Berry chris_berry@xxxxxxxxxxxxxxxxx Information Advisory Manager JM Associates "If we don't believe in freedom of expression for people we despise, we don't believe in it at all." --Noam Chomsky ***************************** New Site from The Kenzig Group! Windows Vista Links, list options and info are available at: http://www.VistaPop.com ***************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm