[kittydragon]

Normally around 5pm each day my browser, instant messenger, and online game will lose connection for a few minutes at random intervals throughout the evening. I've tried calling my ISP and the Netgear tech support (the maker of my router) and after a gruelling bout of them telling me step by step to assign a static ip address, change some settings and etc. they both told me there was nothing more they could do for me.

My indicators in the system tray will show full signal, and my router shows up in the available wireless connections list, yet I cannot connect to anything. This is what I have when the connection is working:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Vicki>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : BARON
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link WDA-1320 Desktop Adapter
Physical Address. . . . . . . . . : 00-15-E9-3C-0E-5C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, November 06, 2009 12:53:00 P
M
Lease Expires . . . . . . . . . . : Saturday, November 07, 2009 12:52:54
PM

C:\Documents and Settings\Vicki>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Vicki>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 4ms

C:\Documents and Settings\Vicki>ping 74.125.45.100

Pinging 74.125.45.100 with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=53ms TTL=52
Reply from 74.125.45.100: bytes=32 time=42ms TTL=52
Reply from 74.125.45.100: bytes=32 time=47ms TTL=52
Reply from 74.125.45.100: bytes=32 time=44ms TTL=52

Ping statistics for 74.125.45.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 53ms, Average = 46ms

C:\Documents and Settings\Vicki>ping yahoo.com

Pinging yahoo.com [209.191.93.53] with 32 bytes of data:

Reply from 209.191.93.53: bytes=32 time=26ms TTL=53
Reply from 209.191.93.53: bytes=32 time=23ms TTL=53
Reply from 209.191.93.53: bytes=32 time=24ms TTL=53
Reply from 209.191.93.53: bytes=32 time=25ms TTL=53

Ping statistics for 209.191.93.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 26ms, Average = 24ms

C:\Documents and Settings\Vicki>



But when the connection is not working, the pings simply respond that they timed out.


I am at my wits end here, all I can think of now is that maybe there's some kind of interference coming from... aliens? I beg ye gods of tech, share any wisdom you may have.

[kittydragon]

As an additional bit of info, I tried a wired connection from my father's computer, as it is next to the router and modem, but during those blackout periods it still will not work.

[TerryNet]

When the connection is not working you still have the same IP configuration, but the ping to the adapter (192.168.1.2) times out?

[kittydragon]

Actually, pinging that address gets a response now. I didn't check to see if the ip settings changed when it was down though, I guess I will have to wait for the next disconnect to see... I wish it weren't so random!

[TerryNet]

Do the ipconfig /all and then the pings when you lose connection again.

[kittydragon]

Okay, here's the information:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Vicki>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : BARON
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link WDA-1320 Desktop Adapter
Physical Address. . . . . . . . . : 00-15-E9-3C-0E-5C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, November 06, 2009 8:16:39 PM

Lease Expires . . . . . . . . . . : Saturday, November 07, 2009 8:16:39
PM

C:\Documents and Settings\Vicki>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Vicki>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 6ms, Average = 3ms

C:\Documents and Settings\Vicki>ping 74.125.45.100

Pinging 74.125.45.100 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.125.45.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Vicki>ping yahoo.com
Ping request could not find host yahoo.com. Please check the name and try again.


C:\Documents and Settings\Vicki>ping yahoo.com

Pinging yahoo.com [69.147.114.224] with 32 bytes of data:

Reply from 69.147.114.224: bytes=32 time=66ms TTL=51
Reply from 69.147.114.224: bytes=32 time=61ms TTL=51
Reply from 69.147.114.224: bytes=32 time=57ms TTL=51
Reply from 69.147.114.224: bytes=32 time=63ms TTL=51

Ping statistics for 69.147.114.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 66ms, Average = 61ms

C:\Documents and Settings\Vicki>


That last ping occurred right after the connection popped back up.

[TerryNet]

Those results show that the computer is OK, but the router lost internet access.

There may be LEDs on the modem and router to help you determine what's happening--whether the router or the ISP/modem is the cause, but the sure way is to connect directly to the modem (remember to power cycle it when switching devices) to see if the problem continues.

[kittydragon]

Alright, after -finally- getting someone competent from my ISP to talk to me, we've figured that the problem is either in the modem or the cable itself so they're sending a technician tomorrow to look things over. *fingers crossed* I'll let you know if it works.

[TerryNet]

... getting someone competent from my ISP to talk to me ...

That's always a big help! Good luck tomorrow.

[kittydragon]

Success! The problem was a bad modem. After replacing it my speed increased almost 3x and the connection seems to have stabilized.

Thanks for the help tech guys!

[TerryNet]

You're welcome. Glad you got it resolved.

[kittydragon]

*sigh* Well, the modem being replaced increased the internet speed and reduced packet loss, but once 5pm rolled around it started dropping again. They are sending another technician tomorrow, and if they can't fix it then I am going to shave myself bald and run through the streets screaming. If any of you are in the Austin area, watch the news and you'll know if I failed or not!

[JohnWill]

This is a classic sign of an overloaded ISP. In the evening hours starting around 4 PM or so, things get slow.

When it's slow, connect directly to the modem and run the following tests.


Register at DSLReports and run their Line Quality Tests. It's best to run this test with a direct wired connection to eliminate any wireless issues from the results. It's useful many times to run this test several times, and we'd like to see each of the results. Post the results link from the top of the test display page for each test run here.

The link to post is near the top of the page and looks like:

If you wish to post this result to a forum, please copy/paste this URL
http://www.dslreports.com/linequality/nil/2357195 <- sample only, yours will obviously be different!
and your IP will be disguised.

Copy/paste that link here.

Note: You will have to enable PING (ICMP) request response either in your router (if you have one), or in your computer's firewall for direct modem connections. This is very important to get the most important part of the test to run.


DSLReports

Here's also the Line Quality Tests FAQ to help you understand the results. This will answer some questions about the line quality display.