router setuo

[Alby]

just got adsl router/modem i need some advice on setup before i start tinkering
i want to connect 2 systems to it sharing the net one as a w2k server the other w2k wstation but im geting confused with dns settings etc
scenarios:

1) leave router dhcp on and let machines pick up ips automatically, what dns settings for router, defaults or ips's

2) enable dhcp on my server, obviously i turn off dhcp on the router. what settings do i need to use for my router(10.0.0.xxx). do i just add the lan ips to the routing table
the gateway on lan is the router, dns would be my server AD?

3) use static ips on lan, what changes (if any) do i make to the routing table etc

i'm new to this so if i havent explained too well please bear with me.
final thought router has built firewall is this good enough or should i keep ZA running
tnx

[Dakota]

Whomever ends up helping you will need some more information. Who is your ISP? Do you currently have a static IP address? OS? If you're currently now DHCP -- ex-@home -- like most of the planet is these days, then set everything to auto (pc's and router -- IP and DNS) and go.

Most of us do still run a firewall such as ZA, Tiny or Sygate to control in/out traffic. You are still going to want to know what sofware is calling out and/or asking for server rights.

[YeOldeStonecat]

Here's what I do with all the router setups on networks with NT servers:

I don't like the DHCP service of the routers. On smaller LANs with no NT server, I always use static IP's on all the workstations. (For ease of future add ons, you can leave the DHCP of the router turned on, just manually assign IP's outside the DHCP's scope) On networks with an NT server, I use the servers DHCP service. Obviously if that's the case, you cannot have two DHCP servers on the same network, so you have to turn off the routers DHCP before you kick in the servers DHCP.

The NT servers DHCP will hand out:
1)IP address
2)Gateway, which is the routers LAN IP
3)The two DNS servers of your ISP. Technically you can hand out the routers LAN IP again, since they often do DNS or just DNS forwarding, but it's a performance hit. Let the network go straight to the source. Or if you're running DNS on your own server, you can use that.

That's it.

Example. Router with a standard 192.168.1.XXX LAN scope, where the router is 192.168.1.1, it's natural DHCP scope is 192.168.1.100 - 192.168.1.253, and say for example your ISP's DNS servers are 211.212.213.214, and 211.212.213.215

I make my server static IP's in the low teens, like 192.168.1.11, 192.168.1.12, etc etc. I usually make my network printers in the 20's, like 192.168.1.21, 192.168.1.22, etc. And workstations from say 50 on up, or 100 on up. Whatever works for you.

So setup DHCP on your server to hand out the scope of 192.168.1.50 - 99, hands out the gateway which is the router at 192.168.1.1, and hands out the two DNS servers, 211.212.213.214 and 211.212.213.215.

[DaRkLaNcE]

Hum, are you trying to learn about Win2k and networking, but having problems initally setting it up.

If you want to use DHCP on your win2k server. I will give you a example of how you would set it up with a 192.168.0.1/24 Scheme.

First set your scope for starting IP 192.168.0.1, subnet 255.255.255.0, and ending ip 192.168.0.254.

Exclude 192.168.0.1-192.168.0.25 for any servers or service you want to use in the future.

Create a scope for, Gateway (which will be the lan or private ip address of your router). DNS(if you want to use your own dns servers then put the ip of your win2k server or your isp dns server).

Make sure you activate and authenicate your dhcp server before it can start alocating ip addresses.

[Alby]

lo ppl
ok thinks me got it, i just assign my ips from the server keeping then outside the router range
tnx