Re: VPN configuration with 2 network cards

I recommend the ProSafe VPN Firewall devices. They have stateful packet
inspection, Dos protection, intrusion detection and AES and 3DES encryption
for VPN. When you go to Netgears site click on Products-VPN Routers and SSL
then click on Wired VPN Firewalls.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ezVIPZyTIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
PFFFFT 'lessen your security model, it's better'.

What model of NetGear device is currently in use? Some have VPN
capabilities, some don't. NetGears are actually pretty good, even the VPN
capable models _normally_ have multiple passthrough capability if you
disable their own.

John, what NetGear devices do you use? AFAIK _none_ are firewalls, they
are simple NAT routers with _some_ firewall features. You can see from the
NetGear site that they do not have a 'firewall' category, they do have
'routers and gateways'.

"John Oliver, Jr. [MVP]" <jcoliverjr@xxxxxxxxxxx> wrote in message
news:uDFARCxTIHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
I may be a little biased as my company is also a Netgear reseller but they
do work and are very reasonably priced for the SMB market. I have many
SBS networks running VPN's with Netgear equipment. No complaints yet.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Rod" <Rod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33142599-E0B7-4CAE-BC19-78D41D727267@xxxxxxxxxxxxxxxx
Thanks. I believe I will do this. Theier support is good however I have
been
talking to a support rep that seems to have limited experience in this.
He is
having a "senior level" tech call me back and I think I will suggest
this
recommendation.

"John Oliver, Jr. [MVP]" wrote:

If you are already using Netgear then I would recommend using their
hardware
for the VPN appliance and go with a Single NIC on your SBS server.
Netgear
is very easy to setup with VPN and you also get the support from
Netgear.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Rod" <Rod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:814E8588-C75F-4ECA-90B7-F6998A1AA71E@xxxxxxxxxxxxxxxx
Our sbs server has been configured with 2 network cards for some
time. I
think we originally did it because of a unique situation we had
diricting
and
protecting internet traffic. One card points to the internal network
and
the
other points to the internet. Currently we use OWA and RWW with no
problem.
We do not use ISA but I am considering re-installing it for the
internet
usage reports.

My problem is that I (and netgear support) am unable to successfully
connect
VPN. Must I reconsider my sbs setup to get the vpn working?









.

Relevant Pages

  • VPN home worker implementation
    ... network security. ... Firewall acting as VPN host which is connected to Company ... All Internet, email etc must go through Company ...
    (comp.security.firewalls)
  • Re: Using a Linksys router, should I also use Zonealarm?
    ... public internet to access corporate network. ... In the "old days" when people used to use Dial-In instead of VPN you ware ... protected by corporate Firewall -- since there was no public Internet ...
    (microsoft.public.security)
  • Re: Sometimes it works sometimes it doesnt (VPN data issues)
    ... NIC1 "Internet" is set to ... (the IP of the external firewall) and the DNS is set to ... A connection between the VPN server and the VPN client xxx.xxx.xxx.xxx ...
    (microsoft.public.windows.server.networking)
  • [fw-wiz] L2L VPN redundancy for T1 link
    ... VPN, without any routing protocol needed on the firewall. ... VPN rather than towards the internal network where the T1 router resides). ... Internet network, bypassing the firewall. ...
    (Firewall-Wizards)
  • Re: PPTP thru SUSEfirewall
    ... on the firewall itself and had quite a few firewall/routing tuning ... The firewall also has to let these packets in from the Internet ... something like "for VPN services that stop at the firewall". ... (assuming your internal server is 192.168.0.1) ...
    (alt.os.linux.suse)