Discussion Locked

DHCP blues...

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

Hi. I'm trying to get some users off of the external IPs at our company. We've got a block of external IPs hooked up to a Cisco 1600 router and an ADSL. I've setup an NT4-SP6A box with 2 NICs to act as a DHCP server. Here's my setup so far:

External NIC - IP: 207.236.57.195 / Subnet: 255.255.255.224 / GW: 207.236.57.193 (the Cisco router)

Internal NIC - IP: 192.168.0.1 / Subnet: 255.255.255.0 / GW: none

I've turned IP forwarding on and I setup the DHCP client (w2k pro boxes mostly) with DHCP enabled and 192.168.0.1 as the default gateway.

Now the client box actually gets an IP address and can ping both the internal and external NICs but nothing beyond that. All that shows up in the browse list is the DHCP server and itself.
It seems the NICs aren't exchanging info between them and I'm well stumped as to what I've left out of the loop. Can anybody give me a hand here? I've also got MS Proxy Server running on the DHCP box.

Thanks!
Luis

8 replies

by bill-ccna

Luis,
Some thing to check:
Can the DHCP client ping the router? You need to make sure the router has the subnet you are using configured (192.168.0.0/24) on its interface attached to the DHCP server. This lets the router know that the 192.168.0.0 network is directly attached to the interface. The first thing to make sure is that the DHCP client is getting to the router.

by luis esteves

Hi Bill. Thanks for the reply. You mean ping the Cisco Router you mean? Nope, the DHCP client can't ping anything beyond the external interface on the NT box with the DHCP server. What is funny is that we're all hooked up to the same hubs and all the boxes in here have fixed IPs. The Router is not working as another DHCP server...

TIA,
Luis

by bill-ccna

The router isn't acting as another DHCP server, but it is acting as a router. You will not be able to ping the router if the subnet you are pinging from isn't known to the router. Further, if you are using private address space, then the router will not know how to route it unless either 1. there is an entry in its route table for the subnet or 2. one of its interfaces is on that subnet (therefore the subnet will be listed as attached). If you can't even reach the router then you will be unable to reach anything else. Also verify you can reach the router from the DHCP server. Try and troubleshoot each piece at a time.

by luis esteves

Hi guys. Sorry it took me son long to get back but I had to go on a job outside of Canada and just got back Monday. I've solved my problem in a roundabout sort of way though...

I've setup a w2k server box and am using DHCP and have setup Routing and Remote Accesss for NAT to give clients access to the internet. I have one server that will stay on the internal network but is hosting pages so it needs an external address so I'm using the adress pool feature to reserve a public address for it.
So far this is working like a charm...

Thanks for your help anyway.

Luis

by tony.griscavage

Luis I noticed that you did not have a GW address for your internal IP. Try assigning a GW and you will probally see more in the browse list. Tony G.

This discussion is closed to new replies.