Mac Yosemite Extremely higher ping
I just updated my Mac Maverick to Yosemite and now I am having issues of extreme lag.
After Yosemite My ping in CS:GO (Counterstrike Global Offensive) Was around 14mms And now my ping is all the way to the 147-200 making it difficult to play.
And also when I tried to play Minecraft, my ping was off the charts around 1000+ on a server I always play on with minimal lag. And I also saw a noticeable slowness in loading youtube videos as where in Maverick it is extremely quick.
Can someone resolve or tell me why this is happening?
Thanks!
Some "usual suspects" include Bluetooth (if you don't need it right now, turn it off), and any Cloud-storage solutions such as Dropbox or similar (they seem to spend way too much time syncing again and again and again).
Similar Messages
-
Extremely High Ping time. Unusable internet for VOIP.
I am having extremely bad ping times due to which my VOIP phone service is literally unusable. My net meetings at home is having lost conversations and I am having real tough time working from home. Comcast service rep has visited my house twice and checked everything from my modem to comcast network end and everything seems to be fine.I have attached the ping times screenshot for my closest servers and both of which show unacceptable ping times.
Start by reviewing the troubleshooting tips at this sticky and post the requested information.
http://forums.xfinity.com/t5/Basic-Internet-Connectivity-And/Connection-Troubleshooting-Tips/m-p/1253575#U1253575 -
Hello, I'm new in Sky, I changed from my previous provided because for the last month or so I've been experiecing high pings while playing and slow browser navigation during peak hours. I just find out that probably this wasn't because the provider... so I probably made the wrong decission. The problem I've now is that I have even higher pings. To be honest, I've been just 1 day using Sky but since it's the same problem that I was previously having with my previous provider I assume it won't be magically fixed. The ping, in ms, is not as much as with my previous provider (before it went up to 700) but last longer, while before it was 5 seconds every 30, now seems to be 1 minute every 2, longer periods and more constant but pings of about 350-400 Below are some details in case this is not due to congestion (hopefully is not) and you could have other ideas (by the way, it happens with ethernet cable and wifi, the channel I have is also the most uncommon in the area) Broadband LinkDownstreamUpstreamConnection Speed20238 kbps1295 kbpsLine Attenuation22.0 dB14.0 dBNoise Margin6.1 dB9.9 dB Thank you, will keep informed on how this goes tomorrow
That's true the ping with the router was too high and that I did the test with wifi but I've the same problem with the cable, and also a few things to consider 1. The problem is only happening on peak hours (even if is with Wifi, it should then be the whole day)2. The router is new, received it last week3. The laptop was 1 meter from the router at the time of testing Considering all the above, I should still have a decent ping, as I do in the morning as I've always had with other providers.
Tracert right now, with Wifi, exact same setting and distance from router. Will do another one tomorrow with the ethernet cable at peak time and send it over C:\Users\ProvoS>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:
1 4 ms 1 ms 1 ms SkyRouter.Home [192.168.0.1]
2 22 ms 16 ms 15 ms sr15.syost.isp.sky.com [2.127.238.90]
3 18 ms 18 ms 18 ms ip-89-200-131-248.ov.easynet.net [89.200.131.248
4 18 ms 18 ms 17 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]
5 * * * Request timed out.
6 * * * Request timed out.
7 19 ms 17 ms 17 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
8 20 ms 16 ms 19 ms 132.185.255.149
9 16 ms 16 ms 17 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
Trace complete. -
Extremely high ping times only fixed via restart
I have 2 BR350 in bridge to a remote tower that has an AP350 providing access to customers. The customers will call in with complaints of very slow access. I have been onsite to see that a user can login to the AP350(web) fine but the BR350 at the tower is slow and the BR350 at the far tower is for most purposes dead. The link still shows up around 65% to 75% signal strength. By restarting either BR350 the link will come back fine. I have been using Ping Plotter to keep track of the ping times and see that the response times sometime slow grow or instantly grow to around 2000ms to 4000ms. Ping times from the customer to the AP350 on the tower remain below 10ms during all of this.
I have had a similar problem with an AP350 in another city thats ping time do the same thing and require a reboot. It's ping time from the client side can range form 4ms to 800ms on regular usage as well. This customer has an average of 80% signal strength from the Workgroup Bridge.
How can I find out what is causing that strange high ping time on these situations.
All units running firmware 12.00
Thanks for the help.
MVNormally ,the first thing to do is to check the software version used. Here,in your case you are using the latest software release(12.00T). So now the problem can be isolated to other issues. Bridge software provides tools to show you the types of problems and where the bridge is encountering the problems. Two of the most helpful tools are the Throughput statistics and the Error statistics screen.You can get the procedure for collecting the error statistics using the following URLs:
http://www.cisco.com/warp/public/102/wlan/br-ts-22950.shtml#conn
http://www.cisco.com/warp/public/102/wlan/errors.html -
Extremely high ping on lan, when aother wireless user uploads video
When a user on wireless does anything intensive such as uploading a video, me on lan experiences ping of over 1000 on game servers, and voice servers. I also expericence slow web page loading. This has been happening for a while now, and i want to to stop. I found disabling the wieless connection on the router stops the high ping for users on lan. Some infomation Manufacturer SkyModel SR102Firmware Version 2.1r.3761.RDSL Firmware VersionA2pv6F038m.d24jSystem Up Time: 361:42:01Broadband LinkDownstreamUpstreamConnection Speed18736 kbps2408 kbpsLine Attenuation29.5 dB0.0 dBNoise Margin6.9 dB6.6 dB
Hello, i too have random freeze without any "usable" info.
The blame "may" (well i think it is) be a "baytay + i915 kernel drivers" fault, these thread are intresting :
- https://bugs.freedesktop.org/show_bug.cgi?id=88012
- https://github.com/OpenELEC/OpenELEC.tv/issues/3726
what intresting is that there is path (for use of "legacy-turbo"), sory not remenber where i get it
-- gpu-drm-i915-fix-vlv-crash.txt --
Revert back to legacy turbo for vlv, fixes random crashes.
Reported by Timothée Giet <[email protected]> on dev@ ml.
https://bugs.freedesktop.org/show_bug.cgi?id=88012#c33
--- linux/drivers/gpu/drm/i915/i915_irq.c.orig
+++ linux/drivers/gpu/drm/i915/i915_irq.c
@@ -4361,12 +4361,7 @@ void intel_irq_init(struct drm_i915_priv
INIT_WORK(&dev_priv->rps.work, gen6_pm_rps_work);
INIT_WORK(&dev_priv->l3_parity.error_work, ivybridge_parity_work);
- /* Let's track the enabled rps events */
- if (IS_VALLEYVIEW(dev_priv) && !IS_CHERRYVIEW(dev_priv))
- /* WaGsvRC0ResidencyMethod:vlv */
- dev_priv->pm_rps_events = GEN6_PM_RP_UP_EI_EXPIRED;
- else
- dev_priv->pm_rps_events = GEN6_PM_RPS_EVENTS;
+ dev_priv->pm_rps_events = GEN6_PM_RPS_EVENTS;
setup_timer(&dev_priv->gpu_error.hangcheck_timer,
i915_hangcheck_elapsed,
I did use the trik on a custom kernel, i do have freeze (none tomoroy but two today but only on using firefox, so may be another probleme (sna)) but not on video (well i had run 15 video same time, and two where running 2 hours after without crash). May be you should try it (i think it work better).
note : link to make custom kernel -> https://wiki.archlinux.org/index.php/Ke … raditional -
Extremely high ping times ( 3000ms) and unusable ...
Hi all,
I am currently at my girlfriends house, trying to do some work but am experiencing absolutely dreadful internet connectivity.
I have just setup a small *nix box plugged directly into the HH4's gigabit ethernet port purely to monitor this abysmal connectivity. Due to the super high latency and low bandwidth for upload / downloads our internet is virtually unusable.
Here are a couple of excerpts from this mornings logged data.
Firstly latency of 4129.204 ms!!!
23/06/15 : 09:09
./speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from BT (86.165.237.95)...
Selecting best server based on latency...
Hosted by Spectrum Internet (Cardiff) [90.75 km]: 4129.204 ms
Testing download speed........................................
Download: 0.10 Mbit/s
Testing upload speed..................................................
Upload: 0.10 Mbit/s
Secondly ping test to bbc.co.uk again showing very high and varied latency. Avg 1629.844ms high 2361.604ms
PING bbc.co.uk (212.58.244.18) 56(84) bytes of data.
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=1 ttl=50 time=653 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=2 ttl=50 time=730 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=3 ttl=50 time=1188 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=4 ttl=50 time=1529 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=5 ttl=50 time=1464 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=6 ttl=50 time=600 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=7 ttl=50 time=153 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=8 ttl=50 time=491 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=9 ttl=50 time=148 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=10 ttl=50 time=870 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=11 ttl=50 time=1163 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=12 ttl=50 time=1202 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=13 ttl=50 time=1192 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=14 ttl=50 time=1209 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=15 ttl=50 time=1193 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=16 ttl=50 time=644 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=17 ttl=50 time=139 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=18 ttl=50 time=96.6 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=19 ttl=50 time=158 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=20 ttl=50 time=510 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=21 ttl=50 time=653 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=22 ttl=50 time=613 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=23 ttl=50 time=827 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=24 ttl=50 time=829 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=25 ttl=50 time=922 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=26 ttl=50 time=124 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=27 ttl=50 time=94.0 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=28 ttl=50 time=90.9 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=29 ttl=50 time=419 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=30 ttl=50 time=364 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=31 ttl=50 time=358 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=32 ttl=50 time=361 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=33 ttl=50 time=402 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=34 ttl=50 time=382 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=35 ttl=50 time=427 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=36 ttl=50 time=409 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=37 ttl=50 time=443 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=38 ttl=50 time=566 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=39 ttl=50 time=651 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=40 ttl=50 time=580 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=41 ttl=50 time=205 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=42 ttl=50 time=361 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=43 ttl=50 time=372 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=44 ttl=50 time=386 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=45 ttl=50 time=360 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=46 ttl=50 time=381 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=47 ttl=50 time=419 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=48 ttl=50 time=430 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=49 ttl=50 time=408 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=50 ttl=50 time=409 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=51 ttl=50 time=492 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=52 ttl=50 time=709 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=53 ttl=50 time=817 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=54 ttl=50 time=1073 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=55 ttl=50 time=1373 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=56 ttl=50 time=1197 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=57 ttl=50 time=1406 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=58 ttl=50 time=1565 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=59 ttl=50 time=1714 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=60 ttl=50 time=1835 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=61 ttl=50 time=2018 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=62 ttl=50 time=2151 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=63 ttl=50 time=2237 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=64 ttl=50 time=2277 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=65 ttl=50 time=2295 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=66 ttl=50 time=2300 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=67 ttl=50 time=2311 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=68 ttl=50 time=2329 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=69 ttl=50 time=2352 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=70 ttl=50 time=2323 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=71 ttl=50 time=2269 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=72 ttl=50 time=2236 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=73 ttl=50 time=2257 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=74 ttl=50 time=2224 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=75 ttl=50 time=2250 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=76 ttl=50 time=2242 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=77 ttl=50 time=2247 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=78 ttl=50 time=2258 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=79 ttl=50 time=2237 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=80 ttl=50 time=2251 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=81 ttl=50 time=2341 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=82 ttl=50 time=2330 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=83 ttl=50 time=2257 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=84 ttl=50 time=2319 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=85 ttl=50 time=2277 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=86 ttl=50 time=2278 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=87 ttl=50 time=2361 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=88 ttl=50 time=2341 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=89 ttl=50 time=2306 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=90 ttl=50 time=2358 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=91 ttl=50 time=2328 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=92 ttl=50 time=2252 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=93 ttl=50 time=2277 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=94 ttl=50 time=2248 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=95 ttl=50 time=2302 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=96 ttl=50 time=2322 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=97 ttl=50 time=2281 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=98 ttl=50 time=2269 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=99 ttl=50 time=2295 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=100 ttl=50 time=2277 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=101 ttl=50 time=2244 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=102 ttl=50 time=2256 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=103 ttl=50 time=2253 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=104 ttl=50 time=2244 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=105 ttl=50 time=2252 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=106 ttl=50 time=2291 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=107 ttl=50 time=2245 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=108 ttl=50 time=2309 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=109 ttl=50 time=2299 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=110 ttl=50 time=2313 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=111 ttl=50 time=2300 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=112 ttl=50 time=2286 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=113 ttl=50 time=2254 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=114 ttl=50 time=2242 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=115 ttl=50 time=2242 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=116 ttl=50 time=2246 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=117 ttl=50 time=2261 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=118 ttl=50 time=2251 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=119 ttl=50 time=2253 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=120 ttl=50 time=2219 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=121 ttl=50 time=2210 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=122 ttl=50 time=2261 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=123 ttl=50 time=2261 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=124 ttl=50 time=2228 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=125 ttl=50 time=2274 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=126 ttl=50 time=2265 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=127 ttl=50 time=2255 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=128 ttl=50 time=2269 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=129 ttl=50 time=2248 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=130 ttl=50 time=2274 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=131 ttl=50 time=2282 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=132 ttl=50 time=2283 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=133 ttl=50 time=2250 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=134 ttl=50 time=2270 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=135 ttl=50 time=2273 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=136 ttl=50 time=2192 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=137 ttl=50 time=2304 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=138 ttl=50 time=2296 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=139 ttl=50 time=2284 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=140 ttl=50 time=2270 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=141 ttl=50 time=2272 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=142 ttl=50 time=2263 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=143 ttl=50 time=2305 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=144 ttl=50 time=2283 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=145 ttl=50 time=2250 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=146 ttl=50 time=2266 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=147 ttl=50 time=2269 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=148 ttl=50 time=2247 ms
64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=149 ttl=50 time=2267 ms
^C
--- bbc.co.uk ping statistics ---
151 packets transmitted, 149 received, 1% packet loss, time 150279ms
rtt min/avg/max/mdev = 90.912/1629.844/2361.604/830.792 ms, pipe 3Anyone able to advise what to do about this problem?
-
Very Slow Internet + High Ping
I am on a Sager laptop running Windows 7 and using an Airport Extreme Base Station as my router. I don't know how the router is set up or even how to access the router from my computer. My roommate set up the internet before I moved in. I have already contacted my internet provider and they believe my slow service + extremely high pings when I try to play any online game are a result of my router.
I am just looking for a way to correct my issue. I would also like to know how I can even access my router from my computer. Thanks.+Is there any way for the owner of the device to limit the amount of bandwidth I am receiving??+
No.
+but I really don't understand why my internet is so crummy.+
Interference from other wireless networks or cordless phones is usually the cause of issues like this. If you have a cordless phone there, turn it off for an hour or so to see if things improve. Unfortunately, there's not much you can do about a neighbor's cordless phone causing problems or another wireless network.
+If I could access the utility what would you suggest I check?+
You can access AirPort Utility by going to the Downloads link on the main forum page. But, you won't be able to access any of the settings on the AirPort Extreme unless you have the device password, which is different than the wireless password. The first thing to do is try different channel settings for the wireless to see if you can find some clear airspace. -
getting random extremely high pings from my pc to my router. i have updated drivers for nic and firmware for router. running windows 7 x64 enterprise edition. its not constant but happens frequently. i have tried disabling tcp autotuning in windows 7. When i boot from windows vista on the same computer it works perfectly fine. is this router not compatable with Windows 7? or is there just some setting i am missing that i need to adjust?
Have you checked on different computer...?
As you upgraded the router's firmware,reset the router for 35 seconds,power cycle the router and re-configure it from scratch. -
My MacBook (late 2009 Mac OS X Lion 10.7.5 (11G63) often runs VERY slow...beach ball of death frequently. My page ins (3.29GB), page outs (5.64BG), and swap files (10GB) seem extremely high in comparison to most other discussions in here. I don't know how to copy the pie chart so it shows on here but here's what it says right now:
Free - 176 MB
Wired - 592MB
Active - 843MB
Inactive - 432MB
Used - 1.82 GB
VM size - 198GB
The page ins and page outs have 0 bytes/sec in the parenthesis even though the numbers are so high.
Any help anyone could provide would be greatly appreciated!!!You difinately need more ram. 2gb is the bare minimum to run just the Lion OS, anything extra will slow your Mac to a crawl. Upgrade to 8gb from either Crucial http://www.crucial.com/ or OWC http://eshop.macsales.com/
And you will be a happy camper! -
Hi,
Over the past month or so, ive noticed im getting a ping of over 200 on Valve servers on Team Fortess 2. For the past 2 weeks, it seemed to had settled down a little to about 70 ping, which i can play on but now its back to 200+. After starting a steam forum thread about this, i soo realised that everyone that has the problem is on BT infinity. One guy added me and we discussed what we was on and what problems we were getting and they were identical. BT Homehub 4, high ping only on Valve servers
Ive reset my connection in a million different ways suggested by different people and none of that did anything. From a few searches, some people fixed the issue by getting mods to change their latency type from Interleaved to Fast, but i dont know what im on so i cant tell if thats the issue.
I dont know what im meant to post but this is all the specs under "Helpdesk":
1. Product name:
BT Home Hub
2. Serial number:
+068341+NQ31327903
3. Firmware version:
Software version 4.7.5.1.83.8.130.1.17 (Type A) Last updated 10/05/14
4. Board version:
BT Hub 4A
5. WAN:
PPP Connected
6. Data sent/received:
136.1 MB / 415.5 MB
7. Broadband username:
[email protected]
8. BT FON:
Yes
9. 2.4 GHz Wireless network/SSID:
BTHub4-XS3P
10. 2.4 GHz Wireless connections:
Enabled (802.11 b/g/n (Recommended)) 20 MHz, WPS enabled
11. 2.4 GHz Wireless security:
WPA and WPA2
12. 2.4 GHz Wireless channel:
Automatic / 11
13. 5 GHz Wireless network/SSID:
BTHub4-XS3P
14. 5 GHz Wireless connections:
Enabled (802.11 n 40 MHz (Recommended)) 20/40 MHz, WPS enabled
15. 5 GHz Wireless security:
WPA2
16. 5 GHz Wireless channel:
Automatic / 40
17. Firewall:
Default
18. MAC Address:
2c:39:96:6b:7d:56
19. Software variant:
20. Boot loader:
BT Home Hub 4 (Type A) | Software version 4.7.5.1.83.8.130.1.17 | Last updated 10/05/14
Any help?Just got off the phone with someone from BT trying to convince me its an issue either my end or Valve's end (Even though it happens on non valve games also). Valve have told me its my ISP, which i am 100% certain it is, and she is just telling me to reset my router just once more.
Hope the forum can save me here -
Airport Extreme Slow Ping (Internet) Response
I am having problems with my dual-band airport extreme. When connecting to the external internet, I'm seeing high ping responses (>500ms) after about 5-10 minutes of resetting (hard reset) the Extreme and initially seeing 15-30ms response times.
I've tried:
1. Moving the router physcially in the house (no improvement)
2. Trying different channels on both 2.5 and 5 (some, but inconsistent improvement)
3. Multiple hard resets and reconfiguring the Extreme
4. Reinstall the firmware (haven't tried going down in firmware)
5. There are no cordless phones in the house
6. Absolute speed to the internet is strong (above my provider's stated speed)
7. If I connect my Macbook pro directly to the cable router, everything (ping + speed) is great.
8. Seeing slow ping responses both on my MacBook Pro and a separate PC
Any suggestions on how to troubleshoot? Seems like it a problem with the wireless connection and/or interference.
thanks!
Dalehad a 5th gen Extreme that I bought with 7.5 and immediately upgraded to 7.6. Saw the exact issue you described. exchanged it for a 6th gen Extreme, and am experiencing the same behavior again... both with 7.5.2 and 7.6 firmware.
everything is hunky dory when plugged directly into my cable modem.
third time's a charm, hopefully. -
Yosemite extremely slow. Cannot stop pop up windows
Yosemite extremely slow. Cannot stop pop up windows on any browsers. Considering going back to Maverick My iMack is mid 2011 21.5. I cannot find a solution to this problem
Helpful Links Regarding Malware Problems
If you are having an immediate problem with ads popping up see The Safe Mac » Adware Removal Guide and AdwareMedic.
Open Safari, select Preferences from the Safari menu. Click on Extensions icon in the toolbar. Disable all Extensions. If this stops your problem, then re-enable them one by one until the problem returns. Now remove that extension as it is causing the problem.
The following comes from user stevejobsfan0123. I have made minor changes to adapt to this presentation.
Fix Some Browser Pop-ups That Take Over Safari.
Common pop-ups include a message saying the government has seized your computer and you must pay to have it released (often called "Moneypak"), or a phony message saying that your computer has been infected, and you need to call a tech support number (sometimes claiming to be Apple) to get it resolved. First, understand that these pop-ups are not caused by a virus and your computer has not been affected. This "hijack" is limited to your web browser. Also understand that these messages are scams, so do not pay any money, call the listed number, or provide any personal information. This article will outline the solution to dismiss the pop-up.
Quit Safari
Usually, these pop-ups will not go away by either clicking "OK" or "Cancel." Furthermore, several menus in the menu bar may become disabled and show in gray, including the option to quit Safari. You will likely have to force quit Safari. To do this, press Command + option + esc, select Safari, and press Force Quit.
Relaunch Safari
If you relaunch Safari, the page will reopen. To prevent this from happening, hold down the 'Shift' key while opening Safari. This will prevent windows from the last time Safari was running from reopening.
This will not work in all cases. The shift key must be held at the right time, and in some cases, even if done correctly, the window reappears. In these circumstances, after force quitting Safari, turn off Wi-Fi or disconnect Ethernet, depending on how you connect to the Internet. Then relaunch Safari normally. It will try to reload the malicious webpage, but without a connection, it won't be able to. Navigate away from that page by entering a different URL, i.e. www.apple.com, and trying to load it. Now you can reconnect to the Internet, and the page you entered will appear rather than the malicious one.
An excellent link to read is Tom Reed's Mac Malware Guide.
Also, visit The XLab FAQs and read Detecting and avoiding malware and spyware.
See these Apple articles:
Mac OS X Snow Leopard and malware detection
OS X Lion- Protect your Mac from malware
OS X Mountain Lion- Protect your Mac from malware
OS X Mavericks- Protect your Mac from malware
About file quarantine in OS X
If you require anti-virus protection Thomas Reed recommends using ClamXAV. (Thank you to Thomas Reed for this recommendation.)
These may be helpful in improving Yosemite's performance.
Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
4. Reinstall Yosemite: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
because it is three times faster than wireless.
5. Reinstall Yosemite from Scratch:
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
How to Clean Install OS X Yosemite
Note: You will need an active Internet connection. I suggest using Ethernet if possible
because it is three times faster than wireless. -
Adobe Creative Cloud (Desktop) does not work properly. The application is blocked : it could not be launch neither stopped. I'm on MAC Yosemite OS, does anyone know how to remove it properly or to force its stop. It does not appear in the launched applications.
I received no error message. The application was just trying to find applications unsuccessfully.
I am using MAC OS 10.10.1
I tried to uninstall the application but it seems that a kind of deamon is still installed thus providing me to reinstall properly. Do you know where are the elements to remove in order to get my machine just like before ?
Otherwise I would have to reinstall everything and this would be a pain.
Thanks for your help. -
my windows(8.1 64bit) partition is read only from the mac(yosemite) side of things. Anybody have a clue on how to fix this? Also, slightly frustrating as well, windows crashes every time I attempt to open a file from the mac partition.
All Office applications will also try to open a temporary work file in the same location as the source file. This implies the source file directory also needs to be writable for this temporary file. Since the default HFS+ driver provides only read-only access, such temporary files will fail to open, and will cause the application to fail.
As a test copy the file you want to edit, say an Excel spreadsheet from the OSX file system to the C: drive on the Windows side and try to open it. If you look in this directory, you should see two files, the source and a temporary file. You may have to force the temporary file to be opened on a read-write file system, by manipulating the folder for temporary files. -
Extremely high memory usage on ideapad u310
Hi all,
I've got a problem with my ideapad u310 touch running windows 8.1. When doing completely nothing (just staring at the desktop with no programs running) my laptop uses ~55% of ram. I find this extremely high, when i open a few chrome tabs and listen to some music, maybe open a powerpoint it even rises to 80+%. My Medion erazer laptop(also running 8.1) with 4GB ram uses ~65% with the same usage and ~35% while doing nothing. I deleted almost every lenovo programm except energy management and OneKey recovery and i disabled as much programs as possible on startup but there's almost no difference.
Now, I don't really care about the high percentages but what I do care about is that it gets extremely slow when 80% of the ram is in use. Does anybody know what i can do about this? I already tried the refresh windows option but that didn't help. Or am I just stuck with a device that has very very very poor multitasking performance.hi spromper,
Welcome to Lenovo Community Forums!
Opening Task Manager will show you which application utilizes the RAM.
Also Doing a clean boot will help on freeing up RAM
http://support.microsoft.com/kb/929135
Hope this helps
Cheers!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!
Maybe you are looking for
-
Error while starting the Oracle BI Server
Hi , I am getting the services.msc error while starting the Oracle BI Server as - Error handling the control request. Please help me out .. Thanks and Regards ,
-
My husband and I are divorcing and we have used his apple ID for our 2 apple tv's. He changed his password and now I no longer have access to the 300 or more movies, tv shows and music. He keeps telling me that , there is no way for us both to hav
-
Bridge will not open after Mac OSX update
Hi, I updated to Mac OSX 10.9.5 yesterday, and now Bridge CC will not open. What should I do?
-
The thread dump has a deadlock ?
We're experiencing a problem with the OC4J server hanging when some we unknow operation . I can see it's a connection pooling problem based on a thread dump. What I can't determine is why it doesn't release a resource in the first place. I've include
-
I just got a Nikon D5000 but PSE 7.0 cannot load the RAW images. I saw that ACR 5.4 with D5000 support is now available but it does not have the install scripts for PSE 7. Has anyone been able to manually install the data files for the D5000?