Hello,
I have a stupid question about how to configure the ISC DHCPD to
work with
Vista/Win7. At home I have XP and Linux systems running. They all will
broadcast
out to the network to find the server and request and address/lease.
The DHCPD server is configured to hand out the same address, based
on MAC
to all the machines/switches/etc. that are running internally. The
problem comes in when someone with a laptop running Vista or Win7 comes
over. According to M$ they
changed their DHCP client in Vista and 7 to rely on broadcasting to get
address.
From digging on the network, it seems to be that the broadcast flag
needs
to be enabled on the server side. Otherwise when clients beacon out to
get an
address, the server doesn't respond to it. (perhaps the incorrect choice of
words for the behavior)
I've dug through the ISC docs for the daemon. I thought the
always-broadcast command would do it... Unfortunately that is not the
case. There didn't seem to
be anything in the GNHLUG email archives about this problem.
If I disable the daemon on the server and use the one on the router,
the Windows
boxes are happy... But that makes me unhappy. I'm at my wits end
trying to get it
figured out.
The server in question is running CentOS 5.4 with dhcp-3.0.5-21
running. The running config is attached. I'm sure I there are multiple
things that could be set up better but it passes parsing and works, at
least until someone visits.
Any and all help is greatly appreciated. Thanks in advance!
- Todd
#
# dhcpd.conf
#
server-identifier my.domain.net;
default-lease-time 86400;
ddns-update-style ad-hoc;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
option domain-name "my.domain.net";
option domain-name-servers 192.168.1.10,68.87.71.226,68.87.73.242;
option netbios-name-servers 192.168.1.10;
always-broadcast on;
authoritative;
# these were for setting up the comcast modem... ignore
#option domain-name-servers 68.87.64.140,68.87.66.135;
subnet 192.168.1.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.1.101 192.168.1.200;
}
host dd-wrt.my.domain.net {
hardware ethernet 00:1A:70:71:6E:66;
fixed-address 192.168.1.2;
}
host dgs-1224t.my.domain.net {
hardware ethernet 00:24:01:63:9a:4b;
fixed-address 192.168.1.5;
}
host chaos.my.domain.net {
hardware ethernet 00:50:DA:7D:66:42;
fixed-address 192.168.1.10;
}
host iscsi.my.domain.net {
hardware ethernet 00:0f:3d:88:2c:a3;
fixed-address 192.168.1.11;
}
host myth-backend.my.domain.net {
hardware ethernet 00:13:D3:E9:DD:0D;
fixed-address 192.168.1.12;
}
host linkstation.my.domain.net {
hardware ethernet 00:16:01:bc:3c:54;
fixed-address 192.168.1.13;
}
host epson810.my.domain.net {
hardware ethernet 00:00:48:76:b1:c9;
fixed-address 192.168.1.18;
}
host ps20fe54.my.domain.net {
hardware ethernet 00:c0:02:20:fe:54;
fixed-address 192.168.1.19;
}
host mayhem.my.domain.net {
hardware ethernet 00:a1:b0:80:37:6b;
fixed-address 192.168.1.21;
}
host entropy.my.domain.net {
hardware ethernet 00:0c:76:c0:37:90;
fixed-address 192.168.1.22;
}
host delta-s.my.domain.net {
hardware ethernet 00:0F:3D:88:2C:99;
fixed-address 192.168.1.23;
}
host mythtv.my.domain.net {
hardware ethernet 00:E0:18:BF:2A:D8;
fixed-address 192.168.1.24;
}
host myth-bedroom.my.domain.net {
hardware ethernet 00:16:44:86:72:67;
fixed-address 192.168.1.25;
}
host myth-livingroom.my.domain.net {
option broadcast-address 192.168.1.255;
hardware ethernet 00:26:2d:10:b9:5c;
fixed-address 192.168.1.26;
}
host jenlaptop.my.domain.net {
hardware ethernet 00:13:E8:87:68:97;
fixed-address 192.168.1.100;
}
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
