I know mine doesn't take nearly 1.5 minutes or at least it doesn't take that long before I can get to Winbox. I think it waits about 30s and then sets a 169.254.x.x. While it is searching for a DHCP lease, I can look at Winbox which will fail when it sets that 169.254.x.x.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Fri, Aug 20, 2010 at 4:01 PM, Justin Wilson <li...@mtin.net> wrote: > The whole thing is windows takes so long if there is no DHCP server > available. For example, plug into a fresh Mikrotik with no configuration. > How long does Windows take to time out if it is set to DHCP? I have timed > this at 1.5 minutes. My mac only takes 17 seconds to say “hey there is no > DHCP server I will auto assign a 169 IP”. What I am looking for is a way to > tell Windows don’t wait 1.5 minutes before you assign a 169 IP. Only wait > 20 seconds or whatever. > > Sure you can assign a static IP and lessen this time, but assigning that > IP takes time to do and undo. > > The best solution I have seen so far is Barnes’s suggest for a program > that lets you change networking profiles. I was hoping someone knew of a > registry key you could edit. Something like DHCP_TIMEOUT=20s. Instead of > DHCP_TIMEOUT=120s. > > Justin > -- > Justin Wilson <j...@mtin.net> > http://www.mtin.net/blog – xISP News > http://www.twitter.com/j2sw – Follow me on Twitter > Wisp Consulting – Tower Climbing – Network Support > > > > ________________________________ > From: John Valenti <vale...@lir.msu.edu> > Reply-To: WISPA General List <wireless@wispa.org> > Date: Fri, 20 Aug 2010 15:44:34 -0400 > To: WISPA General List <wireless@wispa.org> > Subject: Re: [WISPA] Changign DHCP timeout XP/WIn7 > > Justin, > I don't quite understand what you are trying to do, so I can't offer > suggestions. Can you elaborate? > > (I use a Mac generally, and have that configured with several profiles. But > sometimes I use Windows, I know that supports profiles but I've never > bothered setting them up.) > > On Aug 20, 2010, at 2:37 PM, Justin Wilson wrote: > >> All fine and dandy but if you are plugged into a standalone device >> runnign a DHCP server does you no good. How many times has everyone been at >> a tower site wanting to go home only to have to wait 1-2 minutes until DHCP >> times out? Then if you have to reboot the device or something. 3 reboots >> and you have waster 5-10 minutes waiting on windows. >> - > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
