I havent actually setup a VPN, but think I understand the very basic
concepts of a tunnel. Applying to a real life situation is confusing me a
little. I have a need to setup a remote office for a customer. They have a
2500 with a very basic NAT configuration, listed below my signature. They do
In order for the few PCs in the remote office to have access to the main
office servers, do I even need to build a tunnel since they have no
firewall?
Whether to setup a vpn tunnel or not is dictated by your business needs and
the types of services you want the remote office to access, not by
as easy as forcing UDP encapsulation on the server
side...
Good luck,
-Original Message-
From: Craig Columbus [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: VPN Design ? [7:45927]
In order for the few PCs in the remote office to have
]
Subject: Re: VPN Design ? [7:45927]
In order for the few PCs in the remote office to have access to the main
office servers, do I even need to build a tunnel since they have no
firewall?
Whether to setup a vpn tunnel or not is dictated by your business needs and
the types of services you want
: RE: VPN Design ? [7:45927]
I'm not referring to a strictly static NAT setup. I'm talking about
dynamic NAT/PAT, where clients may get a NAT address or may use PAT,
depending on pool availability.
For example, I had a location that was dropping connections on the PIX and
I couldn't figure out
I'm not sure if this is exactly what you are referring to Craig, but it
might help. We also have had problems doing VPN Client connections behind
PAT. Its only in places where the DSL/Cable router cannot support PAT on
unknown ports, like UDP 1 which is default for VPN 3000 connections.
6 matches
Mail list logo
