Re: Very basic question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Anteaus - The 30 IP addresses are the maximum allowed with the mask
255.255.255.224 that we @bought' with the leased line. I don't envisage
using more than say 5.

As for a Cisco trained consultant I really don't want to go down this path
as the router/leased line is managed by my telecoms provider (British
Telecom) you are (so far) at the best useless (although I don't want to turn
this into a BT vs other telecom provider debate).

My problem is that I have to implement this in a short space of time (end of
May at the very latest) and am lacking in a few basic areas. I am about to
post another thread that will detail this more completely.

Thanks for your response
TJ

"Anteaus" <Anteaus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7E73F208-E030-4261-B4C3-A879F014EBA6@xxxxxxxxxxxxxxxx

My thoughts here are that you need to get a consultant in who understands
this type of setup. Preferably a Cisco-trained one.

Most of the Cisco units should be able to handle the IP-routing
requirements
without additional hardware, though they are by no means easy to configure
as
it (usually) has to be done with DOS-like commandline instructions.

I'm also curious to know why you need so many IP addresses, unless of
course
it's a very large site with 30 Internet-facing servers. These days it's
unusual to allocate global IPs to anything other than servers, desktops
get
their Internet feed by way of a NAT router.

Allocating global IPs to desktops (if that is your intention) is not good
from a security point of view, either, as any firewall deficiency or
oversight leaves them open to attack. Better to use NAT, which has
inherent
security.


"TJ" wrote:

Hi

We have recently purchased a leased line that comes with a managed Cisco
1841 router. With this I have 30 IP addresses of say 82.82.82.160 =
82.82.82.190. As this router has not been suplied with a firewal we have
purchased ISA Server 2006 which I am trying to get to grips with (not an
area I am familiar with but need to get so PDQ). On the back of the
router
are 4 ports (Console, Aux, FE0 & FE1).

I want to create a 3 leg firewall - DMZ, Public & Internal and have 3
NIC's
in the server. The Internal NIC is plugged into a powered switch on the
local network. The DMZ is going to go into our web application. I am
unsure where to plug the External NIC. I am guessing that it needs to go
into either FE0 or FE1. However if I use more than 2 of the external IP
addresses, would I need to plug the Cisco into a separate switch that is
not
attached to the internal network?

I know I should ask my telecoms supplier, but anyone who has had dealings
with BT will know that for customer service they are next to usless.

Thanks
Tony





.

Relevant Pages

  • RE: Very basic question
    ... it's a very large site with 30 Internet-facing servers. ... We have recently purchased a leased line that comes with a managed Cisco ... As this router has not been suplied with a firewal we have ...
    (microsoft.public.windows.server.networking)
  • Re: Sendmail on a LAN
    ... It's the servers to which you're going to try to ... I am having serious problem with an unwieldy router. ... So I can indeed smtp out. ... Session types are opaque to the user as far as configuration goes. ...
    (Fedora)
  • Re: 360 Slim ships today, on sale this week(!)
    ... router is negligible compared to a home router to game servers. ... I use wireless versus when I use a wired connection. ... download GT Prologue, and over three hours to fully download OngBak2 ...
    (alt.games.video.xbox)
  • Re: Sendmail on a LAN
    ... It's the servers to which you're going to try to ... I am having serious problem with an unwieldy router. ... So I can indeed smtp out. ... Session types are opaque to the user as far as configuration goes. ...
    (Fedora)
  • Re: Makes no sense to me?
    ... I am not sure what is first here the servers or the routers to the internet? ... Router A starting or IP is ... Reconfigure the NAT Devices to use the same IP Range on the Internal LAN ...
    (microsoft.public.win2000.networking)