From: "Aron Eisenpress" <os2-wireless_users@2rosenthals.com>
Message-ID: <45102158.2030605@eisenpress.com>
Date: Tue, 19 Sep 2006 12:56:56 -0400
Organization: City University of New York
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.13) Gecko/20060425
MIME-Version: 1.0
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless]Re: DHCP Problems
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

On Sun, 03 Sep 2006 10:54:09 -0400 (EDT) you said:
>On Sat, 02 Sep 2006 21:21:43 -0400 (EDT), Hakan wrote:
>
>>Thank you, Stan, I'll try this when I visit this office again in a
>>month or so.  I was not familiar with this file.  Is there perhaps
>>another file where the default timeout -- 60 seconds -- can be changed?
>>
>
>Check file:
>	\MPTN\BIN\setup.cmd
>There is a command:
>	dhcpstrt -i lan0 -d 10
>
>The value after the '-d' is the timeout value.  I have my timeout
>set to 10 seconds.  I've seen other recommendations for using zero,
>but ten has worked well for me.


I know this is a little late, but here are some more DHCP tips that may
help...

1) If you want to totally get rid of the DHCPSTRT delay, you can run that
    in another process - this way it runs asynchronously and you also get
    rid of the message and reply if there's no DHCP response.  (You can
    use DHCPMON to see what's going on if you need to.)  All you need to
    do is replace the line above with

      detach dhcpstrt -i lan0 2> nul

2) The file mptn\etc\dhcpc.db saves previously obtained lease and option
    information.  If you can't get a lease after changing to another 
server,
    you can try erasing this file to get rid of this history.

3) Back at Warp 4, apparently the mptn\etc\dhcpdc.cfg file didn't request
    off of the appropriate options, and so the server might not have been
    asked to return a router address or other useful bits of information.
    (I remember running into that problem myself.)  You can check that the
    file includes lines for option 3 (router), option 6 (dns), and
    option 15 (domain name).  This wouldn't be a problem with an eCS
    install, but I'm not sure what would happen on an upgrade from
    a Warp 4 install with the problem.

    There are some good tips (including this) in Al Savage's old OS/2
    installation information at
     http://asavage.dyndns.org/OS2/Warp4Install/Warp4Install.html .

--Aron