alt.certification.mcse - Advice: Setting up a Home Network

Author

Advice: Setting up a Home Network

Michelle Hillard

2003-11-01, 8:25 am

Hi Experts,
Im calling on you for expert advice. I know what I am asking here is so
much. In a nutshell, I am trying to build a mini network, but thinking of a
bigger picture.
Basically, Im trying to achieve the goals as outlined below but really need
expert advice to point me in the right direction. Thats why Im calling on
the world and YOU!

Equipment I have:

1 PC: Windows 2000 Server running DNS/Active Directory
1 PC: Windows 2000 Server running MS Exchange Server 2000
2 PCs: Windows 2000 Professional
1 Cisco PIX 501 Firewall
Cisco 2514 router.
Cable Modem connection to the internet

Internal Network:
192.168.x.x

Goals:
1) I would like to set up my own MS Exchange Server 2000, so that the 2
client PCs can get their email from it.
2) I would like email from the world to be able to hit my Exchange Server
2000 and passed to my internal 2 client PCs
3) I would like to set up my own DNS domain so that it is accessible to the
world eg.www.mydomain.com.au
4) I would like to set up a Windows 2000 Domain (Active Directory)
5) I would like the 2 internal clients to be able to access the Internet but
be verified/audited on attempts
6) I would like to setup DHCP for internal clients
7) I would like all incoming email VETTED on the Exchange Server before
email is passed through to internal clients
8) I would like all incoming/outgoing web traffic screened before passed to
internal clients
9) I would like to enable VPN access to my internal network

Questions:

1) Do I have enough equipment to be able to achieve the above goals?
2) What would you suggest be the best configuration with the equipment I
have?
3) Would you suggest setting up a DMZ? If so, with a DMZ, do you usually
have 2 firewalls/routers eg. one for the internal --- DMZ boxes --- one
external ---- Internet??
4) What public ip addresses would I need to have? Who needs to know about
these public addresses?
5) Do I need a public ip address for the following:
a) MS Exchange Server
b) DNS Server
c) The router connected to the Internet?

If I need these public IP addresses, in order for the outside world to
contact/see me, to whom do I have to "send"/give these public IP addresses
to, so that they can route to me?

6) If I have to configure NAT on the router eg.PIX etc, do I:
a) Set up Static NAT for the MS Exchange Server eg.If internal it is
192.168.1.2 --- map to public 203.44.56.78
b) Set up Static NAT for DNS
Does the MS Exchange Server and the DNS Server if on different machines,
have to have a public IP address?
Can I simply give the ISP the MX record for the Exchange Server as the PIX
public IP address, and have NAT nat that address to the MS Exchange?
How would I do this?

I know there is so many questions here, and I am so grateful if you have
read this far. I am really keen to learn to build all this stuff myself, as
so far I have not been fortunate enough to land a job where I can do this
stuff. Any help at all by you great people would be so much thanked. Thank
you.

Michelle.

--

---------------------------------------------------------------------
"Are you still wasting your time with spam?...
There is a solution!"

Protected by GIANT Company's Spam Inspector
The most powerful anti-spam software available.
http://mail.spaminspector.com

Pegasus $MVP$

2003-11-01, 9:25 am

There are enough questions in your post to fill three weeks of
full-time MCSE courses - at least. The problem is how to condense
these courses into a 20-line reply.

"Michelle Hillard" <mhillard@bigpond.net.au> wrote in message
news:nWNob.173925$bo1.2831@news-server.bigpond.net.au...
> Hi Experts,
> Im calling on you for expert advice. I know what I am asking here is so
> much. In a nutshell, I am trying to build a mini network, but thinking of
a
> bigger picture.
> Basically, Im trying to achieve the goals as outlined below but really
need
> expert advice to point me in the right direction. Thats why Im calling on
> the world and YOU!
>
> Equipment I have:
>
> 1 PC: Windows 2000 Server running DNS/Active Directory
> 1 PC: Windows 2000 Server running MS Exchange Server 2000
> 2 PCs: Windows 2000 Professional
> 1 Cisco PIX 501 Firewall
> Cisco 2514 router.
> Cable Modem connection to the internet
>
> Internal Network:
> 192.168.x.x
>
> Goals:
> 1) I would like to set up my own MS Exchange Server 2000, so that the 2
> client PCs can get their email from it.
> 2) I would like email from the world to be able to hit my Exchange Server
> 2000 and passed to my internal 2 client PCs
> 3) I would like to set up my own DNS domain so that it is accessible to
the
> world eg.www.mydomain.com.au
> 4) I would like to set up a Windows 2000 Domain (Active Directory)
> 5) I would like the 2 internal clients to be able to access the Internet
but
> be verified/audited on attempts
> 6) I would like to setup DHCP for internal clients
> 7) I would like all incoming email VETTED on the Exchange Server before
> email is passed through to internal clients
> 8) I would like all incoming/outgoing web traffic screened before passed
to
> internal clients
> 9) I would like to enable VPN access to my internal network
>
> Questions:
>
> 1) Do I have enough equipment to be able to achieve the above goals?
> 2) What would you suggest be the best configuration with the equipment I
> have?
> 3) Would you suggest setting up a DMZ? If so, with a DMZ, do you usually
> have 2 firewalls/routers eg. one for the internal --- DMZ boxes --- one
> external ---- Internet??
> 4) What public ip addresses would I need to have? Who needs to know about
> these public addresses?
> 5) Do I need a public ip address for the following:
> a) MS Exchange Server
> b) DNS Server
> c) The router connected to the Internet?
>
> If I need these public IP addresses, in order for the outside world to
> contact/see me, to whom do I have to "send"/give these public IP addresses
> to, so that they can route to me?
>
> 6) If I have to configure NAT on the router eg.PIX etc, do I:
> a) Set up Static NAT for the MS Exchange Server eg.If internal it is
> 192.168.1.2 --- map to public 203.44.56.78
> b) Set up Static NAT for DNS
> Does the MS Exchange Server and the DNS Server if on different machines,
> have to have a public IP address?
> Can I simply give the ISP the MX record for the Exchange Server as the PIX
> public IP address, and have NAT nat that address to the MS Exchange?
> How would I do this?
>
> I know there is so many questions here, and I am so grateful if you have
> read this far. I am really keen to learn to build all this stuff myself,
as
> so far I have not been fortunate enough to land a job where I can do this
> stuff. Any help at all by you great people would be so much thanked. Thank
> you.
>
> Michelle.
>
>
>
>
>
>
>
>
>
>
> --
>
>
> ---------------------------------------------------------------------
> "Are you still wasting your time with spam?...
> There is a solution!"
>
> Protected by GIANT Company's Spam Inspector
> The most powerful anti-spam software available.
> http://mail.spaminspector.com
>
>
>

Kurt L

2003-11-01, 2:26 pm

Pegasus is right, try taking it one step at a time and ask specific
questions as you progress. Also, you might pick up a book or two.....

....kurt

"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:bo0c6u$2ape$1@arachne.labyrinth.net.au...
> There are enough questions in your post to fill three weeks of
> full-time MCSE courses - at least. The problem is how to condense
> these courses into a 20-line reply.
>
>
> "Michelle Hillard" <mhillard@bigpond.net.au> wrote in message
> news:nWNob.173925$bo1.2831@news-server.bigpond.net.au...
> > Hi Experts,
> > Im calling on you for expert advice. I know what I am asking here is so
> > much. In a nutshell, I am trying to build a mini network, but thinking
of
> a
> > bigger picture.
> > Basically, Im trying to achieve the goals as outlined below but really
> need
> > expert advice to point me in the right direction. Thats why Im calling
on
> > the world and YOU!
> >
> > Equipment I have:
> >
> > 1 PC: Windows 2000 Server running DNS/Active Directory
> > 1 PC: Windows 2000 Server running MS Exchange Server 2000
> > 2 PCs: Windows 2000 Professional
> > 1 Cisco PIX 501 Firewall
> > Cisco 2514 router.
> > Cable Modem connection to the internet
> >
> > Internal Network:
> > 192.168.x.x
> >
> > Goals:
> > 1) I would like to set up my own MS Exchange Server 2000, so that the 2
> > client PCs can get their email from it.
> > 2) I would like email from the world to be able to hit my Exchange
Server
> > 2000 and passed to my internal 2 client PCs
> > 3) I would like to set up my own DNS domain so that it is accessible to
> the
> > world eg.www.mydomain.com.au
> > 4) I would like to set up a Windows 2000 Domain (Active Directory)
> > 5) I would like the 2 internal clients to be able to access the Internet
> but
> > be verified/audited on attempts
> > 6) I would like to setup DHCP for internal clients
> > 7) I would like all incoming email VETTED on the Exchange Server before
> > email is passed through to internal clients
> > 8) I would like all incoming/outgoing web traffic screened before passed
> to
> > internal clients
> > 9) I would like to enable VPN access to my internal network
> >
> > Questions:
> >
> > 1) Do I have enough equipment to be able to achieve the above goals?
> > 2) What would you suggest be the best configuration with the equipment I
> > have?
> > 3) Would you suggest setting up a DMZ? If so, with a DMZ, do you usually
> > have 2 firewalls/routers eg. one for the internal --- DMZ boxes --- one
> > external ---- Internet??
> > 4) What public ip addresses would I need to have? Who needs to know
about

> > these public addresses?
> > 5) Do I need a public ip address for the following:
> > a) MS Exchange Server
> > b) DNS Server
> > c) The router connected to the Internet?
> >
> > If I need these public IP addresses, in order for the outside world to
> > contact/see me, to whom do I have to "send"/give these public IP
addresses
> > to, so that they can route to me?
> >
> > 6) If I have to configure NAT on the router eg.PIX etc, do I:
> > a) Set up Static NAT for the MS Exchange Server eg.If internal it is
> > 192.168.1.2 --- map to public 203.44.56.78
> > b) Set up Static NAT for DNS
> > Does the MS Exchange Server and the DNS Server if on different machines,
> > have to have a public IP address?
> > Can I simply give the ISP the MX record for the Exchange Server as the
PIX
> > public IP address, and have NAT nat that address to the MS Exchange?
> > How would I do this?
> >
> > I know there is so many questions here, and I am so grateful if you have
> > read this far. I am really keen to learn to build all this stuff myself,
> as
> > so far I have not been fortunate enough to land a job where I can do
this
> > stuff. Any help at all by you great people would be so much thanked.
Thank

> > you.
> >
> > Michelle.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> >
> > ---------------------------------------------------------------------
> > "Are you still wasting your time with spam?...
> > There is a solution!"
> >
> > Protected by GIANT Company's Spam Inspector
> > The most powerful anti-spam software available.
> > http://mail.spaminspector.com
> >
> >
> >
>
>

Computer Guy

2003-11-01, 11:25 pm

Hello,
You seem to have sufficient equipment. There is an excellent book on the
streets by "Mark Manasi" called
"Mastering Windows 2000 Server". It answers all of your questions and also
applies to Windows 2000 Professional.
When out on a job, I carry that book with me at all times.
It looks to me as thought some reading and study is in order. There are no
easy answers. When it comes to many
people answering questions, much of this is over their heads. If I were not
certified, I would pass on this question.
Pegasus hit the nail right on the head, you could easily become a MCSE
during you quest for knowledge! So,
start reading and studying.
Computer Guy

"Michelle Hillard" <mhillard@bigpond.net.au> wrote in message
news:nWNob.173925$bo1.2831@news-server.bigpond.net.au...
> Hi Experts,
> Im calling on you for expert advice. I know what I am asking here is so
> much. In a nutshell, I am trying to build a mini network, but thinking of
a
> bigger picture.
> Basically, Im trying to achieve the goals as outlined below but really
need
> expert advice to point me in the right direction. Thats why Im calling on
> the world and YOU!
>
> Equipment I have:
>
> 1 PC: Windows 2000 Server running DNS/Active Directory
> 1 PC: Windows 2000 Server running MS Exchange Server 2000
> 2 PCs: Windows 2000 Professional
> 1 Cisco PIX 501 Firewall
> Cisco 2514 router.
> Cable Modem connection to the internet
>
> Internal Network:
> 192.168.x.x
>
> Goals:
> 1) I would like to set up my own MS Exchange Server 2000, so that the 2
> client PCs can get their email from it.
> 2) I would like email from the world to be able to hit my Exchange Server
> 2000 and passed to my internal 2 client PCs
> 3) I would like to set up my own DNS domain so that it is accessible to
the
> world eg.www.mydomain.com.au
> 4) I would like to set up a Windows 2000 Domain (Active Directory)
> 5) I would like the 2 internal clients to be able to access the Internet
but
> be verified/audited on attempts
> 6) I would like to setup DHCP for internal clients
> 7) I would like all incoming email VETTED on the Exchange Server before
> email is passed through to internal clients
> 8) I would like all incoming/outgoing web traffic screened before passed
to
> internal clients
> 9) I would like to enable VPN access to my internal network
>
> Questions:
>
> 1) Do I have enough equipment to be able to achieve the above goals?
> 2) What would you suggest be the best configuration with the equipment I
> have?
> 3) Would you suggest setting up a DMZ? If so, with a DMZ, do you usually
> have 2 firewalls/routers eg. one for the internal --- DMZ boxes --- one
> external ---- Internet??
> 4) What public ip addresses would I need to have? Who needs to know about
> these public addresses?
> 5) Do I need a public ip address for the following:
> a) MS Exchange Server
> b) DNS Server
> c) The router connected to the Internet?
>
> If I need these public IP addresses, in order for the outside world to
> contact/see me, to whom do I have to "send"/give these public IP addresses
> to, so that they can route to me?
>
> 6) If I have to configure NAT on the router eg.PIX etc, do I:
> a) Set up Static NAT for the MS Exchange Server eg.If internal it is
> 192.168.1.2 --- map to public 203.44.56.78
> b) Set up Static NAT for DNS
> Does the MS Exchange Server and the DNS Server if on different machines,
> have to have a public IP address?
> Can I simply give the ISP the MX record for the Exchange Server as the PIX
> public IP address, and have NAT nat that address to the MS Exchange?
> How would I do this?
>
> I know there is so many questions here, and I am so grateful if you have
> read this far. I am really keen to learn to build all this stuff myself,
as
> so far I have not been fortunate enough to land a job where I can do this
> stuff. Any help at all by you great people would be so much thanked. Thank
> you.
>
> Michelle.
>
>
>
>
>
>
>
>
>
>
> --
>
>
> ---------------------------------------------------------------------
> "Are you still wasting your time with spam?...
> There is a solution!"
>
> Protected by GIANT Company's Spam Inspector
> The most powerful anti-spam software available.
> http://mail.spaminspector.com
>
>
>

