Question Locked

Help with Windows Server 2003 DHCP setup

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, I'm trying to reconfigure a Windows Server 2003 SBS, and am having a few problems. Here's the network setup:
DSL line in to DSL Modem
D-Link Router w/ DHCP on plugged into DSL Modem
24-port Switch plugged into D-Link Router
Windows SBS 2003 plugged into D-Link Router via external network port
8-port Switch plugged into internal network port of Windows SBS 2003

We have two separate networks, one for machines coming in that are to be serviced (call this service network), and one for our work machines and POS machines (call this internal network). We want the internal network to connect to the 8-port switch connected to the 2003 server, and the service network to connect to the 24-port switch connected to the Router. The problem I'm running into is the SBS Server is seeing the router serving DHCP upstream, and is turning off it's own DHCP. Any suggestions as to how I resolve this?

9 replies

by naughtymonkey

put one on 192.168.1.- and the other on 10.-.-.-

This way the traffic will have to go through the router to get to the other and should not forward DHCP traffic.

by pete.campbell

By temporarily unplugging external NIC on SBS 2003, I was able to start DHCP service. Now I'm having troubles getting machines on internal network to access the internet.

Here's the configurations:
Router IP: 192.168.2.1
serving 192.168.2.100->192.168.2.200

SBS 2003 external NIC:
IP: 192.168.2.10
subnet: 255.255.255.0
gateway: 192.168.2.1
DNS: 192.168.100.2

SBS 2003 internal NIC:
IP: 192.168.100.2
subnet: 255.255.255.0
gateway: blank
DNS: 192.168.100.2

internal machines get their IP no problem, but can't access the internet. I can do an nslookup from the command prompt for any site no problem, but when I try and ping those addresses, the request times out. I can't ping the router, but I can ping the internal and external NICs. The internet is working fine on the server itself. Is there some more settings I need, such as WINS, NetBIOS?

by sgt_shultz

why not let sbs 2003 do the dhcp? it's really best for sbs to be in charge of things, especially this.

by pete.campbell

We need the two networks to be as separated as possible, since the service network has virus infected machines being plugged into it on a regular basis. We also do quite a bit of bandwidth intensive work on the service network, and don't want the traffic to impede our internal network.

by cg it

the external NIC on the SBS box should have a static address. Also the Windows Firewall on the SBS box should be turned on.

you shouldn't have a problem with DHCP running on the perimeter router with the SBS box external NIC connected to it.

If you do create a reservation for the SBS external NIC address or make that address as part of the reserved pool.

by pete.campbell

"windows firewall cannot run because another program or service is running that might use the component ipnat.sys"

the external NIC address is outside of the range of addresses being served by the router, so the router won't let me create a reservation.

also, when I shut down and restart the server, DHCP is turned off again, I need to unplug external NIC, start DHCP, plug external NIC back in. It tells me the service isn't needed if I try to start it with the external NIC plugged in.

by pete.campbell

Do you mean the gateway for the Internal network? I have the gateway blank for the internal NIC, and the internal network get their IP addresses automatically, and they are being assigned to the internal NIC as gateway.

This discussion is closed to new replies.