*** From dhcp-server -- To unsubscribe, see the end of this message. ***
I've had a similar problem with a smaller subnet of 16 IP's, and for
some reason the DHCP server assigns .146 <not in its range and already
in use> to one system, and I'm unable to get it to stop. Most, but not
all, of the other systems get proper addresses, but randomly a system
will go out of range and stay there, necessitating a rework of my IP
range. I'm currently using pl22. I'm enclosing my dhcpd.conf also,
maybe I'm doing something silly.
-----------------------------
server-identifier suldam.cust.io.com;
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.240;
option broadcast-address 206.224.85.159;
option routers 206.224.85.145;
option domain-name-servers 206.224.85.147, 199.170.88.11;
option domain-name "cust.io.com";
allow unknown-clients;
subnet 206.224.85.144 netmask 255.255.255.240 {
range 206.224.85.150 206.224.85.154;
}
I have the range .144 to .159, for the record, but only 3 systems seem
to currently respond properly to DHCP, the rest are all static. I've
shut down the DHCP server to let everything time out to see how that
goes.
Diamon
-----------------------------------------
CLIFFORD ILKAY wrote:
> Hi,
>
> I am running dhcp 2.0b1pl6-2 on Red Hat 5.2 with kernel 2.0.36. I have one
> client on the network so far, a Windows 98 box. The first time that I
> started dhcpd, the dhcpd.leases file was empty. When the Win 98 client
> acquired an IP address, it acquired 192.168.1.54 as its IP number. Why I
> find this unusual is that my IP address pool is from 192.168.1.20 to
> 192.168.1.100. There are *no* other machines on the network. Several times,
> I have tried clearing the dhcpd.leases file and released the IP address and
> renewed the lease on the Win 98 client just to see what IP number it would
> acquire. It consistently acquires .54. I have never seen this behaviour
> before. Experience tells me that it should acquire .20 if no other machines
> are on the network. I can ping and browse and all that good stuff but
> inquiring minds have to know. You can see the contents of my dhcpd.conf
> file below. I substituted a bogus domain for the real one. Any idea why
> this is happening?
>
> # begin dhcpd.conf
> default-lease-time 7200;
> max-lease-time 14400;
> option domain-name "mydomain.com";
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> option domain-name-servers 165.154.140.31, 165.154.140.32;
> option netbios-name-servers 192.168.1.1;
> option netbios-dd-server 192.168.1.1;
> option netbios-node-type 8;
>
> subnet 192.168.1.0 netmask 255.255.255.0
> {
> range 192.168.1.20 192.168.1.100;
> }
>
> # end dhcpd.conf
>
> Regards,
>
> Clifford Ilkay
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
