[THIN] Re: Domain not Available - Logon on freezes

  • From: "Jeff Durbin" <techlists@xxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 31 Mar 2004 14:03:01 +1200

Check your domain controllers event logs for authentication failures. I had
a customer with a similar problem. It's been a while, but I think it was the
result of a some process that was trying to authenticate and failing so many
times that it hung RPC. Might have had to do with a trust. Just found my
field notes from the issue and there might be some helpful information there
- I'll send them to you off-list.

JD

> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx 
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Monahan, Thomas
> Sent: Wednesday, 31 March 2004 12:49 p.m.
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Domain not Available - Logon on freezes
> 
> Hi,
> 
> We are having a bit of trouble at the moment with some users 
> a/c crashing out servers. If anyone has experienced this or 
> can give some pointers it would be most appreciated.
> 
> The long and short of the problem is as follows:
> 
> *     A user launches a citrix published application (usually 
> Outlook XP)
> *     The application freezes on him, (Outlook immediately, other apps
> seem to freeze when File-Print is selected). 
> *     Future users that try to log into that server get 
> either a "Domain
> not available" or the logon window freezes after an 
> authentication attempt.
> *     Local accounts get past authentication but get no further than
> "loading personal settings" message box. 
> *     Console login also fails.
> *     The only solution so far has been to reboot the server using a
> remote shutdown command under local Admin privileges. 
> Attempts to kill and restart netlogon services have failed.
> *     When this occurred in the past, it was linked to a Nav antivirus
> update. This Nav antivirus update had no apparent link with 
> the servers that were being crashing. No plausible reason for 
> this link has yet been discovered. The only conclusion that 
> can be drawn from this is that it must only be a coincidence, 
> although the times of update -> crash have tallied.
> *     Previous occurrences of the crash were finally fixed for the
> previous month when a printer driver that seemed to be a 
> common denominator in crashing was removed from the servers. 
> There doesn't seem to be any obvious link to a particular 
> printer driver this time.
> *     Problem has been replicated on a fully patched server 
> (except sp4
> and IE6) via Windows Update.  
> *     Problem has been replicated with a RDP desktop session. Crashing
> does not occur until Outlook (or other application) is 
> started. With RDP the application freezes, explorer shell 
> freezes. Task Manager functions fine.
> Killing Explorer shell and restarting it has no benefit.
> *     If the print spooler is stopped, we have not been able 
> to replicate
> the crashing.
> *     If we remove printers completely from user profile, we 
> have not been
> able to replicate the issue.
> *     A second account which was a copy of the original a/c 
> was given to
> user, this a/c also ended up crashing servers. 
> *     The printers that are assigned to this user are not exclusive to
> him. Other users have the exact same combination of printers 
> without any trouble.
> *     It appears to be only one (at most two) user(s) at a 
> time that has
> the ability to cause crashing; it is not necessarily the same 
> user at each occurrence that has the ability. 
> *     With previous occurrences, after playing around 
> (resetting profiles,
> removing groups, adding groups etc) with the users profile 
> the problem stopped, and the account could be given back to 
> the user. This time the account can not be given back to the 
> user, as it consistently crashes servers with printers configured.
> 
> Does this ring any bells with anyone? 
> 
> Cheers,
> Tom
> 
> 
> 
> 
> ***********************************************************
> The information contained in this e-mail is intended only for 
> the individual to whom it is addressed. It may contain 
> privileged and confidential information. If you have received 
> this message in error or there are any problems, please 
> notify the sender immediately and delete the message from 
> your computer. The unauthorised use, disclosure, copying or 
> alteration of this message is forbidden. Neither United 
> Utilities PLC nor any of its subsidiaries will be liable for 
> direct, special, indirect or consequential damage as a result 
> of any virus being passed on, or arising from alteration of 
> the contents of this message by a third party.
> 
> United Utilities PLC (England and Wales No.2366616) 
> registered office: Dawson House, Great Sankey, Warrington, WA5 3LW.
> ***********************************************************
> 
> ********************************************************
> This weeks sponsor Emergent Online.
> Emergent OnLine is the leading server-based computing 
> consulting integration firm in the nation. Emergent OnLine 
> delivers expert consulting services you can depend on.
> http://www.go-eol.com
> **********************************************************
> 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 weeks sponsor Emergent Online.
Emergent OnLine is the leading server-based computing consulting integration 
firm in the nation. Emergent OnLine delivers expert 
consulting services you can depend on.
http://www.go-eol.com
**********************************************************
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

Other related posts: