Best Practice



Mickey
07-10-2005, 01:51 AM
Hi All

I would like to setup a home network for the purpose of learning about
Active Directory and networking technology. I would like it to somewhat mimic
a small network environment. I plan on using 2003 Server for my DC and a
802.11g wireless router. Here is my plan:

Use the router as a gateway and for NAT.
Use the DC for DHCP and DNS
Use one NIC on the server for local traffic and a seperate NIC for outbound
Internet traffic

1. Does the plan make sense?
2. Is it best to have the DC do DHCP and DNS (instead of the router)?

Robert L [MS-MVP]
07-10-2005, 01:51 AM
look good to me.
For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Mickey" <Mickey@discussions.microsoft.com> wrote in message news:40073FB1-E641-4263-8D43-21F80316AF28@microsoft.com...
Hi All

I would like to setup a home network for the purpose of learning about
Active Directory and networking technology. I would like it to somewhat mimic
a small network environment. I plan on using 2003 Server for my DC and a
802.11g wireless router. Here is my plan:

Use the router as a gateway and for NAT.
Use the DC for DHCP and DNS
Use one NIC on the server for local traffic and a seperate NIC for outbound
Internet traffic

1. Does the plan make sense?
2. Is it best to have the DC do DHCP and DNS (instead of the router)?

Ron Lowe
07-10-2005, 01:51 AM
"Mickey" <Mickey@discussions.microsoft.com> wrote in message
news:40073FB1-E641-4263-8D43-21F80316AF28@microsoft.com...
> Hi All
>
> I would like to setup a home network for the purpose of learning about
> Active Directory and networking technology. I would like it to somewhat
> mimic
> a small network environment. I plan on using 2003 Server for my DC and a
> 802.11g wireless router. Here is my plan:
>
> Use the router as a gateway and for NAT.
> Use the DC for DHCP and DNS
> Use one NIC on the server for local traffic and a seperate NIC for
> outbound
> Internet traffic
>
> 1. Does the plan make sense?

I have a similar setup, but use only 1 NIC on the server.
In your case, the entire LAN is behind NAT, which is doing the Internet
sharing,
so there's not a whole lot of benefit from multi-homing the server.

Set the server up with a static IP address.

> 2. Is it best to have the DC do DHCP and DNS (instead of the router)?
>

Yes, it's essential. ( well, the DNS anyway. )
Also, the DHCP server on the windows machine is
much more full-featured than on any domestic broadband router.

--
Ron

Richard G. Harper
07-10-2005, 01:51 AM
Yes, you want the server to do both DHCP and DNS for your "network",
especially if you're considering setting up a domain. Windows Active
Directory works best when it provides DNS and DHCP to the computers in the
network.

--


"Mickey" <Mickey@discussions.microsoft.com> wrote in message
news:40073FB1-E641-4263-8D43-21F80316AF28@microsoft.com...
> Hi All
>
> I would like to setup a home network for the purpose of learning about
> Active Directory and networking technology. I would like it to somewhat
> mimic
> a small network environment. I plan on using 2003 Server for my DC and a
> 802.11g wireless router. Here is my plan:
>
> Use the router as a gateway and for NAT.
> Use the DC for DHCP and DNS
> Use one NIC on the server for local traffic and a seperate NIC for
> outbound
> Internet traffic
>
> 1. Does the plan make sense?
> 2. Is it best to have the DC do DHCP and DNS (instead of the router)?
>
>
>


Best Practice