Comments on: Problem with Vlan DHCP, wrong Subnet IP address

By: sixball

sixball — Thu, 10 Feb 2011 21:25:56 +0000

I noticed you have the Line “ip route 0.0.0.0 0.0.0.0 192.168.2.201″, bt your last comment said you removed the path to the 192.168.2.x VLAN – could be a good palce to look as it seems you removed the devices knowledge of the route you’re shoving traffic to…

By: labnuke99

labnuke99 — Tue, 05 Jan 2010 18:40:20 +0000

Deweywhite – please go ahead and post a new question here and let us know what you have tried to do to resolve the DHCP lease issue.

Some things to look at:

VLAN switch port membership – including DHCP helper statements
DHCP scope exhaustion – is the scope big enough?
Is something quenching the DHCP request broadcast? Use Wireshark to listen for traffic to/from the problem client(s)
client may have static IP address assigned – modify client config

I look forward to seeing your question posted.

By: deweywhite

deweywhite — Tue, 05 Jan 2010 17:19:20 +0000

Sorry,

I have a situation where the a few PC will not pull the DHCP, and all hardware and configurations seem correct. Ant Ideals

By: labnuke99

labnuke99 — Thu, 03 Apr 2008 11:55:58 +0000

Yes, it sounds like something is wrong with the routes. You will need to ensure that your router knows how to get to each VLAN you have defined. If you are using the switch as the gateway to these VLANs, then you should put a route on the router to the switch for those VLANs. I would also take a look to see if EIGRP or some other routing update protocol can be used on the switch to automatically publish these routes to the router for you.