win 2k boots slow (verizon dsl?)

[BZ]

on my new pc (specs below) windows 2000 takes a really long time to boot up and shut down - much longer than than on my old install on a much slower computer. both are running about the same things - sql server 2000, IIS, verizon DSL, and various apps (not that many yet - 2 day old install). everything else on this new computer is much faster than the old one, but on bootup it takes about 3-5 minutes after the desktop displays before I can click on the verizon DSL dialer (winpoet). shut down also takes a long time

during this delay, most programs work, but some, such as "add/remove programs" doesn't.
I installed win2k SP3, and this seemed to help a little (old pc running SP2)

now just to make this totally undiagnosable: on my old computer I had this same kind of boot slowness for a while, and then it went away, and I never could remember what caused it or fixed it.

Any ideas would be much appreciated. I have ghost so I don't mind trying crazy things
thanks

specs:
p4 2.4 ghz
asus p4pe mobo
512 mb ddr 333 ram
2 udma hdds
1 tdk velo cd (that may be failing - could be related?)

 

[mattbta]

I've had several problems that caused my slow boot up on systems.

1st- do you use an Nvidia vid card? Have you installed detonators? You might try disabling the nvidia driver helper service. This sped up my boot times on the nvidia box.

2nd- how are your DNS servers configged? Are you joining a domain? When my DNS server wasn't configged correctly and the clients tried to logon, it took forever before it times out and gave up on locating the DC.

These were my problems, but likely totally unrelated to yours. FWIW.

 

[BZ]

thanks - this IS an nvidia (geforce 440 mx) card - I had already disabled the driver helper service, and that might have contributed to the speed up I've gained so far -
but what are detonators? (I did a search and see that they are drivers) I installed the drivers that came with the card (6.13) - are detonators good, or something to stay away from?

as for DNS and domains, its a standalone pc with no LAN and the only networking via DSL, and I didn't change anything from the windows install defaults except to install winpoet and IIS - Is there somewhere I should look for settings on those?

Also, is there any way to know exactly what it is doing during startup? so I could see what is active during that pause? there's no disk activity

thanks again

 

[mattbta]

Detonators are drivers as you found out. They load that driver helper service, and that caused a huge slowdown on my systems. There are some other miscellaneous network services that might try to load and have a default timeout period set really high. Try looking around for xp boot stuff....I know you're running 2k, but they have guides out for xp to help get the boot times down. You might try the bootvis utility, but I'm not sure if that's xp only.

 

[Woodchuck2000]

Check the event viewer for any errors - that may shed some light on anything going wrong during startup.

 

[Pilsnerpete]

"...5. Open the MMC and add the Group Policy snap-in, then open the Group Policy editor. Go to Computer Configuration/Administrative Templates/System/Logon and find the policy "Maximum retries to unload and update user profile." Do not click "Disable" nor "Not Configured" as that just will use the default of 60. Rather, lower the # of tries to unload downward from 60. I figured, "If you can't unload it, don't bother trying", so I set mine to 0 and shutdown is (finally!) instantaneous once again." Taken from a search I did on google for slow shutdown 2k OR 2000.


Pete

 

[BZ]

nice - that knocked 60 seconds off my shut down time.

now I think the startup problem is similar - its exactly 60 seconds delay too.

the event log registers this, just before everything becomes useable:

warning: DHCP event ID 1007
Your computer has automatically configured the IP address for the Network Card with network address 00E018D628EC. The IP address being used is 169.254.123.183.

I tried searching on this and people are saying to set the IP manually in the DHCP server -- but I'm not running a DHCP server as far as I can tell (none shows up in services list)

 

[LiekOMG]

Same problem here. Running XP and Verizon DSL. I don't have any problems with shutdown, but I have to wait about 1 minute before I can use any programs once my desktop appears. It has nothing to do with any Nvidia drivers. If i turn off my DSL modem and start windows, the problem is gone. I assume its trying to assign me an IP or something like that during this 1 minute. And I don't think I can set it manually since Verizon DSL gives me a dynamic IP, not static. I've lived with this 'issue' for about a year now. It would be great to finally find a solution.

 

[johnlog]

>If i turn off my DSL modem and start windows, the problem is gone. I assume its trying to assign me an IP or something like that during this 1 minute. And I don't think I can set it manually since Verizon DSL gives me a dynamic IP, not static. I've lived with this 'issue' for about a year now. It would be great to finally find a solution. <

Easy solution. Do like I do and never turn off your DSL modem. It takes a long time to shake hands with your ISP.

My DSL modem is turned on 24/7 and have not had any problems with it. It is on when my computer is shut down.

 

[LiekOMG]

Easy solution. Do like I do and never turn off your DSL modem. It takes a long time to shake hands with your ISP.

Well thats the thing, I DON'T turn off my DSL modem - its always on. But, I do have to turn off my PC every night. And when I turn it back on in the morning, i have to wait that 1 minute delay.

 

[BZ]

