We had this problem for years under W2K and MF XPe. Turns out our email system replaced msgina in the registry so that we could have single sign-on. I disabled the email single sigh-on service and put msgina back to its default location. Basically, any developer can replace (actually chain) msgina with their own gina. When they do this, they are supposed to pass along all the info to msgina. In our case, something was wrong with the 3rd party gina and it never passed credentials along. adam "Stratton, Doug ISMC:EX" <Doug.M.Stratton@ To gov.bc.ca> <thin@xxxxxxxxxxxxx> Sent by: cc thin-bounce@freel ists.org Subject [THIN] need some help 06/20/2007 05:05 PM Please respond to thin@xxxxxxxxxxxx g We are having some serious problems with servers gradually over the day getting into a state where when you try to logon you can put in your credentials and it starts to log you on but gets to a blue screen and just sits there. We can, in some cases, remote manage and view part of event logs but hangs most times. Our environment configuration is: w2k3 sp1 (+bunch of patches) PS3 with 2005.04 but not set to PS4 and a bunch of patches Office 2003 sp1 We think this has something to do with printers as calls usually come in first saying printing is not working. Users can’t do print preview and printing stops working. Most of our users are using Lexmark printers of some sort, networked. We have been told that the printer server guys are updating their print servers from windows 2000 to w2k3. Don’t know if it is related. At this point the only option we can come up with is SP2 the servers + patches and R03. Anyone got any less dramatic things that might help? Regards, Doug Stratton, Shared Service BC Service Desk Email: 77000@xxxxxxxxx Service Desk Tel: (250)387-7000