I have been trying to fix this for almost a year and have resolved to asking for help. Here is the problem:
Loading web pages is very unstable. Whether pages are loaded consistently or over time getting the page to load is hit and miss.
The only thing that has been a workaround is using Live Mail client and clicking the 'sync' button then waiting a sec and refreshing the page. 9 out of 10 times the page loads. I have tried to just wait the same amount of time it takes me to switch to LM but still no load. I had thought it was a DNS problem but I have tried OpenDNS and my ISP DNS servers but get the same issue. The ISP says they do not see me loosing connection at all and have changed out my DSL modem. I have scanned over and over for malware/spyware and nothing. The ISP is the only one I can get or I would switch as asking them for help gets me nowhere.
System running Win 7 browsing with FireFox or IE makes no difference. Using a router for connection to network printer and occasional laptop although I have removed it during troubleshooting and same issue exists.
Any help would be appreciated and questions will be answered. Thank you in advance.
It sounds like a Windows 7 problem, we need to be clear whether we are losing connection or if it is a loading fault, if you were losing connection would it not be 'flagged' on the task bar?
There have been one or two issues with Firefox and Windows 7 but your problem may not be related, the only problem I am aware of was Firefox Skype add-on this doesn't explain your IE problem.
I assume you have scanned for malware and ran your anti-virus... how about emptying your cache, temp and history files and defragging the disc, degragging would effect all programs not just on line activity.
Have a look here at the Windows 7 forum, there might be something there to help you resolve the problem.
Thank you Davy for taking the time to answer my post. I do not believe it is a Windows 7 problem for 2 reasons. 1) I used Vista Pro x64 for several months with this problem that is one reason I upgraded to Win 7 to see if that would fix it. 2) The icon in the status bar continues to show 'Network Internet Access'. The messengers seem to stay connected as well and only the checking of mail seems to re-establish the connection.
I do not use Skype or anything similar. I have scanned over and over with many different online and application scanners. Nothing came up. I do defrag on a regular basis even though MS says you do not need to on NTFS volumes. I also use utilities like CCleaner to clean out the cache. Any other ideas would be appreciated.
So the issue is slowness when browsing the internet?
What kind of pingtime do you get to your router from your PC?
From your PC to the default gateway* listed in your network settings?
From your PC to high-profile websites like msn, google, and yahoo?
Are you using IPv4 or IPv6 in Win7?
*- Not sure about Win7, but this can be easily gotten in XP: Start-->Run-->cmd-->ipconfig /all
Not slowness it is a loss of connection. While trying to get the ISP to assist me in troubleshooting I would ping servers like yahoo, msn and google as well as the direct IP address of my ISP DNS server/default gateway. The ping would be a continus ping and at the time of loss of connection the ping would show 100% packet loss whereas when I was getting pages to load I would get 100% packet success. This would happen with the ISP on the phone and they said that while looking at my connection from their side they did not see me loose connection at all. I thought it might be a DNS problem so I tried using OpenDNS but still received the same errors. When I run the ping to the router I never get lost packets and when printing to the network printer or sharing files with the laptop never have problems. Yes IPv4 and IPv6 are enabled. In troubleshooting, IPv6 was disabled to see if that was the problem but did not make any differences.
Thank you for your help and if you have any other questions or suggestions please send them on as I would really like to get this fixed.
Do me a big favor and actually run the ping tests and give me some numbers.
This doesn't sound like an ISP or DNS issue to me. This sounds local.
Are you using the same router that you were using when this began?
What is the make and model?
Have you upgraded the firmware to the latest and greatest?
How long has this unit been in service?
Currently I am using a Linksys WRT160Nv2 originally was using a Belkin G router when the problem started so I deceided to move up to an N router although I know the wireless has nothing to do with it since I have no wireless devices hooked up (all wired) just thought upgrading the router would fix the problem and it did not. I also have removed the router in the troubleshooting process and the problem continued. Originally when I contacted the ISP they said it was the router so that is why I upgraded it. After doing that I called them back and they came out and replaced the modem saying it was an older model. The tech might as well have been a pizza delivery guy as he did not know what to do to check it and did witness the errors. The firmware is upto date on the router and mobo. The ISP says the modem firmware can't be updated at least not by me. As a note also I would love to get a new ISP but living in a small town in a state that does not have 911, as they say this is the reason, I can not use any other DSL provider. I am stuck with this one.
I will provide ping listing but need to research on which switches to use again as the tech at the ISP told me what to put and that was about 8 months ago. As soon as I can get that I will post it.
ping [hostname] will send 4 ping packets to the host.
ping -t [hostname] will ping the host until stopped. This kind of arrangement is good for when you are trying to show someone the problem. You let it go uintil the problem crops up.
Provide a single traceroute for me to one of the hosts, as well. tracert [hostname] will send a trace device by device until it reaches the host. This may show us where the problem lay.
Most tech support guys aren't worth the cardboard the pizza came in. In fact, I know a few
Sorry took so long for me to get back to you my mouse battery died. Here is the listing for the ping. I did each for about a minute except for the first one which was half minute.
C:\>ping -t www.google.com
Pinging google.navigation.opendns.com [208.69.36.230] with 32 bytes of data:
Reply from 208.69.36.230: bytes=32 time=58ms TTL=51
Reply from 208.69.36.230: bytes=32 time=60ms TTL=51
Reply from 208.69.36.230: bytes=32 time=62ms TTL=51
Reply from 208.69.36.230: bytes=32 time=60ms TTL=51
Reply from 208.69.36.230: bytes=32 time=60ms TTL=51
Reply from 208.69.36.230: bytes=32 time=63ms TTL=51
Ping statistics for 208.69.36.230:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 63ms, Average = 60ms
Control-C
Ping statistics for 65.55.17.26:
Packets: Sent = 10, Received = 0, Lost = 10 (100% loss),
Control-C
C:\>ping -t www.yahoo.com
Pinging www-real.wa1.b.yahoo.com [209.191.93.52] with 32 bytes of data:
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=62ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=62ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=62ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=61ms TTL=52
Reply from 209.191.93.52: bytes=32 time=60ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Reply from 209.191.93.52: bytes=32 time=57ms TTL=52
Reply from 209.191.93.52: bytes=32 time=59ms TTL=52
Reply from 209.191.93.52: bytes=32 time=58ms TTL=52
Ping statistics for 209.191.93.52:
Packets: Sent = 68, Received = 68, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 62ms, Average = 58ms
Control-C
Ping statistics for 207.126.123.20:
Packets: Sent = 12, Received = 0, Lost = 12 (100% loss),
Control-C
Here is the tracerout information:
C:>tracert www.google.com
Tracing route to www.l.google.com [209.85.225.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.10.1
2 7 ms 7 ms 7 ms ip-69-27-219-1.marktwain.net [69.27.219.1]
3 15 ms 14 ms 14 ms host-69-27-196-153.stjoseph.mo.npgco.com [69.27.196.153]
4 26 ms 25 ms 28 ms host-69-27-196-73.stjoseph.mo.npgco.com [69.27.196.73]
5 25 ms 25 ms 25 ms sl-st20-stl-1-1-3.sprintlink.net [144.228.25.17]
6 25 ms 25 ms 27 ms sl-crs2-chi-0-14-0-3.sprintlink.net [144.232.8.58]
7 32 ms 31 ms 35 ms sl-st21-chi-5-0-0.sprintlink.net [144.232.18.155]
8 26 ms 27 ms 25 ms sl-googl1-150497-0.sprintlink.net [144.223.241.54]
9 33 ms 31 ms 31 ms 209.85.254.120
10 43 ms 42 ms 42 ms 72.14.232.141
11 43 ms 41 ms 41 ms 209.85.241.29
12 43 ms 57 ms 44 ms 209.85.248.106
13 37 ms 36 ms 36 ms iy-in-f147.google.com [209.85.225.147]
Trace complete.
C:>tracert www.msn.com
Tracing route to us.port.msn.com.nsatc.net [65.55.17.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.10.1
2 7 ms 6 ms 7 ms ip-69-27-219-1.marktwain.net [69.27.219.1]
3 17 ms 15 ms 16 ms host-69-27-196-153.stjoseph.mo.npgco.com [69.27.196.153]
4 26 ms 25 ms 26 ms host-69-27-196-73.stjoseph.mo.npgco.com [69.27.196.73]
5 26 ms 24 ms 25 ms sl-st20-stl-1-1-3.sprintlink.net [144.228.25.17]
6 34 ms 33 ms 31 ms sl-crs1-kc-.sprintlink.net [144.232.8.56]
7 43 ms 42 ms 41 ms 144.232.20.56
8 48 ms 44 ms 44 ms sl-st20-dal-1-0-0.sprintlink.net [144.232.9.136]
9 51 ms 51 ms 66 ms sl-micro139-273287-0.sprintlink.net [144.223.244.166]
10 46 ms 45 ms 44 ms 207.46.47.132
11 52 ms 52 ms 52 ms ge-7-0-0-0.dal-64cb-1a.ntwk.msn.net [207.46.43.238]
12 82 ms 82 ms 81 ms ge-1-0-0-0.co2-64c-1a.ntwk.msn.net [207.46.43.190]
13 87 ms 86 ms 86 ms ge-2-0-0-0.co1-64c-1a.ntwk.msn.net [207.46.43.164]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 Control-C
C:>tracert www.yahoo.com
Tracing route to www-real.wa1.b.yahoo.com [209.191.93.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.10.1
2 7 ms 7 ms 7 ms ip-69-27-219-1.marktwain.net [69.27.219.1]
3 16 ms 14 ms 16 ms host-69-27-196-153.stjoseph.mo.npgco.com [69.27.196.153]
4 32 ms 32 ms 31 ms 67.221.223.9
5 122 ms 119 ms 129 ms 207.88.184.33.ptr.us.xo.net [207.88.184.33]
6 140 ms 136 ms 141 ms 207.88.84.213.ptr.us.xo.net [207.88.84.213]
7 188 ms 122 ms 118 ms 207.88.12.141.ptr.us.xo.net [207.88.12.141]
8 37 ms 38 ms 37 ms 207.88.13.5.ptr.us.xo.net [207.88.13.5]
9 51 ms 51 ms 51 ms 206.111.2.206.ptr.us.xo.net [206.111.2.206]
10 56 ms 56 ms 67 ms Vlan5.icore2.DTX-Dallas.as6453.net [206.82.141.30]
11 56 ms 56 ms 56 ms if-5-0-0-31.core2.DTX-Dallas.as6453.net [66.198.2.37]
12 52 ms 53 ms 52 ms ix-4-1.core2.DTX-Dallas.as6453.net [66.198.2.10]
13 54 ms 52 ms 63 ms ae2-p110.msr2.mud.yahoo.com [216.115.104.109]
14 48 ms 53 ms 56 ms te-8-1.fab1-a-gdc.mud.yahoo.com [209.191.78.133]
15 50 ms 53 ms 49 ms UNKNOWN-209-191-78-173.yahoo.com [209.191.78.173]
16 58 ms 59 ms 58 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Tracing route to www.about.akadns.net [207.126.123.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.10.1
2 8 ms 7 ms 7 ms ip-69-27-219-1.marktwain.net [69.27.219.1]
3 17 ms 15 ms 15 ms host-69-27-196-153.stjoseph.mo.npgco.com [69.27.196.153]
4 26 ms 25 ms 24 ms host-69-27-196-73.stjoseph.mo.npgco.com [69.27.196.73]
5 31 ms 32 ms 32 ms 65.255.143.193
6 65 ms 272 ms 234 ms gi1-8.mpd01.mci01.atlas.cogentco.com [38.112.3.9]
7 99 ms 42 ms 46 ms te4-8.mpd01.dfw01.atlas.cogentco.com [154.54.3.17]
8 36 ms 36 ms 37 ms te3-3.mpd01.dfw03.atlas.cogentco.com [154.54.6.94]
9 59 ms 45 ms 44 ms te8-1.ccr02.dfw03.atlas.cogentco.com [154.54.25.10]
10 * 36 ms 37 ms 38.104.204.74
11 102 ms 220 ms 209 ms border1.ge1-1-bbnet1.ext1a.dal.pnap.net [216.52.191.24]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 Control-C
Hope this helps. I see with the traceroute some problems or I think those would be problems. Let me know what you think. Thanks again.
Random connection loss 
Linear Mode