same here - I'm pretty sure this is a timeout thing - its exactly one minute, suggesting 60 retries. I've searched on this and can't find any solutions (that I understand or seem like they apply)

 

[Doh!]

Originally posted by: BZ
nice - that knocked 60 seconds off my shut down time.

now I think the startup problem is similar - its exactly 60 seconds delay too.

the event log registers this, just before everything becomes useable:

warning: DHCP event ID 1007
Your computer has automatically configured the IP address for the Network Card with network address 00E018D628EC. The IP address being used is 169.254.123.183.

I tried searching on this and people are saying to set the IP manually in the DHCP server -- but I'm not running a DHCP server as far as I can tell (none shows up in services list)

Check you network card's settings (TCP/IP). There you'll see the DHCP options. Turn off "automatically configure....." and manually input the ip addy as noted above. Also, check the services list and find out whether or not "DHCP Client" exists (and the related settings).

 

[LiekOMG]

Hmm, i've looked everywhere under my network options, and I can't find *anything* that refers to DHCP. I've checked under TCP/IP in both my Verizon DSL connection and under the 'local area connection'. I can't find DHCP anywhere. However, there is a DHCP service running.

 

[BZ]

well I found it, but it didn't work

in device manager, network and dialup connections right-click winpoet connection for properties (you may get a stupid wizard first, give it the information and it will go away)

then you get winpoet connection properties dialog box - click the networking tab. click properties for the first item - tcp/ip

this gives you the choice between "obtain IP address automatically" (checked) and "use the following IP address.

I entered in 169.254.123.183 since that's what the DHCP error was assigning, rebooted, still got the delay, and the connection didn't work! (error 720: no ppp control protocols configured)

so I set it back and everything is fine, but I still have the delay

 

[Doh!]

Originally posted by: DOACleric
Hmm, i've looked everywhere under my network options, and I can't find *anything* that refers to DHCP. I've checked under TCP/IP in both my Verizon DSL connection and under the 'local area connection'. I can't find DHCP anywhere. However, there is a DHCP service running.

Are you just looking for the word "DHCP"? Or are you looking for a description of a dhcp service such as "obtain an ip address automatically"? What do you mean you can't find "anything"? You're running windows right? This dhcp has been available at least since win95 and XP definitely has it as long as you have a network card. That option will show up even if you're not connected to anything. It's a part of tcp/ip settings. It just doesn't disappear.

 

[Doh!]

Originally posted by: BZ
well I found it, but it didn't work

in device manager, network and dialup connections right-click winpoet connection for properties (you may get a stupid wizard first, give it the information and it will go away)

then you get winpoet connection properties dialog box - click the networking tab. click properties for the first item - tcp/ip

this gives you the choice between "obtain IP address automatically" (checked) and "use the following IP address.

I entered in 169.254.123.183 since that's what the DHCP error was assigning, rebooted, still got the delay, and the connection didn't work! (error 720: no ppp control protocols configured)

so I set it back and everything is fine, but I still have the delay

Dump that junky connection software (winpoet). Winpoet v4 and higher actually uses winXP's native pppoe. Just use Xp's default dsl connection software or use RASPPPOE.

 

[LiekOMG]

Thanks a lot Doh! I inputted the IP for the network card, and the delay is now gone! Instant booting. Finally! Thanks again.

 

[BZ]

DOACleric, did you do the same thing that I described above, and it worked for you? or did you do something different?

 

[LiekOMG]

Originally posted by: BZ
DOACleric, did you do the same thing that I described above, and it worked for you? or did you do something different?

I'm running XP, so i use the built in PPPoE that XP offers. I simple opened up the TCP/IP tab for my network card (listed as "local area connection"), and typed in that IP and subnet mask that was listed in the event viewer. Rebooted, and the delay was gone.

 

[johnlog]

Doh!,

>Dump that junky connection software (winpoet). Winpoet v4 and higher actually uses winXP's native pppoe. Just use Xp's default dsl connection software or use RASPPPOE. <<<

That is exactly what my DSL ISP told me to do (use XP's native pppoe) and it has worked perfectly from day one. That is after I installed the NIC myself the SBC children techs could not install. Don't know how some persons kept on using that winpoet thing in XP unless they did not read any instructions at all.

 

[Doh!]

Originally posted by: BZ
DOACleric, did you do the same thing that I described above, and it worked for you? or did you do something different?

He manually configured the network card settings. You, on the other hand, made changes to the winpoet pppoe adapter's settings.

According to your post, I see that you're running Win2k, not XP. Again, depart with winpoet and start using RASPPPOE (even NetVoyager will do or any other pppoe connection software other than winpoet which has been nothing but trouble for many users). Personally, I won't use anything other than RASPPPOE 'cause it's very small and will do everything I need (i.e., changing MTU and other values).

 

[BZ]

got it working!
thanks everyone for the help.

being always reluctant to install new software, I tried again to manually configure the IP address and this time it worked. everything the same as above but I did it to local area connection instead of winpoet connection

thanks again