A
artemidorus
Okay, so I'm coming here out of desperation, and I'll understand if
what I'm asking simply isn't doable, but I figured if anyone knows how
to work around this, you guys would... I have done some searching and
determined that a change in the behavior of XP as a result of the
installation of SP2 (see http://support.microsoft.com/?id=891559) is
causing my laptop to not fail back to NTLM to access network shares
when the domain controller is not available. This may sound
unusual--and, believe me, I know it is--but the scenario is not
terribly different from having a remote network with local member
servers, having the WAN link go down to the domain controllers (yes, I
know I should have a local [backup] DC--just ignore that for the
purposes of this scenario) and wanting to access shares on the member
servers. In XP's post SP2 default behavior, the system will not
failback to NTLM to allow the systems to access the local shares until
the domain controllers come back online. (Does anyone else find this
stupid?) Default behavior aside, does anyone know of any
policy/registry/config file/voodoo curse hack that I can use to get
around this behavior?
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 2/15/2006
Time: 6:11:08 PM
User: N/A
Computer: MYCOMPUTER
Description:
The Security System could not establish a secured connection with the
server cifs/mylocalserver. No authentication protocol was available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
what I'm asking simply isn't doable, but I figured if anyone knows how
to work around this, you guys would... I have done some searching and
determined that a change in the behavior of XP as a result of the
installation of SP2 (see http://support.microsoft.com/?id=891559) is
causing my laptop to not fail back to NTLM to access network shares
when the domain controller is not available. This may sound
unusual--and, believe me, I know it is--but the scenario is not
terribly different from having a remote network with local member
servers, having the WAN link go down to the domain controllers (yes, I
know I should have a local [backup] DC--just ignore that for the
purposes of this scenario) and wanting to access shares on the member
servers. In XP's post SP2 default behavior, the system will not
failback to NTLM to allow the systems to access the local shares until
the domain controllers come back online. (Does anyone else find this
stupid?) Default behavior aside, does anyone know of any
policy/registry/config file/voodoo curse hack that I can use to get
around this behavior?
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 2/15/2006
Time: 6:11:08 PM
User: N/A
Computer: MYCOMPUTER
Description:
The Security System could not establish a secured connection with the
server cifs/mylocalserver. No authentication protocol was available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.