Slow network connection at boot

Kaktussoft said:

Answer #10 please

Will ping now.

1. Disabled sharing did not seem to help.

2. Result of ping;

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping cnn.com
Pinging cnn.com [157.166.226.25] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 157.166.226.25:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>

whs said:

1. Disabled sharing did not seem to help.

2. Result of ping;

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping cnn.com
Pinging cnn.com [157.166.226.25] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 157.166.226.25:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>

Ping another site for example google.com please. Ping when you're having problems

That was right after boot when the network icon in the taskbar was noodling. I'll try Google next time I reboot.

Here is the Google.com ping result. Although it had not yet connected, I got this:


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping google.com
Pinging google.com [173.194.37.96] with 32 bytes of data:
Reply from 173.194.37.96: bytes=32 time=20ms TTL=51
Reply from 173.194.37.96: bytes=32 time=20ms TTL=51
Reply from 173.194.37.96: bytes=32 time=20ms TTL=51
Reply from 173.194.37.96: bytes=32 time=24ms TTL=51
Ping statistics for 173.194.37.96:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 24ms, Average = 21ms
C:\Windows\system32>

Good news - I might have found the culprit.

My router was set to check for updates on every boot. I unchecked this option and now the connection seems to be instant. Will have to verify this with future boots.

The last ping gave me the idea - it did ping Google.com even though the icon was still noodling. Thank you Kactussoft for insisting I do that. You are my hero.

Update: after 3 more boots I can confirm that the internet connects immediately. What apparently happened is that the OS did not release the line whilst the router was looking for updates.

The fact that my ping google.com worked whilst the line was still not up gave me the idea to inspect the router settings closely. And voila, the culprit was found.

Well I think you just found the little culprit causing your problem.
Auto update. I hate auto update anything.

Good job Kactussof. You never gave up.

That's good know and thanks for the follow up. Question is; How did it get set in the first place?

carwiz said:

That's good know and thanks for the follow up. Question is; How did it get set in the first place?

That is a good question. It must have been the default because I had that problem all along.

Why was it a router problem? All connected wifi devices don't have this problem!

Was router looking for new firmware after each router reboot? It doesn't boot so much anyway.
Glad you solved it, glad you call me a hero ;-)