[483] in Kakapo Windows Team

home help back first fref pref prev next nref lref last post

Re: [Kakapo] In need of some second-tier Windows help on a case

daemon@ATHENA.MIT.EDU (Kyle Pope)
Thu Sep 23 17:02:42 2004

Message-Id: <5.2.1.1.2.20040923170028.0227ace8@po10.mit.edu>
Date: Thu, 23 Sep 2004 17:01:54 -0400
To: Oliver Thomas <othomas@mit.edu>, kakapo@mit.edu
From: Kyle Pope <ndpope@mit.edu>
In-Reply-To: <9BED939C-0DA2-11D9-AD2E-000A95AF06BA@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Errors-To: kakapo-bounces@mit.edu

         Is the user profile downloading from AFS correctly?  I had a 
similar situation in which a temp user folder was being created instead of 
the user's profile, so the browser was not letting me save the certificate 
information to the temp profile.  Just a thought.

                         Kyle




At 04:53 PM 9/23/2004 -0400, Oliver Thomas wrote:
>We have run into this problem on two machines that are members of a 
>Windows domain, although I believe neither is a member of WIN.MIT.EDU. (We 
>are currently waiting to hear back from the client with an actual host 
>name and detail on the machine--all we know is that it's in a Windows lab 
>on the 4th floor of building 3.) It also occurs on our call center 
>machines (Win2K), which are members of a stand-alone domain.
>
>The problem occurs when trying to get certificates from IE. The error is 
>one generated by the MIT certificate server:
>
>"Your browser failed to properly generate a key. Make sure you are using a 
>supported browsers version. Under certain circumstances your installation 
>of Windows may be damaged or not have a critical security patch. In 
>particular we have seen this problem crop up on systems that do not have 
>Microsoft patch Q323172 (Windows 2000 and Windows XP). The patch may 
>either be obtained via Microsoft Update, or the following URL 
>http://www.microsoft.com/windows2000/downloads/critical/q323172/."
>
>We did of course check the obvious: both machines are up to date on 
>security patches. My current theory is that there may be a container 
>setting that can cause the same error that we used to see with the old 
>patch problems. I figured someone on Kakapo might know of the top of their 
>head.
>
>Thanks,
>
>Oliver
>
>https://casetracker.mit.edu/caset/findcasecon.do?a=1&case_id=666534
>
>_______________________________________________
>Kakapo@mit.edu
>http://mailman.mit.edu/mailman/listinfo/kakapo

_______________________________________________
Kakapo@mit.edu
http://mailman.mit.edu/mailman/listinfo/kakapo

home help back first fref pref prev next nref lref last post