Metal Guitarist Forums banner
1 - 20 of 22 Posts

·
NICE BLACKMACHINE YO
Joined
·
7,276 Posts
Discussion Starter · #1 ·
Bear in mind I'm not terribly knowledgeable about computer hardware:

Earlier tonight my internet connection seemed to be crawling. Google would take around 30 seconds to load - mg.org wasn't happening, same for facebook and the like. At the time I was streaming music on spotify, and it kept dropping out which is when I noticed. Bizarrely, it's working fine on here. (around 2.5Mb/s, which is standard for peak times like now).

Did the whole on/off thing which usually fixes the problem (it happens frequently) but no luck - in fact, it 'forgot' the router password, and upon re-entry it said it was wrong. (I know it wasn't). Decided to ping the router and I got these results:



Ran the first one for about two minutes but closed it by accident - although this one isn't as long, the numbers are almost exactly the same.

Any suggestions? I'm running 10.4.whateverthelatestversionis
 

·
Mutes the Meat
Joined
·
10,236 Posts
Holy fuck that is a slow response. Are you able to ping the router from a different computer?

Here is a ping result from my Ubuntu laptop to my router.

Code:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.89 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.11 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.10 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.90 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.20 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.34 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.24 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.17 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.13 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.11 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.12 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=6.67 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=11.3 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.89 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.11 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.17 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1.14 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.90 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=7.52 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=1.11 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=3.23 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=1.49 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.13 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=3.52 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=4.92 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=1.57 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=2.26 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=3.25 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=1.13 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=2.67 ms
^C
--- 192.168.1.1 ping statistics ---
33 packets transmitted, 33 received, 0% packet loss, time 32042ms
rtt min/avg/max/mdev = 1.106/2.495/11.313/2.234 ms
 

·
Mutes the Meat
Joined
·
10,236 Posts
:lol:

IPv4 running out won't affect his home network.
 

·
THUNDERBEEEEAR!
Joined
·
3,920 Posts
I know :D
but he said he had trouble connecting to the internetz.
it does sound like you could use a router upgrade though.
 

·
Mutes the Meat
Joined
·
10,236 Posts
IPvFFFFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
 

·
Mutes the Meat
Joined
·
10,236 Posts
Your Windows XP ping is a lot faster than your Mac ping...hmm.....ping on the Mac again?

Windows 7 ping doesn't show the time taken? That sucks.

Also :lol:mad:/Users/chris
 

·
NICE BLACKMACHINE YO
Joined
·
7,276 Posts
Discussion Starter · #12 ·
Your Windows XP ping is a lot faster than your Mac ping...hmm.....ping on the Mac again?

Windows 7 ping doesn't show the time taken? That sucks.

Also :lol:mad:/Users/chris
Yeah, I know it's a lot faster. I'm posting from my laptop, it's what i meant when I said "It's working a lot faster on here". All the other computers work fine - it's just my mac that has this problem.
 

·
Mutes the Meat
Joined
·
10,236 Posts
Probably not the router then.....hmm....

Have you tried the ol' DHCP release/renew? Is there perhaps some cache that can be cleared?

I've never had to troubleshoot this particular problem, so I'm just throwing shit out there :lol:
 

·
Mr. Negative Pants, ,
Joined
·
14,796 Posts
Wirelessly posted :)darren:phone: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5)

Check your DNS settings. Having the wrong ones for your network can really slow things down.
 

·
MG.ORG Irregular
Joined
·
9,747 Posts
another thing it could be is a bad NIC, it says 48% packet loss at the bottom which is indicative of this
 
1 - 20 of 22 Posts
Top