I've got myself a DHCP server installed on WBEL 3.0 , and there is this strange behaviour ... when the computer comes up and requests a new ip address via the dhcp server it takes aprox. 10-15 seconds.

note : this also happens with other computers...the time till it's up and running is usualy shorter then this, the computers are WinXP Pro with SP2.

Sincerely Robert B

hughesjr

Oct 31 2004, 06:35 AM

Change your line 2 from: authoritative;

to

ignore client-updates;

see if that helps....

Robert83

Oct 31 2004, 06:49 AM

Hi,

same thing, I get a ip address ,but there is something about ip 192.168.1.14 (that computer) not authoritative for subnet 192.168.1.0;

please note I've also got another dhcp server for 192.168.2.0 that gives out ip's via mac addresses, and in that log file I also see 192.168.1.14 showing up...but its denied there, which is ok...

the problem is that some computers (random...) go up really-really fast, and some are waiting for the ip for 15-60sec at the begining, any ideas?

Sincerely Robert B

Robert83

Oct 31 2004, 06:51 AM

hi,

and my /var/lib/dhcpd.leases file is empty... this is normal right ? (I mean I'm only giving ip's via mac addresses)

Sincerely Robert B

hughesjr

Oct 31 2004, 07:52 AM

It looks like, for whatever reason, the acknowledgement sent back to the computer (MAC 00:30:4f:27:43:81) is not being recieved.

Then the computer (MAC 00:30:4f:27:43:81) is re-requesting the IP again.

Since you say you have another DHCP server, and that the other server is also recieving requests from the computer (MAC 00:30:4f:27:43:81), I think the problem is this:

DHCP requests are sent as either a subnet broadcast (192.168.1.255) or a full broadcast (ip 255.255.255.255) (most of the time as a full broadcast ... only as a subnet broadcast if a DHCP relay has been setup).

Your computer (MAC 00:30:4f:27:43:81) sends out a DHCP request, and it gets replyed to by the first server ... request denied ... the computer recieves the denied DHCPACK and sends out another request.

In the meantime, the first request gets to the other DHCP server ... which says, OK ... here is your IP ... but the computer is no longer looking for ACK from that request.

The computer continues in that loop until it makes a request and the DHCP server that you have the MAC listed for actually beats the other server and gives the requested IP to the computer.------------------You should NEVER have more than 1 DHCP server on a subnet (or the same physical network broadcast segment) because of this ... try booting with the other server's dhcp turned off and see if it gives you an address faster.

Robert83

Oct 31 2004, 12:24 PM

Hi,

...then I should create 1 dhcp server for all three subnets?

do you know how can I write the configuration file so that it is as simple as possible.

and then only defining the hosts ... how do I tell the hosts to use the settings of the first subnet second subnet third subnet ? this is the problem that drives me crazy.

Sincerely Robert B

Robert83

Oct 31 2004, 12:29 PM

Hi,

---------------------------------------------------------------------------------------- You should NEVER have more than 1 DHCP server on a subnet (or the same physical network broadcast segment) because of this ... try booting with the other server's dhcp turned off and see if it gives you an address faster. ----------------------------------------------------------------------------------------

does this mean that I can only use one dhcp server in my lan ? (all three companies are connected togeather by wireless devices)

Sincerely Robert B

Robert83

Oct 31 2004, 12:38 PM

Hello,

thank you thank you thank you, I realized something today, and made my week end a really nice one...

after that info you told me...I started searching google for dhcp multi subnet situations

and guess what I found ???? ))

as you know my problem was

dhcp 1 was giving ip's to 192.168.1.x and dhcp 2 was giving to 192.168.2.x but they didn't knew anything about the other subnet.

and then that would happen that dhcp 1 would tell dhcp2 clients access denied.

to fix the problem (as I found out via google) you only need to define a empty subnet in the dhcpd.conf file like this

for dhcp server 1

subnet 192.168.2.0 netmask 255.255.255.0 { } and now it's aware of the other subnet...it will not tell the client computer access denied but it will not give it a ip address...it will let the other dhcp server deal with the problem.

problem solved

thank you!!

Sincerely Robert B

hughesjr

Nov 1 2004, 06:44 AM

I would give all IPs from one DHCP server ... but the blank subnet will work as well. (I never thought of doing it with a blank subnet )

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.