Had and still have the same problem with some Televideo TeleClients. Applied the hotfixs from M$ and that fixed majority of them but still had a few that this would happen on. The guys at Televideo had a server setup that I could make an RDP connection to that as soon as I hit it it would reset the license key on the unit and I was good to go. That may not help you but they didn't blame it on M$ and leave it at that. See if Wyse can do something like that for you. Bruce =20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Luchette, Jon Sent: Friday, May 07, 2004 9:09 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] single thin client license 6 MF XP FR3 servers Win2k sp4 on all 1 Win2k TS Licensing server/domain controller Wyse thin clients 3630's =20 Hello, =20 I am having a strange problem with just one of my WYSE 3630 thin clients that I believe is related to terminal services licensing. Whenever I try to connect over ICA from it, the session simply disconnects immediately upon communication with the Metaframe server. Whenever I try to connect over RDP from it, I get the following error message: "The remote computer disconnected the session because of an error in the licensing protocol." The metaframe server that accepts the request initially is getting event id's 1004 ' The terminal server cannot issue a client license' logged in the system log. Wyse has said that even though I am not having any other problems with any of my other 100 - 150 thin clients of the same build version and model, that this is not a problem with my thin client, but rather a Microsoft TSLicensing problem. They have directed me to install the following hotfixes from Microsoft on my TSLicensing server: Q825027and Q813508 and I did with no success (actually 813508 was fixed in sp4 so it detected it as already there and wouldn't let me install it). I've also tried stopping and starting the TSLicensing service and waiting 15 minutes, but still nothing. I don't know what else to do, I've reimaged the thin client a million times, set it back to factory defaults, changed the name, everything. The weird part is that it is only happening to this one thin client. Even knowing that I have tried both of the suggested Microsoft hotfixes on my TSLicensing server, and still nothing. Anybody got any ideas/had the same problem? =20 Thanks, =20 /jL =20 ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm