Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DHCP

Status
Not open for further replies.

WheeDoggy

Programmer
Nov 26, 2002
338
TW
Don't remember a way to do this one.........

On a Win98SE w/Realtek 8139, what is the way to bypass the auto DHCP on boot?

Have already attempted ReleaseLeaseOnShutdown=0 in WinReg hoping that this would stop IP renewal on bootup but still waited for timeout.

The problem is that the net isn't always hooked up and there is a 4 day lease although the DHCP may issue a new IP after a couple of hours, and may have a few in one day OR may continually reissue the same IP for 3 months. Christened "STYNAMIC IP" :). Which is why it isn't practical to disable auto DHCP and enter the current IP.

Anyway, It would be preferrable to obtain an IP manually (renew in winipcfg) after bootup when not connected to the network instead of waiting the long timeout during boot.

If this isn't possible, please point me in the direction to lower the timeout.

Thanks
 
Doesn't anyone have an answer to this?

Short version without rants:

Need to bypass the auto DHCP (bootp) on bootup and allow a manual IP renew after boot so the network drivers need to load.
Need to retain "Obtain IP Automatically" setting in network options.

TIA
 
Sorry, but you can't have it both ways...

With all the MS systems you have to pick one way of the other,
UNIX's would let you change without rebooting but you would have to configure the interface manually each time... ( you would still have to put it into DHCP mode to get the address from the ISP... and then configure it manually )

 
Thanks for response DeadEye.

OK, not being the greatest at putting thoughts to words let me try one more explanation.

All that I want to do is if the modem isn't connected, during a boot is to avoid the loooooong boottime.

Basically, if I can cause it to fail quickly on boot by getting 169.xxx.xxx.xxx I would be happy.

My previous firewall would load prior to bootp and cause an instant fail by blocking UDP 67&68 therefore not delaying the boot.
The new firewall loads after bootp which causes the long wait for timeout.

Where are the timeout settings located?

TIA
<cfif IsStressed(objWheeDoggy)>
<!--- 10%/hour/each day --->
<cf_objWheeDoggy BloodPressure=&quot;340%&quot;>
</cfif>
 
I'm not sure if this is what you're looking for but couldn't you do it with hardware profiles. Create one profile with the network card in it and one without it. That way when you choose the one without the network card it wouldn't attempt to locate the DHCP server since none of the networking hardware is installed at bootup. david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top