someone help!
my ping is constantly 200 - 230 and must be the reason for me dropping nearly everytime i kill a builder!
it never used to be like this. i never ever dropped from games so i dont know what the problem is.
ive got the fastest possible internet speed package available from my provider and have had it for all the time ive been playing winbolo but its never been an issue before.
i dont know what could be causing it so if someone could shed some light and help me out id be very grateful.
thanks
kill some proesses, change your window frame rate, delete some cookies??
thats about all i got// restart your computer?
Do a scan for malware and spyware.
Make sure you dont have tons of files and programs on your desktop area (try to use shortcuts instead).
Also try restarting your router/cable modem if you have one (i.e turn completely off...and then on again).
Check you dont have a huge amount of downloads/torrenting etc.. going on.
Lastly you should search and find a free online broadband speed test, and tell us the results.
make sure no on else is using your internet connection when you are playing. If you have a home network with wireless access, someone else in your home or even a neighbor could be online at the same time you are. Since there is only ONE modem for all of you, anything they are doing is going to slow you down. In other words when u are playing bolo, everyone else has to get the hell off the internet.
Thanks for the replies guys im guna try all these things. :D
results of broadband speed test:
download:- 6800 kbps
upload:- 311 kbps
Gdit im pretty sure i should be getting 20 meg speed! wheres the phone! :evil:
that looks fine to me......u might want to do one that also reports the ping.
But yeah, if its significantly lower than what ure paying for, a phone call is in order.
But the connection is good....just need a ping number.
If the ping is also low (and therefore good), its most likely a spyware thing or a router that needs a restart....seeing how it has recently cropped up.
umm, a 200ms pingtime isn't very bad, that's not really laggy at all honestly. Lower than that would be 'better' but I doubt that's causing your dropping issues. For dropping to occur you need to start having alot of packet loss. Try pinging google.com or something from command prompt. type ping www.google.com -t from command prompt and see what kind of response you get. If it seems ok, try upping the packet size slightly with ping www.google.com -l 3000 -t or similiar it should take longer, what your looking for is packet loss. Not necessarily ping times.
Min
min im not really sure what u mean by this. i get the pinging from cmd promp but not sure what to do with the information :oops:
also when i ping google how do i know if 'its ok'?
these are good points by min,
in the results look at not only the ping time but whether any packets have been lost...it should be 0%
try adding the -t switch at the end for a continuous stream....and press ctrl c say after a minute or so.....
so do: ping www.google.com -t
(wait 2 minutes)
hit ctrl-c
....then report back if u lost any packets...also tell us ur ping average just so we know....
do the tests I said, each one for 5-10 minutes, then ctrl-c and copy/paste the summary into this thread.
Min
If you want to know your real-time connection speed, BT do that for free, its understandable seeing as they provide the phone line aswell. Its the connection manager icon that appears on the desktop when u install the software disk that comes with the hub.
You could have got this information by calling BT customer services, but unfortunately you would have shot yourself in the head after having to explain to them what the 'internet' is.
ping www.google.com -t
Ping statistics for 216.239.59.103:
Packets: Sent = 138, Received = 138, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 63ms, Average = 58ms
ping www.google.com -l 3000 -t
when trying to do this it keeps saying 'request timed out'
Well, thats your problem then.
ping google.com -l 3000 -t
Ping statistics for 208.69.34.230:
Packets: Sent = 150, Received = 150, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 233ms, Average = 200ms
Control-C
Is what I get. You got 100 percent loss apparently.
3000 is 3000 bytes, 3 kilobytes. Apparently you can't send a 3 kilobyte packet to google without it timing out. No wonder your dropping from games. Find the source and fix it. Could be your internet provider, could be your computer. Could be your network hardware. Isolate and determine which it is.
Min
how will i be able to find out what it is?
i pinged winbolo.net in the same way as i did google and got 0% packet loss. do you think the problem could be with the google server in my area? would that be the reason for the packet loss?
i get 0% loss from upto: ping www.google.co.uk -l 1472 -t
anything over that amount of packets times out??
No, its not the google server in your area, based on your findings I'd say its your connection or computer. As I suggested before your going to have to isolate whats going on. I'm not going to be able to handhold you through the whole process unfortunately, I don't have the patience to do that anymore. What you need to do is if you have a router, bypass it, see if it does the same thing, if you have a different computer (laptop for example) try that, see if the same thing occurs (winbolo dropping) if it does, go to the next thing. Step by step elimination of possible causes is the only way you can figure out whats going on. It could be a problem with your internet provider, your modem could be cooked, it could be your computer (malware, viruses) it could be your router, it could be your Ethernet cable, etc. Your going to have to do the legwork on this one. Systematically eliminate possible causes and go from there.
Min
Last edited: Apr 13, 2010 06:21 (edited 1 time)
didnt rid's post say he has 0% loss? Im on the same ISP as him, these things just happen and go away, BT has a less than impressive reputation, partially due to it being the only option in some areas. Ive had crap connection for days on end with them, its just something that will pass if i understand your problem
I have had similar problems and tested my ping. I can send a 1464 packet size 100% of the time and never send a 1465 sized packet. This sounds like it is set somewhere. Computer, wifi card, wireless router / modem, ISP.
Min, why does a client need to send a 3000 packet for bolo?
The other think to consider is location. Could the distance between the server and client location make any difference?
Check this (http://www.dslreports.com/tweaks/MTU), I am wondering about the 3000 packet size.
(TCP, IP, MTU and MSS magic numbers)
1500 The biggest sized IP packet that can normally traverse the internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492 The maximum MTU recommended for internet PPPoE implementations
1472 The maximum ping data payload before fragmentation errors are received on non-PPPoE non VPN connections
1460 TCP Data size (MSS) when MTU is 1500 and not using PPPoE
1464 The maximum ping data payload before fragmentation errors are received when using a PPPoE connected machine
1452 TCP Data size (MSS) when MTU is 1492 and using PPPoE
576 Typically recommended as the MTU for dialup type applications .. leaving 536 bytes of TCP data.
48 The sum of IP, TCP, and PPPoE headers
40 The sum of IP, and TCP headers
28 The sum of IP, ICMP headers
Sigh, ok first, this was simply the first step it trying to narrow down whats going on with his setup. He has dsl, he's restricted to 1472 as the largest packet he can send without fragmenting. No winbolo doesn't require 3kilobyte packets.
If your having 'similiar' problems, post your own thread with the symptoms.
Min
