*** From dhcp-server -- To unsubscribe, see the end of this message. ***

This is a resend:


>I have recently encountered two instances where the lease period
>assigned to a client was incorrect.  The proper lease period should
have
>been 14 days and the client was incorrectly assigned 2 minute leases.
>
>The first instance involved the use of a Novell Multiprotocol Router
>with bootp forwarding configured.  We could trace the client's request
>through the router to the server and the server then assigning a 2
>minute lease, but the lease never made it back to the client but it did
>make it to the router.  We found that the wrong version of the bootp
>forwarding NLM was loaded and when the correct one was loaded, the
>problem corrected itself.
>
>The second instance was with a Microsoft DOS client and the problem has
>seemed to resolve itself after a reboot.  In this case the client did
>receive an address, but the lease period was just incorrect.
>
>What I was wondering was why the server decided to give out a 2 minute
>lease period in each case.  Is there a timer based on number of
discover
>messages received, in which it hands out a default lease period, or is
>there something else going on that triggers this type of action?  I had
>never seen this before.  The config file definitely had the correct
time
>of 14 days in it.
>
>Thanks for any help on this issue.
>
>....Jill.
>
>
>
>
>
>
>Jill K. Smith
>Lockheed Martin
>919-541-5323
>[EMAIL PROTECTED]
>http://network.epa.gov:9876
>



------------------------------------------------------------------------------
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.

Archives for this mailing list are available at 
http://www.webnology.com/list-archives/dhcp/dhcp-server

------------------------------------------------------------------------------

Reply via email to