HELP, New to Real world Networking need some answers!!!   

Hi Life Savers

I’m new to “Real Word” networking and HOPE to find some HELP here answering 
some (stupid) questions.

I work in a company of about 30 users. We have 1 windows server 2003 as PDC 
in Active directory domain. All clients are Windows XP Pro. The domain name 
is (petra.local) I have the PDC server also configured as DNS for local use. 
I use local IP addresses for LAN (100.100.100.X)

Now the company is growing…they want to add:
- One IIS Server that will host the company website (still under construction)
- One Exchange server
- One Firewall

Here is what I want to know:

1. How many Public IP addresses do we need? Will one public IP be enough for 
the   whole company? Can I subnet the public IP address to additional Public 
IP addresses for the other servers Or do I need one Public IP for EACH of the 
3 new servers (FW, Exchange, IIS)

2. If one IP address is enough, to which server I should assign it? To the 
Firewall or To the IIS

4. Regarding the Firewall: Is it better to use a Hardware FW or a Software 
one?

5. If  the ISP provide us with a Hardware Firewall and I also use a Windows 
server 2003 as an additional Firewall with 2 NICs and set it up as NAT 
server, How do I configure the IP address of the server to go through the ISP 
Firewall.

6. Do I need to setup my own public DNS server or I can just rely on the ISP 
for DNS services?


I REALLY appreciate your help guys

date: Tue, 29 Jan 2008 12:33:04 -0800   author:   Zegra1

RE: HELP, New to Real world Networking need some answers!!!   

Hi, too much question for one post. :-);

Q1,2,3,4,6: You can do all of this using one public IP , the IP will be 
assigned to the extrenal Interface of your FW, MS ISA 2006 would be a good 
choise as it's easy to use and proivde may wizard to configure IIS ,and 
Exchange publishing .
you  don't need to setup public DNS server you can use ISP DNS.

Q5: more info is need , this would complicate you net steup.

"Zegra1" wrote:

> Hi Life Savers
> 
> I’m new to “Real Word” networking and HOPE to find some HELP here answering 
> some (stupid) questions.
> 
> I work in a company of about 30 users. We have 1 windows server 2003 as PDC 
> in Active directory domain. All clients are Windows XP Pro. The domain name 
> is (petra.local) I have the PDC server also configured as DNS for local use. 
> I use local IP addresses for LAN (100.100.100.X)
> 
> Now the company is growing…they want to add:
> - One IIS Server that will host the company website (still under construction)
> - One Exchange server
> - One Firewall
> 
> Here is what I want to know:
> 
> 1. How many Public IP addresses do we need? Will one public IP be enough for 
> the   whole company? Can I subnet the public IP address to additional Public 
> IP addresses for the other servers Or do I need one Public IP for EACH of the 
> 3 new servers (FW, Exchange, IIS)
> 
> 2. If one IP address is enough, to which server I should assign it? To the 
> Firewall or To the IIS
> 
> 4. Regarding the Firewall: Is it better to use a Hardware FW or a Software 
> one?
> 
> 5. If  the ISP provide us with a Hardware Firewall and I also use a Windows 
> server 2003 as an additional Firewall with 2 NICs and set it up as NAT 
> server, How do I configure the IP address of the server to go through the ISP 
> Firewall.
> 
> 6. Do I need to setup my own public DNS server or I can just rely on the ISP 
> for DNS services?
> 
> 
> I REALLY appreciate your help guys
>

date: Mon, 7 Apr 2008 02:42:00 -0700   author:   Hikmat Kanaan