oo.com> cc:
> [EMAIL PROTECTED]
> Sent by: Subject: tough VPN
> question
>
cc:
[EMAIL PROTECTED]
Sent by: Subject: tough VPN
question
nobody@groups
tudy.com
ary 22, 2001 2:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Still doesn't work: tough VPN question
>
>
> Are you sure the PDC has a route back to the VPN client?
>
> "Justin Menga" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[
PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Still doesn't work: tough VPN question
>
>
> Hello,
>
> Thank you guys for the help. Unfortunately, I tried to
> put LMHOST file, still doesn't work. We use WINS and I
> can ping
Hello,
Thanks a lot for all the info, you guys are great!!!
Problem is solved by doing:
1. Use PIX internal ip address as match address
2. Create nonat for traffic to central router
I have 2 more questions (sorry, couldn't find answer)
1. How do I do redundancy between branch office (2
PIXs) an
Are you using overload and port address translation with the working config? I
undertsnad the issue to be with the VPNs ability to utilize layer-4
translations. I think the VPN will succeed with a singular address-based
translation.
Curtis
Jim Bond <[EMAIL PROTECTED]> wrote:
Hello,
Let me re-
lto:[EMAIL PROTECTED]]
Sent: Monday, December 11, 2000 12:18 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: last try: tough VPN question
Hello,
Let me re-describe the situation:
Central office 7100 router, site office PIX (NAT
overload 1 public ip address), IPSec tunnel is
establised,
ts is supported (though I could be wrong on that).
Have you tried the LMHOSTS approach?
Scott
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Jim Bond
Sent: Sunday, December 10, 2000 6:18 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: last try: t
Hello,
Let me re-describe the situation:
Central office 7100 router, site office PIX (NAT
overload 1 public ip address), IPSec tunnel is
establised, clients at site office can't logon NT
domain but can do everthing else.
Today, I replaced the PIX with a 3620 router (same
IPSec setup), everythin
riday, December 08, 2000 6:30 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Still doesn't work: tough VPN question
Hello,
Thank you guys for the help. Unfortunately, I tried to
put LMHOST file, still doesn't work. We use WINS and I
can ping domain controller
D]]On Behalf Of
Travis Gamble
Sent: December 7, 2000 9:05 PM
To: Jim Bond; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: tough VPN question
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 t
wick" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Still doesn't work: tough VPN question
>Date: Fri, 08 Dec 2000 17:56:25 -
>
>How about getting a test machine and running nbtstats to test the WINS
>resolution?
>
> >>>Brian
>
>
>
I beg to disagree with you. I can certainly telnet, ftp and ping to any
NETBios name on my network.
-Original Message-
From: Benjamin Walling [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 08, 2000 9:21 AM
To: [EMAIL PROTECTED]
Subject: Re: Still doesn't work: tough VPN que
esn't work: tough VPN question
Name resolution is exactly what WINS does! It maps Netbios names to IP
addresses. Windows clients resolve names to IP addresses using a number of
criterion, and depending on what kind of node they are (H;B;P;M)the order
that they search services and files dif
How about getting a test machine and running nbtstats to test the WINS
resolution?
>>>Brian
>From: "Benjamin Walling" <[EMAIL PROTECTED]>
>Reply-To: "Benjamin Walling" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Still doesn&#x
ge
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I beg to disagree with you. I can certainly telnet, ftp and ping to any
> NETBios name on my network.
>
>
>
> -Original Message-
> From: Benjamin Walling [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 08,
ED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Still doesn't work: tough VPN question
Hello,
Thank you guys for the help. Unfortunately, I tried to
put LMHOST file, still doesn't work. We use WINS and I
can ping domain controller using name so I don't think
it's naming issue.
-
From: Benjamin Walling [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 08, 2000 12:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Still doesn't work: tough VPN question
Yes, WINS resolves NetBIOS names to IP addresses, but only for Windows
networking functions. It is not used for ping, ftp, t
> The way you have written makes it sound as if I did not have DNS and I
> did a ping, telnet, or ftp by name that it would not work, and that is
> not the case.
That is not what I intended. If you do a ping, it is not a test of whether
WINS is working because there are other ways to resolve a n
ROTECTED]]
> Sent: Friday, December 08, 2000 9:21 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Still doesn't work: tough VPN question
>
>
> Yes, WINS resolves NetBIOS names to IP addresses, but only for Windows
> networking functions. It is not used for ping, ftp, telnet, etc. It is
min Walling'; [EMAIL PROTECTED]
Subject: RE: Still doesn't work: tough VPN question
I beg to disagree with you. I can certainly telnet, ftp and ping to any
NETBios name on my network.
-Original Message-
From: Benjamin Walling [mailto:[EMAIL PROTECTED]]
Sent: Friday, Decemb
Jim, here is a link to an MS KB article outlining the requirements for
domain traffic over a firewall. Open these ports on the firewall to pass
the domain traffic.
Here's what happens: a client comes up and broadcasts for an available DC.
This also happens over TCP/IP, even if TCP/IP is the on
gt;From: "Benjamin Walling" <[EMAIL PROTECTED]>
> >Reply-To: "Benjamin Walling" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: Re: Still doesn't work: tough VPN question
> >Date: Fri, 8 Dec 2000 08:27:04 -0500
> >
>
.
> >
> > In LMHOSTS. :
> >
> > (ip address) (Netbios name) #PRE #DOM:(domain name
> > if domain controller)
> >
> > Also, to refresh without rebooting the PCs, "nbtstat
> > -R"
> >
> > Hope this helps!
> >
> > Scott
> >
> >
#PRE #DOM:(domain name
> if domain controller)
>
> Also, to refresh without rebooting the PCs, "nbtstat
> -R"
>
> Hope this helps!
>
> Scott
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Jim Bond
&g
Altiga VPN Client works with Pix 5.2
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Sam Munzani
Sent: December 7, 2000 4:38 PM
To: Manishkumar Patel; Scott Morris; Jim Bond; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [RE: tough VPN question
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 o
-R"
> >
> > Hope this helps!
> >
> > Scott
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Jim Bond
> > Sent: Thursday, December 07, 2000 1:19 AM
> > To: [EMAIL PROTECTED]
&g
To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> 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 beca
g the PCs, "nbtstat -R"
>
> Hope this helps!
>
> Scott
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Jim Bond
> Sent: Thursday, December 07, 2000 1:19 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
>
ED]>
To: "Jim Bond" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 5:54 AM
Subject: Re: tough VPN question
> You are not NAT'ing the clients to the Domain Controller are you? I think
> you are by the fa
-Original Message-
From: Jim Bond [mailto:[EMAIL PROTECTED]]
Sent: ??? ? 07 ? 2000 08:19
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
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
9 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
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
fr
manually map drives
without the use of the browser service.
-Original Message-
From: Jim Bond [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 06, 2000 11:19 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: tough VPN question
Hello,
I'm trying to set up a IPSec between a PIX (b
rk (Canada)
Email: [EMAIL PROTECTED]
- 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 u
Jim,
Make sure that your Pix is allowing the NBT. If not open a port for it.
Also, if you are not using WINS, configure an ip helper address.
Jim Bond wrote:
> 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
CCIE # 5185
- Original Message -
From: "Jim Bond" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 06, 2000 10:18 PM
Subject: tough VPN question
> Hello,
>
> I'm trying to set up a IPSec between a P
Message-
From: Jim Bond [mailto:[EMAIL PROTECTED]]
Sent: ??? ? 07 ? 2000 08:19
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
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 ad
Did you try an LMHOST file to specify the name and IP address of the domain
controller?
Robert
Original Message Follows
From: Jim Bond <[EMAIL PROTECTED]>
Reply-To: Jim Bond <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
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 p
40 matches
Mail list logo
