Re: cached credentials, vpn, failed authentication

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Dirk (ikke_at_ikke.com)
Date: 11/05/04 

Date: Fri, 5 Nov 2004 17:13:41 +0100

I use an hosts file so I can ping the server by name.
I don't use WINS and I did a test with an LMHOSTS (Q314108) file:

192.168.0.3 PDCNAME #PRE #DOM:DOMAIN_NAME
192.168.0.3 "DOMAIN_NAME \0x1b" #PRE

The LMHOSTS file didn't solve my problem.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> schreef in
bericht news:OIE2Rt0wEHA.3276@TK2MSFTNGP15.phx.gbl...
> Dirk wrote:
>> Hi,
>>
>> Client: Windows XP Pro SP2
>> Server: Windows 2000 Server SP4 (DC, AD)
>>
>> I logon to my laptop with cached domain credentials (Event ID: 5719,
>> Source: Netlogon). I start a VPN connection to my corporate network
>> with a Cisco VPN client. I can ping our servers,...
>
> By name? Given that you're describing trying to connect via IP address, it
> isn't clear. Are you using WINS? LMHOSTS?
>>
>> When I want to make a connection to a server share \\192.168.0.3\data
>> i see a window asking my domain credentials. I give these credentials:
>> DOMAIN\Username and the password (same as the cached domain
>> credentials). I receive an error message that: "this account is the
>> same as the one logged on to the system and that this account was
>> tried before to logon. There is no domain controller available to
>> validate this account."
>>
>>
>> At the same time i see these errors in the system log of the Windows
>> XP client:
>> Event ID: 40960, Source: LSASRV, Category: SPNEGO (Negotiator)
>> Event ID: 40961, Source: LSASRV, Category: SPNEGO (Negotiator)
>>
>> When i use other credentials to logon to this share
>> (DOMAIN\AnotherUsername and the password - NOT the same credentials
>> as the cached domain credentials) there is no problem. I don't see
>> any messages in the event log.
>>
>> When i logon to this laptop with a local account (no cached domain
>> credentials), start the VPN connection and make a connection to
>> \\192.168.0.3\data with DOMAIN\Username i don't have any problem
>> either.
>>
>> It seems that the problem is that the logon process only wants to
>> validate my account only one time. At start-up the domain controller
>> is not yet available and thus the system is using the cashed domain
>> credentials. When my domain controller is available (vpn is active)
>> the system doesn't want to validate my account anymore....
>>
>> Does anyone have an idea?
>>
>> Thanks in advance!
>>
>>
>>
>> Dirk
>
>

Relevant Pages

  • VPN logon problem
    ... a window asking my domain credentials. ... DOMAIN\Username and the password (same as the cached domain credentials). ... on to the system and that this account was tried before to logon. ...
    (microsoft.public.windows.server.networking)
  • RE: Notebook users locked out when off network
    ... logon with cached domain credential. ... Let us refer to the following steps to troubleshoot the issue: ... from your newsreader: microsoft.private.directaccess.partnerfeedback. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting via VPN Net Use g: \servernameshare asks for user name password on some machines
    ... when mapping drives via VPN (using a batch file) ... If the provide the credentials does it work? ... Are these users logging into their workstations with cached domain ...
    (microsoft.public.windows.server.sbs)