Short DHCP leases not all showing on Server 2008. Too short?

I have a Wlan and that is designed for clients to connect, print, then move back to another Wlan.  I made the DHCP lease 20 minutes so many more clients could connect and print over an hour than I had addresses.  I had read that you could go as short as 1 minute without problems, except for the additional network traffic on that VLAN for DHCP requests, acks.....  

However, I'm seeing that DHCP scope as being full, or almost full, much of the time (491 total addresses) when looking at the statistics.  But when I look at the address leases, only about 150 or so show up.  That 150 usually is about the same as the current number of wireless clients I have on that VLAN.  When it shows a having no addresses left (in statistics) to hand out, it stops handing them out, even though the address leases don't show that many.

This just doesn't make sense to me.  All the other DHCP scopes look correct.  The number of used IP addresses in statistics is the same as the number of leases that are shown.

I've deleted and recreated the scope a few times, but the same thing always happens.

I'm wondering if the lease is too short, where the server won't reassign an address for a set amount of time, no matter how short you set your lease. But that doesn't correspond to what I've read.  

Any ideas?

To nip one idea in the bud, we have just the one DHCP server.  There isn't another server handing out the other addresses in a split scope scenario.  The addresses showing are #.#.#.21, #.#.#.22, #.#.#.30, #.#.#.42... when looking at the list of address leases.
LVL 2
davebuhlAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JeffG2583Commented:
I know in Server 2000-2003 there was a "grace period" for DHCP leases no longer in use. It sounds like this is what you're running into. Try adding the following registry key and restart the DHCP service on the server.

 HKLM/System/CurrentControlSet/Services/DHCPServer/Parameters
 DWORD value: LeaseExtension
 Value measure: minutes

I would set this to something like 10 minutes.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vivigattCommented:
Maybe these articles will help you:
http://technet.microsoft.com/en-us/library/cc783573%28v=ws.10%29.aspx
http://blogs.technet.com/b/csstwplatform/archive/2009/12/17/configuring-a-short-dhcp-lease-for-wireless-users.aspx
In particular, check the following registry keys (in addition to the LeaseExtension key that JeffG2583 mentioned):

HKLM/System/CurrentControlSet/Services/DHCPServer/Parameters
DWORD value: DatabaseCleanupInterval
HKLM/System/CurrentControlSet/Services/DHCPServer/Parameters
DWORD value: DynamicDNSQueueLength
0
davebuhlAuthor Commented:
Thanks.  I made a couple of changes and will see how that affects it on Monday.
0
davebuhlAuthor Commented:
I added LeaseExtension and modified the DatabaseCleanupInterval.

The combination of your two suggestions appears to be working perfectly.

Thanks for the help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DHCP

From novice to tech pro — start learning today.