Author Topic: Slow DHCP  (Read 1476 times)

redmondmj

  • Zen Apprentice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Slow DHCP
« on: August 12, 2008, 11:08:05 pm »
Hello:

I am finding that the DHCP server is slow to lease IP's to my Windows machines. When a machine is first connected it takes 30 seconds-1 min. before an IP is obtained from the DHCP server. When I connect the same machines to a home WAP running DHCP they obtain an IP immediately.

I am running DNS Cache and have tried changing the DNS settings in the DHCP config.

I have attached my dhcpd.conf:
eth5 is my external.

Code: [Select]
# extra options
# RFC3442 routes
option rfc3442-classless-static-routes code 121 = array of integer 8;
# MS routes
option ms-classless-static-routes code 249 = array of integer 8;

ddns-update-style none;

option domain-name-servers 24.222.0.33, 24.222.0.5;


default-lease-time 1800;
max-lease-time 7200;




shared-network eth5 {

option routers 24.222.X.3;
option domain-name-servers 24.222.X.3;

        default-lease-time 1800;
        max-lease-time 7200;



subnet 24.222.X.0 netmask 255.255.255.248 {
        }


}

shared-network eth1 {

option routers 192.168.1.254;
option domain-name-servers 24.222.0.33;

        default-lease-time 86400;
        max-lease-time 129600;



subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.166 192.168.1.220;
        }


}


Any suggestions as to where to look are welcome!

Thanks,

javi

  • Zen Hero
  • *****
  • Posts: 1042
  • Karma: +0/-0
    • View Profile
Re: Slow DHCP
« Reply #1 on: August 13, 2008, 04:12:04 pm »
Sometimes the DCHP leases can take longer if you have an issue in your network devices, typically a switch.

You can request an IP while tailing the content of /var/log/syslog, and you should be able to see when the DHCP server is aware of a client machine requsting an IP.

redmondmj

  • Zen Apprentice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Slow DHCP
« Reply #2 on: August 14, 2008, 01:06:43 pm »
That was the issue. I found that spanning tree was enabled, but not properly configured on a switch. Thanks for the help!!