[THIN] Sasser patch b0rk me.

  • From: "Ryan Lambert" <rlambert@xxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Thu, 27 May 2004 08:55:04 -0400

I've seen some issues posted re: the Sasser patch and Terminal Services

After a client of ours applied the patch, they could no longer connect
to the Terminal Server with a device that did not already have a CAL
(not a cow, like I'm having right now). Seeing the event id "The
Terminal Server could not issue a client license."


I've deleted the Certificate, X509 Certificate, X509 Certificate ID
values in the registry with no go. I've also reinstalled and re-issued
licenses for Terminal Server Licensing. It shows them all as available,
and none issued out. TS License Server & Terminal Server are on the same
subnet, and have connectivity between eachother. Licensing *is*
installed on a Windows 2000 DC, and dcdiag brings back no errors. While
spending 4 hours on the phone with Microsoft yesterday, I still haven't
gotten the issue resolved... and we are continuing it today.


Has anybody seen any other possible resolutions other than the two
listed above?


I'm 22 years old, and going gray. Or bald. I'm not sure which one will
be first at this rate. :-)

This Week's Sponsor - Tarantella Secure Global Desktop
Tarantella Secure Global Desktop Terminal Server Edition
Free Terminal Service Edition software with 2 years maintenance.
Useful Thin Client Computing Links are available at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts: