DHCP quit working

[Iowan]

I know there's a similar thread nearby, but rather than hijack it ...
Dual-boot HP laptop was working fine wired/wireless. After wifi-ing in the restaurant yesterday, I took machine home and plugged back into wired network. No DHCP address (although lights on switches blink). Tried setting up static lease - no go.
Static address works! A manual DNS entry in /etc/resolv.conf got it back on internet, but what happened to DHCP? The Windows side still works via DHCP. This machine uses r8169 driver. Any glitches for this driver?
Is there something I could run on the DHCP server (Breezy) or another machine to monitor packets to see if valid DHCP requests are being sent?
I'm thankful that it will still access network/internet... and equally thankful that the problem wasn't the wireless side (my weakest area), but I'd still like to have it work like it did last Friday...

Problem is similar to bottom of this bug report.

[Iowan]

Update: I commented out my changes in /etc/network/interfaces and /etc/resolv.conf - just to see if it'd play nice today... still not playing nice.
Disabled wireless, unplugged machine and rebooted, no network (although wireless re-enabled itself... the checkbox, anyway). Plugged in the cable, globes spin, no connection.
Built "manual connection" through the applet. First it tried "auto eth0", then succeeded with manual connection. Deleted "auto eth0", rebooted, and built another "auto eth0". Reboot again - same thing. Failure via DHCP (auto eth0), success via manual connection.
Still curious why DHCP has failed.

[Iowan]

[Updated update] Per a suggestion in another thread, I tried commenting out the "option rfc3442" line and removing the reference in the "request" line - rebooted, and got a DHCP address. (Thanks Peter09) We'll see if the "fix" stays fixed...

It should be noted that the actual path is /etc/dhcp3/dhclient.conf. That got edited a couple of posts later than the one I linked.

[xAirrick]

You are the man IOWAN.

Commenting out that line in /etc/dhcp3/dhclient.conf also fixed my DHCP problems

[no_angst]

No doubt! You rock! Thanks!

[Lutin]

Thanks for that. Managed to get my Dell D400 back onto wireless thanks to this.

[shredder12]

btw.. what's the issue with this line containing options rfc3442..??

[Iowan]

Apparently rfc3442 is for classless static routes. There's a bug report here. One would like to think that a DHCP server that didn't understand it would ignore it, but some (my Breezy server for one) just give up, and don't process the request - meaning no DHCP address... at least that's my interpretation - so far.

[wjamoore]

Hi

This didn't help me. Same issue here. Laptop sees the network (full signal) but fails to connect.

I am using a netgear wrn2000 wirless router with no security for now

in iwconfig it has the essid OK but is not associated

also scanning for network gives wlan0 no scan results.

Interestingly I can connect without problem at hotspots, but I may still have an issue there as I couldn't get on the web yesterday

So what is different about wireless hotspots versus wireless routers???

Having trawled the forums for days now I can see that:

1. this is a common problem
2. it is not associated directly with the hardware because I see it on multiple hardware platforms and therefore a global solution should be found. I notice on the forums that the same issue is split mutiple times for computer and wifi card

I think it is a DHCP isue, and for me I think network management is doing something strange. i tried nm & wicd.. same... I tried madwifi... same

any help appreciated

Aaron

[wjamoore]

and another interestinbg point.

What's Samba up to here?

Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/


Listening on LPF/wlan0/00:19:7e:84:7e:44
Sending on LPF/wlan0/00:19:7e:84:7e:44
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
* Reloading /etc/samba/smb.conf smbd only
...done.


Is this relevant or not?

thanks

aaron