Robert, We are getting that exact error. I have sent an email to all users telling them to switch their terminals off before they leave for the day. I'm going to see how it goes next week and if necessacery I'll raise a call with WYSE. I'm pleased that someone else is having the same problem though!=20 Many thanks, John -----Original Message----- From: Robert Barrett [mailto:RobertB@xxxxxxxxxx]=20 Sent: 17 April 2003 15:55 To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: WYSE Terminal Connection Error What is the actual "terminal connection error" you are getting? We are running Wyse 3360's and have basically the same type of setup with the exception of all connections being made on a 100Mb switched internal network. What we are finding is that the Wyse clients do not take well to being on while the servers are being rebooted. Most of our users have gotten to the point of knowing that when they arrive in the morning to logon and it gives them an error like "no server found", staying on the white Wyse screen (can't remember the proper name) they simply unplug the terminal and plug it back in and it is fine. Those users who faithfully turn the client off before going home have far less problems. -----Original Message----- From: Blackman, John [mailto:John.Blackman@xxxxxxxxxxx]=20 Sent: Thursday, April 17, 2003 3:48 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] WYSE Terminal Connection Error Hi guys, I am hoping someone might be able to point me in the right direction with this one. Scenario: Random users of the WYSE WT3125 terminal will attempt to connect with their terminal to a published desktop. The terminal is configured to connect to "Standard Desktop" using the ica server location. Ica is in DNS and round-robins with about 6 servers. Funny thing is though, the day after the terminal will work fine with no problems what so ever. It affects users on our construction sites (64K lines), our regional offices (2 - 4 mb lines), and here in our head office (100mb LAN). =3D20 All servers are rebooted in increments of 10 minutes from midnight. This issue occurs even when all servers are and running and accepting ICA client requests. Users very rarely turn off the terminal, just switch the monitor off. =3D20 We also have a lot of normal PC's running anything from Windows 95 to Windows 2000 running published apps via NFuse and never get any connection problems (unless something has kicked off). Servers: All servers are DELL 1650's, Windows 2000 SP2 + Hotfixes, MetaFrame XP FR2. Any advice would be very much appreciated. Regards, John John Blackman Network Administrator IT Incorporated ltd. [t] 01924 245245 [m] 07779 314 171 [a] Normanton Industrial Estate, Normanton, WF6 1RN [e] john.blackman@xxxxxxxxxxx [w] http://www.birse.co.uk Britain "is not worth an old shoe"=3D20 - Muhammed Saeed al-Sahaf=3D20 ******************************************************** This Week's Sponsor - ThinPrint Simply the best print solution for Microsoft Terminal Services=20 and Citrix Metaframe. http://www.thinprint.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************************** This Week's Sponsor - ThinPrint Simply the best print solution for Microsoft Terminal Services=20 and Citrix Metaframe. http://www.thinprint.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************************** This Week's Sponsor - ThinPrint Simply the best print solution for Microsoft Terminal Services and Citrix Metaframe. http://www.thinprint.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm