Vista doesn't ack dhcp offer

[Doug Tucker]

Here you go....and thank you everyone for your help here!!  Client makes
request, offer is made..then nothing.  Make the registry hack in vista,
wallah, the ack comes back.  Whatever this broadcast flag in vista is
doing, it's expecting "something" from the isc dhcp server it's not
getting, and refuses to ack.  However, talking to my test linksys router
here, allowing the linksys to hand out the ip's, no problem, connects
right away.


sh-2.05b# tcpdump -i eth1 -a -v | grep 00:13:e8:23:e5:a7
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96
bytes

10:24:04.443161 00:13:e8:23:e5:a7 (oui Unknown) > 01:60:1d:00:01:00 (oui
Unknown) SNAP Unnumbered, ui, Flags [Command], length 46
          source link-address option (1), length 8 (1):
00:13:e8:23:e5:a7
10:24:04.463469 IP (tos 0x0, ttl 128, id 462, offset 0, flags [none],
proto: UDP (17), length: 328) default.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:13:e8:23:e5:a7 (oui Unknown), length 300,
xid 0x23c2dee4, Flags [ Broadcast ]
          Client-Ethernet-Address 00:13:e8:23:e5:a7 (oui Unknown) [|
bootp]
10:24:07.086389 IP (tos 0x0, ttl 128, id 477, offset 0, flags [none],
proto: UDP (17), length: 328) default.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:13:e8:23:e5:a7 (oui Unknown), length 300,
xid 0xe620b997, Flags [ Broadcast ]
          Client-Ethernet-Address 00:13:e8:23:e5:a7 (oui Unknown) [|
bootp]
          source link-address option (1), length 8 (1):
00:13:e8:23:e5:a7
10:24:10.085040 IP (tos 0x0, ttl 128, id 499, offset 0, flags [none],
proto: UDP (17), length: 328) default.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:13:e8:23:e5:a7 (oui Unknown), length 300,
xid 0xe620b997, secs 768, Flags [ Broadcast ]
          Client-Ethernet-Address 00:13:e8:23:e5:a7 (oui Unknown) [|
bootp]
          source link-address option (1), length 8 (1):
00:13:e8:23:e5:a7
10:24:18.088653 IP (tos 0x0, ttl 128, id 531, offset 0, flags [none],
proto: UDP (17), length: 328) default.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:13:e8:23:e5:a7 (oui Unknown), length 300,
xid 0xe620b997, secs 2816, Flags [ Broadcast ]
          Client-Ethernet-Address 00:13:e8:23:e5:a7 (oui Unknown) [|
bootp]
10:24:33.096073 IP (tos 0x0, ttl 128, id 550, offset 0, flags [none],
proto: UDP (17), length: 328) default.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:13:e8:23:e5:a7 (oui Unknown), length 300,
xid 0xe620b997, secs 6656, Flags [ Broadcast ]
          Client-Ethernet-Address 00:13:e8:23:e5:a7 (oui Unknown) [|
bootp]

And this is where the client gives up.


On Wed, 2007-09-19 at 15:48 +0100, Phil Mayers wrote:
> > While we do have dhcp relay on our routers for the rest of the network,
> > the network in question is our wireless network, which is segregated.
> > Clients connect to access points that do not do dhcp.  DHCP is done on
> > the gateway/router for the subnet, which is a debian linux box running
> > 3.0.4 isc dhcp.  So in this case, all clients are on the same subnet as
> > the dhcp server.
> 
> To repeat an earlier post: what does a tcpdump/wireshark of the outgoing
> DHCPOFFER look like?
> 
> 
>