Re: Domain Issues XP

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 03/03/04


Date: Wed, 03 Mar 2004 01:59:46 GMT

Probably a security option incompatibility. Check your Domain Security Policy, Domain
Controller Security Policy and the Local Security Policy on the domain controllers to
make sure smb signing is not required [digitally sign communications -client/server]
as that can cause problems with XP boxes, and that the XP boxes are not requiring it
in their security settings. You may temporarily disable all the settings on the
domain controllers to see if it helps. Also you do not want "additional restrictions
for anonymous connections" to be no access with without explicit anonymous
permissions and Lan Manager Authentication levels need to be compatible on the domain
controllers. --- Steve

"anonymous" <anonymous@discussions.microsoft.com> wrote in message
news:5a8501c400b1$85485ce0$a301280a@phx.gbl...
> No thoughts? :(
> >-----Original Message-----
> >Hello,
> >
> >I am getting quite a few new events logged:
> >______________________________________________
> >Event Type: Warning
> >Event Source: Srv
> >Event Category: None
> >Event ID: 2022
> >Date: 3/1/2004
> >Time: 9:59:10 AM
> >User: N/A
> >Computer: xxxxxxx
> >Description:
> >The server was unable to find a free connection 7 times
> >in the last 60 seconds. This indicates a spike in
> >network traffic. If this is happening frequently, you
> >should consider increasing the minimum number of free
> >connections to add headroom. To do that, modify the
> >MinFreeConnections and MaxFreeConnections for the
> >LanmanServer in the registry.
> >_________________________________________________________
> >
> >Event Type: Warning
> >Event Source: LSASRV
> >Event Category: SPNEGO (Negotiator)
> >Event ID: 40961
> >Date: 3/1/2004
> >Time: 9:58:43 AM
> >User: N/A
> >Computer: xxxxxxxx
> >Description:
> >The Security System could not establish a secured
> >connection with the server cifs/xxxxxxxx. No
> >authentication protocol was available.
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >_______________________________________________________
> >Event Type: Error
> >Event Source: AutoEnrollment
> >Event Category: None
> >Event ID: 15
> >Date: 3/1/2004
> >Time: 9:54:25 AM
> >User: N/A
> >Computer: xxxxxxxxxxxxx
> >Description:
> >Automatic certificate enrollment for local system failed
> >to contact the active directory (0x8007054b). The
> >specified domain either does not exist or could not be
> >contacted.
> > Enrollment will not be performed.
> >
> >Theres events are happening on all my XP Pro. boxes. But
> >nothing seems to be effected on my Win2k boxes....??
> >
> >
> >Any suggestions?!?!
> >
> >[B]Thanks in advance.[/B]
> >
> >.
> >



Relevant Pages

  • Re: Domain Issues XP
    ... Not like I just added a few XP boxes to my LAN ... >Controller Security Policy and the Local Security Policy ... >domain controllers to see if it helps. ...
    (microsoft.public.win2000.networking)
  • Re: Auditing Account management events
    ... If you have configured auditing of account management in Domain Controller ... Security Policy, check the Local Security Policy of your domain controllers ...
    (microsoft.public.win2000.group_policy)
  • Re: Restrict Anonymous Key
    ... It probably is configured in the security policy for the domain controllers and ... Go to Domain Controllers Security Policy/security ... equivalent to the registry setting of 1. ... We have Windows XP and Windows ...
    (microsoft.public.win2000.security)
  • Re: Problems since SP1 (Server 2003) - 2nd request for help
    ... then run a gpupdate /force. ... 4.If you open up the Local Security Policy, ... Is your server still in the Domain Controllers OU, ... Remote Desktop Users group have this right. ...
    (microsoft.public.windows.terminal_services)
  • Re: Domain Issues XP
    ... Not like I just added a few XP boxes to my LAN ... >>Controller Security Policy and the Local Security Policy ... >>in their security settings. ... >>domain controllers to see if it helps. ...
    (microsoft.public.win2000.networking)