3 computers on same MiFi, one suddenly slower?

[BoulderRidge]

I rely on Verizon MiFi wireless for my home internet. I am routinely online with two laptops (one XP and one Vista) and one desktop running Windows 7. Just this week, the Win7 desktop slowed to half its normal speed. The two laptops are still running their usual speed. The desktop has always had ESET virus protector fully up to date.

Where do I look to “fix” my desktop? I’m a programmer but not very good with hardware/networking so I could be missing something simple here.
Thanks,


-- BoulderRidge B-)

 

[BoulderRidge]

Ok, I found a thread saying to run Ping 8.8.8.8 on different machines to compare results and I'm posting those here. Unfortunately the thread did not get results like mine and I have no idea how to interpret these...but I'm sure it makes sense to someone out there
Non-internet programs appear to run at normal speed on the desktop, so the issue seems to be isolated to the internet connection.
Note: These tests were all run within a 5 minute window, and the laptop was sitting on the desk 2 feet from the desktop.

[b]Windows 7 Desktop (slow machine):[/b]
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

1.	C:\Users\Calvin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=137ms TTL=52
Reply from 8.8.8.8: bytes=32 time=157ms TTL=52
Reply from 8.8.8.8: bytes=32 time=146ms TTL=52

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 157ms, Average = 146ms

2.	C:\Users\Calvin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=129ms TTL=52
Reply from 8.8.8.8: bytes=32 time=159ms TTL=52
Reply from 8.8.8.8: bytes=32 time=149ms TTL=52
Reply from 8.8.8.8: bytes=32 time=149ms TTL=52

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

3.	C:\Users\Calvin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=558ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=210ms TTL=52
Reply from 8.8.8.8: bytes=32 time=134ms TTL=52

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 134ms, Maximum = 558ms, Average = 300ms

4.	C:\Users\Calvin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

5.	C:\Users\Calvin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=603ms TTL=52
Reply from 8.8.8.8: bytes=32 time=158ms TTL=52
Reply from 8.8.8.8: bytes=32 time=170ms TTL=52

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 158ms, Maximum = 603ms, Average = 310ms

[b]Windows Vista laptop (normal faster speed)[/b]
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

1.	C:\Users\sayler>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=399ms TTL=52
Reply from 8.8.8.8: bytes=32 time=104ms TTL=52
Reply from 8.8.8.8: bytes=32 time=94ms TTL=52
Reply from 8.8.8.8: bytes=32 time=100ms TTL=52

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

2.	C:\Users\sayler>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=101ms TTL=52
Reply from 8.8.8.8: bytes=32 time=99ms TTL=52
Reply from 8.8.8.8: bytes=32 time=99ms TTL=52
Reply from 8.8.8.8: bytes=32 time=119ms TTL=52

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

3.	C:\Users\sayler>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=101ms TTL=52
Reply from 8.8.8.8: bytes=32 time=100ms TTL=52
Reply from 8.8.8.8: bytes=32 time=147ms TTL=52
Reply from 8.8.8.8: bytes=32 time=105ms TTL=52

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

4.	C:\Users\sayler>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=106ms TTL=52
Reply from 8.8.8.8: bytes=32 time=213ms TTL=52
Reply from 8.8.8.8: bytes=32 time=106ms TTL=52
Reply from 8.8.8.8: bytes=32 time=104ms TTL=52

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

5.	C:\Users\sayler>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=102ms TTL=52
Reply from 8.8.8.8: bytes=32 time=97ms TTL=52
Reply from 8.8.8.8: bytes=32 time=105ms TTL=52
Reply from 8.8.8.8: bytes=32 time=103ms TTL=52

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

-- BoulderRidge B-)

 

[linney]

Can you connect via Safe Mode With Networking, and if so, browse any faster?

Advanced startup options (including safe mode)

http://windows.microsoft.com/en-US/windows7/Advanced-startup-options-including-safe-mode

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

http://support.microsoft.com/default.aspx/kb/929135

Have you tried cleaning out your Temporary Internet Files, Cookies, etc.? Perhaps running the Disk Cleanup tool too.

You could use System Restore if you want to go back in time and test things out.

How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista (or 7)

http://support.microsoft.com/kb/936212/#appliesto

Have you tried testing with another Windows user?

The Ping data doesn't mean much to me so I can't comment on that.

 

[vacunita]

Seems you are having connectivity issues. The Pings are somehow getting lost in transit. This means intermittent connectivity between you and the 8.8.8.8 servers. (Google's DNS servers).

How is the desktop connecting to the MiFi router? Wired? Or Wireless? If wired, have you tried replacing the cable?

If wireless, can you try a different Wireless card?

You can also try some tracert tests, to see where its getting lost.

tracert 8.8.8.8





----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Web & Tech

 

[BoulderRidge]

Hi linney and vacunita,

Thanks so much for the helpful comments. I will go thru the recommended cleanups since I think they are overdue anyways.

However, today the speed has doubled on the desktop (without me making changes). When I shut down last night, I got a blue system screen and it went thru "do not power down...installing update n of 12..." for several minutes and some extra steps booting up this morning. I suspect (rather sheepishly) that the slowness yesterday was caused by some massive windows updates invisibly downloading all day in the background. Does this fit with the symptoms?

Appreciate your help,

-- BoulderRidge B-)

 

[vacunita]

Possibly. Though Windows doesn't usually download things when you are working, to prevent this sort of thing. It downloads updates when the PC is idle... so as to not affect either the PC performance, or suck up bandwidth while its in use.

Other than that, maybe some interference form a cordless phone or some other device causing the intermittent issues.



----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Web & Tech

 

[linney]

If your machines are kept fully updated then I feel that the updates you are talking about were this months normal release by Microsoft, in which case there was nothing too enormous in the recent releases.

You can look at your Windows Updates settings and set them to not download anything but to just notify you when updates are available thereby allowing you to start the download (and installation) process manually.

 

[BoulderRidge]

Odd, I checked settings and downloads are scheduled to run daily at 3 am. If I have the machine shut down overnight, wouldn't they start as soon as I log in? The slowness was consistent all that day Wednesday.

We don't have any cordless phones active anymore; had hoped to run the old landline using VoIP on the MiFi but it sucked up so much data the cost was prohibitive.

The good news is the machine has been happily running at normal speeds all day...so I can hope it was a fluke that won't happen again...(until it does).

thanks,

-- BoulderRidge B-)

 

[ChrisHirst]

I've been seeing noticeable slowdowns when using Google's public DNS servers and so have a few people who I know and suggested using Google to them

Try switching to the OpenDNS servers on 208.67.222.222 and 208.67.220.220

Chris.

Indifference will be the downfall of mankind, but who cares?
Time flies like an arrow, however, fruit flies like a banana.
Webmaster Forum

 

[BoulderRidge]

Hi ChrisHirst,
I'll ask the dumb question: how/where would I go about 'switching to the OpenDNS servers'? Is this just when searching from Google or is it more universal than that?

thanks,


-- BoulderRidge B-)

 

[vacunita]

DNS's are the servers that translate the name addresses like

http://www.google.com

to their actual IP addresses. xxx.xxx.xxx.xxx

The setting change would need to happen in your connection settings on the network card.
Though I'm not entirely sure you are using google's DNS servers for anything other than the tests above. So the slowdown probably isn't due to them.

----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Web & Tech

 

[ChrisHirst]

You would change the nameserver IP in the TCP/IP settings of your metwork card.

Or you could add them to your router configuration



Chris.

Indifference will be the downfall of mankind, but who cares?
Time flies like an arrow, however, fruit flies like a banana.
Webmaster Forum