| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 79712 | 2007-05-29 11:00:00 | Slingshot ping problem | jmastaj (12340) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 554213 | 2007-05-29 11:00:00 | hi im having a problem with my slingshot MAX/128 25GB connection. my pings to Australian servers have suddenly gone crap today for some reason. theyre usually 90-110 but today they are up at 400-500 and i cant join any Aus servers in BF2 and Call of Duty. It also says in the server lobby in BF2 and Call of Duty that the NZ pings are at 200 but when i join, the pings are 40-60. Does anyone know why my Aus pings are so high? also why are my pings so high in the server lobby but not actually in the game? Can anyone help? thanks, Josh |
jmastaj (12340) | ||
| 554214 | 2007-05-29 11:28:00 | Welcome to PF1 :) Tried restarting the modem? I cant think of anything else that you yourself can do... In cmd (start > run "cmd") type: ping www.stuff.co.nz > c:\stuff-ping.txt Then enter. Repeat that, and check sites like www.google.com, www.slingshot.co.nz etc. Each time, change "stuff-ping" to whatever name you want. The txt files will be saved on the C drive. Copy some of that data for us to see. Cheers |
jermsie (6820) | ||
| 554215 | 2007-05-30 06:44:00 | hi, thanks for the help, but the problem seems to have gone anyway . i can now join all servers :) wonder what the problem was i got these results, seems ok to me . . . Pinging www . slingshot . co . nz [202 . 180 . 68 . 145] with 32 bytes of data: Reply from 202 . 180 . 68 . 145: bytes=32 time=61ms TTL=250 Reply from 202 . 180 . 68 . 145: bytes=32 time=58ms TTL=250 Reply from 202 . 180 . 68 . 145: bytes=32 time=56ms TTL=250 Reply from 202 . 180 . 68 . 145: bytes=32 time=59ms TTL=250 Ping statistics for 202 . 180 . 68 . 145: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 61ms, Average = 58ms Pinging www . stuff . co . nz [202 . 135 . 111 . 130] with 32 bytes of data: Reply from 202 . 135 . 111 . 130: bytes=32 time=73ms TTL=58 Reply from 202 . 135 . 111 . 130: bytes=32 time=81ms TTL=58 Reply from 202 . 135 . 111 . 130: bytes=32 time=73ms TTL=58 Reply from 202 . 135 . 111 . 130: bytes=32 time=75ms TTL=58 Ping statistics for 202 . 135 . 111 . 130: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 73ms, Maximum = 81ms, Average = 75ms thanks, josh |
jmastaj (12340) | ||
| 554216 | 2007-05-30 06:55:00 | The time is the time for a remote site to respond. I'd guess that a game server would be set to respond to ping requests on a lower priority than game messages. The people playing the game would prefer that. ;) Some sites don't respond to ping requests at all. They have decided not to waste time doing that. There are people who abuse the ping command. The overall network time depends on the busyness of all the routers on the path, too. It would be sensible for network routers to also give a lower priority to passing ping requests through. The real traffic is much more important. |
Graham L (2) | ||
| 1 | |||||