hi... i'm tryin' to find out how i would configure the ip addressing between windows 2003 server and a Cisco 1801 broadband router when setting up DHCP and NAT on the NOS... just not sure if the ip addressing is correct... and something else i've been chewing on... if i set the router up to handle DHCP/NAT would i configure it to have 1 inside and 1 outside ip and then the server would just have one stacic internal IP? how i currently have them assigned... INTERNET /\ Cisco 1801 IP (static ip assigned by ISP) /\ 2003 server w/2 nics E0 168.192.0.1 (to router) E1 168.192.0.2 (to switch/lan) /\ workstations IP 168.192.x.x thanks for any help.

if i set the router up to handle DHCP/NAT would i configure it to have 1 inside and 1 outside ip and then the server would just have one stacic internal IP? Yes. The internal interface on your router would be your gateway address for internet access for clients. If this is an AD integrated windows domain, you'll want your client DNS addresses to point at your server (DC) and forward it's DNS to your ISP. Otherwise, assign your ISP's DNS addresses to the clients. You might want to use: 192.168.0.250 as your gateway address (IP on internal interface of router) and give: 192.168.0.1 to your server. Keep at least the first 10 or 20 IP's out of your DHCP scope to be used for printers and servers etc. Also keep 250 and up out of your scope. DHCP scope should look as follows: 192.168.0.21 - 192.168.0.249 If this is, or may become an AD domain, use DHCP on your DC and not your router.

sorry... i'm the newest of newbies when it comes to this stuff... i've been cramming all day long... all i can find is info on setting up NAT on just 2003 server or just a Cisco router. i can't figure out the ip addressing or how to point the gateway address if i am using AD 2003 server, then going from the server to the cisco 1801, then from the router to the internet... am i a little closer? lol... INTERNET /\ Cisco 1801 IP (static ip assigned by ISP) /\ 2003 server w/2 nics E0 168.192.0.2 (to router) E1 168.192.0.1 (to switch/lan) /\ workstations DHCP SCOPE 168.192.0.21 - 168.192.0.249 Gateway address would point to server (168.192.0.1) default subnet mask 255.255.0.0

Internet >> Router (external interface) >> Router (internal interface) >> switch >> server & clients Router: External: IP: provided by ISP Internal: IP: 192.168.0.250 Subnet Mask: 255.255.255.0 Server IP 192.168.0.1 Gateway: 192.168.0.250 Subnet Mask: 255.255.255.0 DNS: ISP's DNS server addresses DHCP enabled on server Scope: 192.168.0.21 - 249 Gateway: 192.168.0.250 Subnet Mask: 255.255.255.0 DNS: ISP's DNS server addresses Or, if you're planning on creating a Windows AD integrated domain DNS: 192.168.0.1 (DNS service on server forwarded to ISP's DNS servers)

Internet >> Router (external interface) >> Router (internal interface) >> AD 2003 server >> switch >> clients this is how i had it setup... now what i don't understand is i need 2 nics in the server (one pointing to the router to get outside to the internet, and one pointing to the lan)... then i don't know why the router would still need internal and external ip addressing if the AD 2003 server is handling DHCP, DNS, and NAT... i know the router has to contain the static internet address by which all nodes on the internet can communicate with our network... i thought i could set it up so that the clients gateways point to the address on the Internal NIC in the AD 2003 server... then NAT does its thing... and then on out to the router... In your scenerio you have the server connected to the switch then to the router... as opposed to how i'm going router >> server >> switch... can it be done either way? sorry... don't mean to grill you... i'm assumming you are correct as i've read through some of your posts before and you sound like a dude who know what he's talking about... i'm just trying to understand this stuff as opposed to just having somebody tell me what to do. thanks for the help/schooling...

Internet<>AD 2003 server >> switch >> clients is a config when you don't have a router or you want to proxy/control bandwidth/monitor usage/web page hosting on the server. Normally with a router you wouldn't have two nics in the server. wksts point to MS dns and MS dns forwards to the isps dns servers. Golly gee wilerkers everyone. Learn to Internet Search

Yes, it can be done either way . Since you have a router, it makes sense to let it do the routing and NAT. In which case, you would go Router >> Switch >> Server/Clients. As Wanderer said, if you don't have a router, then you multihome your server (ie: two NIC's) and use RRAS/NAT to do your NAT and routing with one NIC internal (LAN) and one external (WAN/Internet). The big point is to keep things as simple as possible (ie: KISS - Keep it Simple Stup....you get the idea.....lol). The simpler your setup the easier it is to maintain and troubleshoot in the case of errors. Also, You don't want to mix and match too much between your router and server. Designating one device to do your routing, NAT, DHCP etc also helps when you have to troubleshoot as you know which device is doing what. If you're running a peer to peer network at present but may move to an AD integrated domain in the future you'll want to let the router do as much as possible to ease the load on the server. Heck, that's not even a bad idea in a P2P network if your server is under a heavy load. Every service you can offload from the server onto another device is that much less the server has to do. One other thing of note.........document everything! This not only makes your life easier but also helps whoever is going to replace you at some point in the future (none of us lives forever right!). Where I'm working now, documentation has been a big project as the network was never adequately documented before. My co-worker and I have spent countless hours tracing cabling and documenting all 11 wiring closets and the racks of switches in them as well as the two server rooms. Let me tell you, it wasn't fun....but in the end, we have a redundant documentation system that makes our lives so much simpler when troubleshooting problems. One look at a wall jack tells us what wiring closet, what patch panel and which port in the patch panel is associated with that jack. A quick walk to the closet and a look at the documentation in there tells us which switch and which port the cable plugs into. This beats the heck out of toning it out, finding the end in the closet, tracing the cable...... I can't stress good documentation enough. It's a time saver and frequently a life saver when things start to go really wrong.