Network slow to start up

[Tom K.]

When I boot my Vista Ultimate system the desktop appears in an acceptable
time, but the networking doesn't start till maybe 5 minutes or so later. It
always does start, but I either have to wait it out or "Diagnose and Repair"
it to force it to start. As a result I always have to manually mount my NAS
drives after the network connection is active.

Dell 8400, 1.5GB RAM, Broadcom 10/100 wired ethernet, all current drivers
and BIOS, OS fully patched with standard services running, Norton 360
AV/Firewall/etc., NetGear RP614v4 router with current firmware

Any ideas why it's taking so long?

Thanks,

Tom

 

[AlexB]

Just a thought. I have the same problem but it did not bother me since, I
found what I consider an explanation.

What if you leave your LAN alone and come back in 10 minutes. Vista has a
lot of territory to cover after you turned it on. It checks the integrity of
the system, checks for possible downloads, sees if some upgrades that have
already been downloaded but not yet installed should be, perhaps some
indexing takes precedence.

If this is an issue, do Vlite. You have to disable some start up services
that also take time .... to start up. There is an accurate description of
which services are dispensable but I do not have that link at hand. You can
search the web.

 

[DanS]

When I boot my Vista Ultimate system the desktop appears in an
acceptable time, but the networking doesn't start till maybe 5 minutes
or so later. It always does start, but I either have to wait it out
or "Diagnose and Repair" it to force it to start. As a result I
always have to manually mount my NAS drives after the network
connection is active.

Dell 8400, 1.5GB RAM, Broadcom 10/100 wired ethernet, all current
drivers and BIOS, OS fully patched with standard services running,
Norton 360 AV/Firewall/etc., NetGear RP614v4 router with current
firmware

Any ideas why it's taking so long?

Thanks,

Tom

Quick troubleshooting......could be a DHCP issue, if your are using DCHP.
It could also be a negotiation issue between the rtr and PC, depending on
what type of wireless security is set up.

DHCP is the quickest to check.....Setup your wireless with a static
IP/Default Gateway/DNS server and see if the problem goes away. Pick any
unused IP on the subnet, and for the D G/W & DNS Server enter the IP of
your wireless rtr.

Regards,

DanS

 

[AlexB]

OP:

DanSS:

It is just pathetic.

 

[DanS]

OP:

It is just pathetic.

Sorry, an honest mistake yes, but by no means pathetic. One less thing to
troubleshoot.

DHCP still applies.

 

[Tom K.]

Thanks for the thought, AlexB. I usually don't have that urgent an issue
getting onto my PC that I can't wait out the network delay, like you
suggest, but it the drive mounting failing that's really annoying. Maybe
I'll just write a script to mount them so I can run it after the network is
up. Seem like a lame solution, but it would work.

 

[Tom K.]

Quick troubleshooting......could be a DHCP issue, if your are using DCHP.

It could also be a negotiation issue between the rtr and PC, depending on
what type of wireless security is set up.

DHCP is the quickest to check.....Setup your wireless with a static
IP/Default Gateway/DNS server and see if the problem goes away. Pick any
unused IP on the subnet, and for the D G/W & DNS Server enter the IP of
your wireless rtr.

Thanks, DanS, I'll give that a try. This being my primary system, and
always connected to the same port, using a static IP won't be an issue. All
my "visiting" laptops can keep using DHCP. The original LinkSys router I
had on my network failed and I replaced it with a less expensive NetGear
device. I haven't been particularly impressed with it's performance even
before I introduced Vista to my network, so maybe it's just the way the
NetGear router is handling DHCP and Vista.

Tom

 

[DanS]

Thanks for the thought, AlexB. I usually don't have that urgent an
issue getting onto my PC that I can't wait out the network delay, like
you suggest, but it the drive mounting failing that's really annoying.
Maybe I'll just write a script to mount them so I can run it after
the network is up. Seem like a lame solution, but it would work.

It is a lame non-solution. And sorry about the wireless part of my initial
reply. Most people don't specify a wired network when asking questions, and
I skimmed over it so fast, saw the beginning of the word wired, and it just
registered as wireless.

The network is a service. A service is supposed to start before a user is
logged in. That is why you can fire up a Windows box and not log in, ever,
and other network PC's are supposed to be able to have access already.

It would be interesting to see if there is network access to your Vista PC
w/o being logged on. Maybe something that is happening at log in that is
killing it for some reason and it takes a while to come back.

Also, did you try disabling IPv6 ? IPv6 can cause troubles for *some* users
that don't utilize IPv6.

 

[Tom K.]

It is a lame non-solution. And sorry about the wireless part of my initial

reply. Most people don't specify a wired network when asking questions,
and

I knew what you meant. And like you said, it makes no difference to DHCP.
Guess I'm not most people. I got into my house before the drywall was up
and ran CAT5 everywhere.

It would be interesting to see if there is network access to your Vista PC
w/o being logged on. Maybe something that is happening at log in that is
killing it for some reason and it takes a while to come back.

Since my daughter moved out, and I no longer need to monitor teenage
computer usage, I removed all the other users and just do autologon to my
ID. I'll reconfigure and test that if all else fails.

Also, did you try disabling IPv6 ? IPv6 can cause troubles for *some*
users
that don't utilize IPv6.

IPv6 is disabled.

Thanks, again.

 

[Curt]

Check if network discovery is on

I knew what you meant. And like you said, it makes no difference to DHCP.
Guess I'm not most people. I got into my house before the drywall was up
and ran CAT5 everywhere.


Since my daughter moved out, and I no longer need to monitor teenage
computer usage, I removed all the other users and just do autologon to my
ID. I'll reconfigure and test that if all else fails.


IPv6 is disabled.

Thanks, again.

 

[Tom K.]

DHCP is the quickest to check.....Setup your wireless with a static
IP/Default Gateway/DNS server and see if the problem goes away. Pick any
unused IP on the subnet, and for the D G/W & DNS Server enter the IP of
your wireless rtr.

Thanks for the suggestion, DanS. Static IP did the trick.

 

[DanS]

Thanks for the suggestion, DanS. Static IP did the trick.

Your welcome.

You can now either leave it that way, or troubleshoot DNS.

Regards,

DanS