dhcp-superscope-wifi-pocketpc

[news.microsoft.com]

This is my scenario
I have a superscope with 10 scopes inside, each scope has 10 clients
(pocket-pc).
There is Frame Relay Link and a Router between the clients and the dhcp
server .
Each pocket-pc is connected at the LAN by a local Acces-Point.

The symptoms
The clients gets ip address withouth problems.
The bad news is when a client change his phisical location to a new one
(change the scope).
The clients gets the old address finstead of getting the new one from the
new scope.(they change locations three times by day.)
I supposed the problem will correct if a change the lease interval, so I
changed it at one two hour, but it wasn't a solution for me.
I read that the ip address (tombstoned) don't dissapeard from de dhcp.mdb
until it is clean-up, so how can I know how often is cleaning up the
database? and how can i change the interval?


Thanks, sorry my english
Gustavo Uehara

 

[Michael Johnston [MSFT]]

This is caused by the superscope. The superscope allows the DHCP server to assign the clients an address from any of the
scopes within the superscope. Since the clients already have a leave in a scope within the superscope, DHCP will assign the
client the previously used address. If this isn't desired behavior, you need to get rid of the superscope.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[news.microsoft.com]

I appreciate your response.

I think I'm in big trouble because I created the superscope to serve
different subnets in branches in which I don't have a server locally
installed. The superscope is configured in one DHCP server in our Main
Office.

We configured DHCP Relay in our Cisco router (IP Helper Address) so IP
leases could be routed through it. It works OK for desktop PCs but, as I
said, the problem comes when mobile devices change from one scope to another
(some of them connect to 2 or 3 different branches per day).

If I eliminate the superscope I won't be able to serve different subnets.
There is no plan to buy new servers nor licenses in short term!

Do you have any tip to help me work this out?

This is caused by the superscope. The superscope allows the DHCP server

to assign the clients an address from any of the

scopes within the superscope. Since the clients already have a leave in a

scope within the superscope, DHCP will assign the

client the previously used address. If this isn't desired behavior, you

need to get rid of the superscope.

Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the

terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from

 

[Jesse Hottle]

Can you tell me how to get the DHCP server to assign IP
from the superscope form all the scopes defined?

I have a CISCO switch with multiple subnets defined, but
the DHCP sever will not assigned IP unless the request is
detected from a directly connected subnet.

I have a (.252) subnet defined on the primary interface ,
and two class "c" blocks on the other interfaces. The dhco
is receiving the request from the gateway on the (.252)
block and therefore will not grant an IP request.

Any iodea or work arounds for this issue?

Thanks,

Jesse Hottle
Omnicity, Inc.