Re: Pros/Cons of Single/Dual NIC Card Topology?



an FVS318 is a 'simple NAT router' rather than a firewall device. Go 2 NICs
and ISA.

"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C610D675-ECA5-4C53-8CB9-3E41CABC6EE5@xxxxxxxxxxxxxxxx
Leythos:

We are using a Netgear Prosafe VPN Router/Firewall FVS318. it only has 8
ports so it will not support 10 users. If I do not "need" the Netgear
hardware, I was planning on using ISA since it is a part of SBS premium,
as I
didnt want to add an extra layer of complexity to things.

Part of this line of thought is because we have one of our departments
that
is too far away for us to hard-wire in, so I was planning on having them
access via remote access.

Regards
Jeff

"Leythos" wrote:

In article <A2A0EA7E-DE07-4429-84AD-108CDAD3FCB9@xxxxxxxxxxxxx>,
Jay@xxxxxxxxxxxxxxxxxxxxxxxxx says...
A couple of questions from a server install newbie:

1. I am readying a server for install that has SBS 2003R2 Premium with
10
users. Are there any pros/cons/gotchas over placing the server between
the
WAN connection (Internet Connection Device) running directly to the
server (2
NICs required), or having the WAN connection going into a switch/hub
and
having the server connected to it (1 NIC required)?

2. This server is replacing a peer-to-peer network, and I would like
to use
the router we are using now which has a hardware firewall to be placed
between our DSL modem and the server. In doing this I was planning on
purchasing a switch to distribute the network...basically using our old
router/firewall just for its firewall capability. Is this good
practice?
We are a small company and the cost of the dedicated hardware firewalls
is
prohibitive.

A 1 NIC solution is the easiest and most versatile solution provided you
get a firewall and not just a NAT router. At the very least you need a
barrier device between the server and the internet - and unless you get
Premium and install ISA, you're just as well off with a single NIC and
router.

What router are you using that has a firewall? Most say they have a
firewall and if you dig deep enough, it's just NAT and some special
blocking rules, but it's not a firewall and may not handle a significant
load without performance hits.

You can provide a Dedicated Firewall for as little as $400 and devices I
consider to be very low end firewalls for about $300.

So the setup would be:

INTERNET DEVICE (ISP Router)
||
FIREWALL
||
SWITCH
||||||||||||
Server, Workstations, Printers, Etc..

If you ever setup remote workers or remote access, both RWW and VPN are
simple to setup and control in this solution.

--

spam999free@xxxxxxxxxx
remove 999 in order to email me



.



Relevant Pages

  • RE: OWA page not displayed Outside
    ... Open the ISA Server management console, ... On the ISA Server computer, stop the Microsoft Firewall service. ...
    (microsoft.public.windows.server.sbs)
  • RE: OWA page not displayed Outside
    ... Open the ISA Server management console, ... On the ISA Server computer, stop the Microsoft Firewall service. ...
    (microsoft.public.windows.server.sbs)
  • RE: OWA page not displayed Outside
    ... Open ISA 2006 management console. ... Expand the server node and highlight 'Monitoring'. ... Click 'Configure Firewall Logging'. ... |> internal client as both the web proxy client and firewall client? ...
    (microsoft.public.windows.server.sbs)
  • Re: Using ISA and Exchange together
    ... In this scenario, IMHO, the router shouldn't be doing anything other than routing traffic. ... kind of unusual that your router and firewall are two different hardware devices, but none the less...I would remove ISA and the second nic, and let your firewall do it all. ... Otherwise you might want to keep ISA so you can have that functionality...and then I would remove the hardware firewall. ... traffic will be proxied by the ISA server. ...
    (microsoft.public.windows.server.sbs)
  • Re: loss of SOME connectivity
    ... I "think" it is DNS. ... Yes, I can ping the router, AND the ISP DNS. ... I cannot connect the inet cable directly to the server because the inet is ... MS firewall not started. ...
    (microsoft.public.windows.server.sbs)

Loading