One thing I've noticed is that Windows tries to cache passwords. When they
first turn on their computer, they aren't generally connected to the VPN, so
they can't login normally at that point. Make sure they are still setup to
logon to the domain, even if they can't. Have them enter the correct
username and password at the login prompt, and just say "OK" when it
complains that it can't find a domain controller. Keep hitting OK until it
boots, without the domain controller. This will cache the correct
username/password combination, so that when it does try and connect to an NT
server, it will send the correct information. Also, as others have said,
make sure you have WINS or an LMHOSTS file working to allow them to find the
domain controller(s).
Hope this helps,
Travis Gamble
Systems Engineer
Attache Group Inc.
----- Original Message -----
From: "Jim Bond" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 1:18 AM
Subject: tough VPN question
> Hello,
>
> I'm trying to set up a IPSec between a PIX (branch
> office) and router (central office). All PCs at branch
> office share 1 ip address. IPSec seems to be working
> fine because clients can ping/telnet/email/map drives
> from/to central office. The problem is they can't
> logon NT domain. They can ping domain controller
> though.
>
> Any idea why they can't log on NT domain? (The
> machines were already added to domain)
>
> Thanks in advance.
>
>
> Jim
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products.
> http://shopping.yahoo.com/
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
