• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Long bootup delay for TCP/IP

S

Steve309

Member
Hi, I recently installed a 10/100 Ethernet NIC (D-Link DFE-530TX+)and I use it with a DSL modem. I noticed my computer paused for a while at bootup so I logged my bootup and used a program called BootLog Examiner to determine where the delays were. The longest delay by far was 25 seconds for Starting TCP/IP (NETWORK\MSTCP\0001). There are other lines just like this one, but they have 0000 or 0002 at the end. Why is 0001 taking so long? In my network options TCP/IP is bound to my Dial-up adapter, Dial-up adapter #2 (VPN), and my network card. Also, I'm using Windows 98 SE. Anyone know how to shorten that delay? Thanks!
 
If you have DHCP enabled, the reason it is taking so long is that it has to take time to grab an ip from the DHCP server.
 
Hey Guys. I have the exact same problem, too. So, would it be OK to disable DHCP?
I also had a whole lot of problems with my NIC that caused intermittent crashes. I have changed from a D-Link 528 10BaseT NIC to a Linksys PCI 2 10 BaseT NIC. Less crashes from hereonwith, but at times, I get some form of lag that causes my Winamp and mouse movement to stutter.
Do you guys have experienced similar problems? If so, how to get solve this?
Help me please...
Thanks!
 
Possbile solution (depends on your ISP), assign an IP address along with the Default Gateway, Subnet Mask and possbile DNS configuration. Use the WINIPCFG program to get this information from what your DSL modem is currently assigning your computer.
 
Problems solved!
Thanks a lot H.A.R.M.!
Still some stuttering when I am on the net... may be it's some hardware problems... but no more crashes..
Thanks again.
 
Good for you Voltare 😉. Unfortunately my IP isn't static so I can't enter anything in for the IP or Gateway. Oh well...
 
Sigh... problems again.
I tried changing back the NIC to my D-link card... 5 crashes within 2 hours!! What seems to be the problem?! I have tried keying all those IP numbers and all, it did help out with the boot time (thanks again, HARM), but not with the crashes. I have only used DSL for less than a month and my computer has crashed not less than 30 times.
Should I just change to a better (more expensive?) NIC? Or is it just Win98SE being totally unstable when using DSL? Or go back to using dialup?

Any way out of this, guys?
 
I think that you have answered your own question Voltaire with the NIC change.

The only other advice would be the classic 'try the latest drivers' thing.

You may want to try a whole different brand of NIC to possibly avoid driver conflicts. Personally, I have had good success with Realtek and the SMC 1211TX. Both are in the $10-15 range.

viz
 
Viz,
Thanks a lot viz... but my system is not entirely stable. I still get random crashes after NIC change. The D-link NIC, which is provided by my ISP, is totally unusable. The LinkSys is OK, but it causes some stuttering when I am online. The system would freeze intermittently... this is especially apparent when I have WinAmp on, when you really notice the stuttering. I have tried everything that I can think of... driver change, cable change (RJ45 = CAT5 ?), NIC change... I still can't have a system that does not crash on me 5 times a day. This is pretty frustrating.
Probably if I gave you the specs of my system then, perhaps a better diagnosis can be made. Here goes:
ASUS P3V4X/PIII 600E @ 800 on standard HSF/Samsung PC133 128MB CAS3/IBM 34GXP 20.4GB/Guillemot GeForce2 MX/SBLive! MP3+/Linksys PCI 2 NIC (partially stable)/D-Link 528 NIC (totally unstable)

Thanks in advance for your help!
 
I'm also using a D-Link NIC (DFE-530TX+ 10/100) and Windows 98 SE with no crashes whatsoever. Have you tried un-overclocking your processor or at least slowing it down a little? In order to get the 800mhz did you overclock your system bus or just change the multiplyer? Maybe your NIC (or other components) can't take the extra bus speed.

BTW, my ISP (Bell Atlantic/Verizon) uses a Westell DSL modem and WinPoET software for the connection.
 
Hey Steve, I believe my D-Link NIC is a lower model than your. I have a D-link DE-528. I heard that this model is not a really reliable model.
It has been a long time since I have looked at my bus speed settings on the PCI bus, but I believe I am running on 33Mhz on PCI Bus and 133Mhz on CPU/DRAM. I am using a VIA chipset mobo, which allows that. But you have a point there, Steve. I will post an update after unclocking the CPU.
Sigh... there were days when my systems could be turned on for 5 days without a single crash when I was using dialup. I had a Pentium 200MMX@265 running on standard HSF for days without a single crash and so did my PIII600E@800 in those days.
Thanks a million, Steve 🙂
 
I just had a similar problem with my puter. It was taking 3 minutes or more to boot. I just changed my NIC card TCP/IP to a static IP addy since my DSL gateway/router is not set up to assign one. I believe the computer is waiting for an address and will wait for a specified time before it gives up and continues with the boot. I also have the DFE-530TX+ from DLink. They must be pretty standard.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top