XP slow to initialise network connections on startup

feenster99

feenster99

feenster99

Associate
Joined
19 Jun 2003
Posts
1,680
Location
West Yorks, UK
Hi all,
Running XP Pro SP2. Whenever I boot my machine, it loads Windows, and I can start playing around, but it takes about another 45 seconds to initialise the network connection. After the 45 seconds or so, the "No Firewall is turned on" bubble pops up and then quickly disappears, then I can connect to the 'net.

Anyone seen this before? It happens regardless of whether I'm using on-board ethernet, or a USB wireless dongle.

Matt
 
Have you tried botting up with no network connection plugged in or disabled? If it makes the bootup faster then thats obveously the problem and you can investigate further.
 
Yeah, it doesn't make any difference. I'm begining to wonder if it might be Avast anti-virus that is hogging more resources than it should. Will have a look round for a more lightweight AV.

Matt
 
How about uninstalling avast and rebooting? See if it gets faster. If not its not the AV.
 
Disable (in Network Connections) any unused adapters (especially things like Firewire or secondary LAN connections).

Ensure there are no DHCP problems with the network adapters that you are using.
 
Hi,
Thanks - have done so - had quite a few in there like VMWare, 1394 and a spare LAN. Will try rebooting later and let you know.
 
feenster99 said:
Hi,
Thanks - have done so - had quite a few in there like VMWare, 1394 and a spare LAN. Will try rebooting later and let you know.
Click to expand...

If you would also like to stop the notices about missing Firewall you can go to Control Panel > Security Center and on the left hand side click 'Change the way Security Center alerts me.'
 
If you're currently using DHCP then you could also try assigning a fixed IP for the PC connection.

Just add a value in the same range that the router uses e.g. if it automatically assigns values from 192.168.0.1 upwards (usually to 255) that just select an ending value higher than that.

Add a high value just to factor in any other devices that might be looking for an auto-assigned IP address - consoles etc.

All depends on how the router is set up though.

Type in ipconfig /all into a command prompt to find out the range if you can't get the values from the router's control panel.
 
Last edited:
Le Samourai said:
If you're currently using DHCP then you could also try assigning a fixed IP for the PC connection.

Just add a value in the same range that the router uses e.g. if it automatically assigns values from 192.168.0.1 upwards (usually to 255) that just select an ending value higher than that.

Add a high value just to factor in any other devices that might be looking for an auto-assigned IP address - consoles etc.

All depends on how the router is set up though.
Click to expand...

DHCP is pretty quick really. The problem happens when you've got network adapters trying to use DHCP when there is no DHCP server available. Firewire adapters are the biggest culprit here.
 
I found XP did this when using an old router which took an eternity to hand out ip addresses using dhcp, fixed ip sorted it.
 
You must log in or register to reply here.
Back
Top Bottom