aardvark_ratnick

2003-11-03, 9:26 am

Michelle,

Yep you've taken on a big task for someone who has little experience. I'd
personally suggest one additional server with IIS 5.0 for your web server
and install the SMTP filter on it as well to screen your incoming e-mails.
The rest of it you should be able to hammer together in a few months, with
the help of several resources, internet, books, and perhaps news groups.

Good luck!

"Michelle Hillard" <mhillard@bigpond.net.au> wrote in message
news:nWNob.173925$bo1.2831@news-server.bigpond.net.au...
> Hi Experts,
> Im calling on you for expert advice. I know what I am asking here is so
> much. In a nutshell, I am trying to build a mini network, but thinking of
a
> bigger picture.
> Basically, Im trying to achieve the goals as outlined below but really
need
> expert advice to point me in the right direction. Thats why Im calling on
> the world and YOU!
>
> Equipment I have:
>
> 1 PC: Windows 2000 Server running DNS/Active Directory
> 1 PC: Windows 2000 Server running MS Exchange Server 2000
> 2 PCs: Windows 2000 Professional
> 1 Cisco PIX 501 Firewall
> Cisco 2514 router.
> Cable Modem connection to the internet
>
> Internal Network:
> 192.168.x.x
>
> Goals:
> 1) I would like to set up my own MS Exchange Server 2000, so that the 2
> client PCs can get their email from it.
> 2) I would like email from the world to be able to hit my Exchange Server
> 2000 and passed to my internal 2 client PCs
> 3) I would like to set up my own DNS domain so that it is accessible to
the
> world eg.www.mydomain.com.au
> 4) I would like to set up a Windows 2000 Domain (Active Directory)
> 5) I would like the 2 internal clients to be able to access the Internet
but
> be verified/audited on attempts
> 6) I would like to setup DHCP for internal clients
> 7) I would like all incoming email VETTED on the Exchange Server before
> email is passed through to internal clients
> 8) I would like all incoming/outgoing web traffic screened before passed
to
> internal clients
> 9) I would like to enable VPN access to my internal network
>
> Questions:
>
> 1) Do I have enough equipment to be able to achieve the above goals?
> 2) What would you suggest be the best configuration with the equipment I
> have?
> 3) Would you suggest setting up a DMZ? If so, with a DMZ, do you usually
> have 2 firewalls/routers eg. one for the internal --- DMZ boxes --- one
> external ---- Internet??
> 4) What public ip addresses would I need to have? Who needs to know about
> these public addresses?
> 5) Do I need a public ip address for the following:
> a) MS Exchange Server
> b) DNS Server
> c) The router connected to the Internet?
>
> If I need these public IP addresses, in order for the outside world to
> contact/see me, to whom do I have to "send"/give these public IP addresses
> to, so that they can route to me?
>
> 6) If I have to configure NAT on the router eg.PIX etc, do I:
> a) Set up Static NAT for the MS Exchange Server eg.If internal it is
> 192.168.1.2 --- map to public 203.44.56.78
> b) Set up Static NAT for DNS
> Does the MS Exchange Server and the DNS Server if on different machines,
> have to have a public IP address?
> Can I simply give the ISP the MX record for the Exchange Server as the PIX
> public IP address, and have NAT nat that address to the MS Exchange?
> How would I do this?
>
> I know there is so many questions here, and I am so grateful if you have
> read this far. I am really keen to learn to build all this stuff myself,
as
> so far I have not been fortunate enough to land a job where I can do this
> stuff. Any help at all by you great people would be so much thanked. Thank
> you.
>
> Michelle.
>
>
>
>
>
>
>
>
>
>
> --
>
>
> ---------------------------------------------------------------------
> "Are you still wasting your time with spam?...
> There is a solution!"
>
> Protected by GIANT Company's Spam Inspector
> The most powerful anti-spam software available.
> http://mail.spaminspector.com
>
>
>

Sponsored Links