Hello First of all I´m (still :roll: ) a computer noob so if this is a rather stupid post just ignore it pls I have the problem that my ping on the TF2 server sometimes goes up to 300 for about 5 mins or so before it´s back to my usual ping :? ... before you ask : I´m not running anything in the background.
Hey Marmie I got a ping issue atm too, but it's only at LZ3 the others are fine, but it's ( from what I'm told ) a routing problem at my ISP's side, so maybe you got a problem like mine but for a shorter time ?? Greatz Sniffi
Marm, try Eric's suggestion for the problem. start run type "cmd", enter type "tracert 82.94.255.222", enter and post the output of it here! then we can see where the problem is! p.s some small thing you can do is resetting you modem at home. just unplug you power and restart it again.. Mine is: C:\Documents and Settings\Frank>tracert 82.94.255.222 Bezig met het traceren van de route naar vandaag.net [82.94.255.222] via maximaal 30 hops: 1 <1 ms <1 ms 1 ms 192.168.1.1 2 20 ms 18 ms 23 ms 10.219.128.1 3 20 ms 13 ms 17 ms csw1-vlan201.dbsch1.nb.home.nl [213.51.152.193] 4 28 ms 16 ms 18 ms bb1-ge0-2-0-0.dbsch1.nb.home.nl [213.51.158.92] 5 22 ms 20 ms 23 ms bb2-ae0-0.amsix-telecity.home.nl [213.51.158.102] 6 25 ms 40 ms 38 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74] 7 31 ms 21 ms 16 ms vandaag.net [82.94.255.222] De trace is voltooid.
indeed.. what guus is saying. If there is a problem with the connection you see the FAT numbers really high 1 <1 ms <1 ms 1 ms 192.168.1.1 2 20 ms 18 ms 23 ms 10.219.128.1 3 20 ms 13 ms 17 ms csw1-vlan201.dbsch1.nb.home.nl [213.51.152.193] 4 28 ms 16 ms 18 ms bb1-ge0-2-0-0.dbsch1.nb.home.nl [213.51.158.92] 5 22 ms 20 ms 23 ms bb2-ae0-0.amsix-telecity.home.nl [213.51.158.102] 6 25 ms 40 ms 38 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74] 7 31 ms 21 ms 16 ms vandaag.net [82.94.255.222]
Ok, I got this: C:\Dokumente und Einstellungen\sabine>tracert 82.94.255.222 Routenverfolgung zu vandaag.net [82.94.255.222] über maximal 30 Abschnitte: 1 <1 ms <1 ms <1 ms Speedport_W_500 [192.168.2.1] 2 46 ms 47 ms 47 ms 217.0.118.158 3 58 ms 58 ms 53 ms 87.186.248.18 4 82 ms 86 ms 91 ms 217.239.37.233 5 304 ms 295 ms 292 ms 194.151.244.57 6 301 ms 320 ms 327 ms asd-sara-ipc-dr01.nl.kpn.net [195.190.227.246] 7 332 ms 332 ms 335 ms rt-dc2-ipc-br01.nl.kpn.net [195.190.233.33] 8 331 ms 331 ms 324 ms 195.190.233.96 9 317 ms 312 ms 308 ms asd-dc2-ias-ur10.nl.kpn.net [195.190.227.7] 10 312 ms 304 ms 306 ms 194.151.244.73 11 293 ms 293 ms 320 ms 0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58] 12 301 ms 300 ms 304 ms vandaag.net [82.94.255.222] Ablaufverfolgung beendet. :?
errr... did it again few minutes later and now it´s this: Routenverfolgung zu vandaag.net [82.94.255.222] über maximal 30 Abschnitte: 1 <1 ms <1 ms <1 ms Speedport_W_500 [192.168.2.1] 2 41 ms 43 ms 41 ms 217.0.118.158 3 42 ms 41 ms 42 ms 87.186.248.18 4 59 ms 59 ms 59 ms 217.239.37.233 5 59 ms 58 ms 59 ms 194.151.244.57 6 61 ms 61 ms 61 ms asd-sara-ipc-dr01.nl.kpn.net [195.190.227.246] 7 64 ms 63 ms 64 ms rt-dc2-ipc-br01.nl.kpn.net [195.190.233.33] 8 64 ms 63 ms 63 ms 195.190.233.96 9 61 ms 61 ms 60 ms asd-dc2-ias-ur10.nl.kpn.net [195.190.227.7] 10 62 ms 62 ms 63 ms 194.151.244.73 11 66 ms 63 ms 64 ms 0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58] 12 68 ms 61 ms 61 ms vandaag.net [82.94.255.222] :roll:
the second hop is already to high. This is most of you time your router. so first thing you need to do is reset your router/modem. Do the tracert again and i think its fine. Why do i think its fine.. because when i do a tracert to you the reaction time isnt that high Bezig met het traceren van de route naar 217.0.118.158 via maximaal 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 12 ms 8 ms 7 ms 195.190.249.124 3 9 ms 9 ms 9 ms iawxsrt-dc2-bb21-ge-3-1-0.302.wxs.nl [213.75.1.5 ] 4 9 ms 9 ms 9 ms nl-asd-dc2-ias-csg01.nl.kpn.net [213.75.1.146] 5 * * * Time-out bij opdracht. 6 * * * Time-out bij opdracht. 7 * * * Time-out bij opdracht. 8 * * * Time-out bij opdracht. 9 14 ms 13 ms 14 ms 194.151.244.58 10 28 ms 28 ms 28 ms ulm-ea2.ULM.DE.net.DTAG.DE [62.154.58.126] 11 28 ms 28 ms 28 ms 217.0.118.158 De trace is voltooid.
With a ping issue you just can check if your equipement are not in cause. If it isn't, you cannot do anything more unfortunetly. Sometimes, it's just temporarily. My ping is high on TF2 server too :/ C:\Documents and Settings\trajan>tracert 82.94.255.222 Détermination de l'itinéraire vers vandaag.net [82.94.255.222] avec un maximum de 30 sauts : 1 1 ms <1 ms <1 ms router [192.168.1.1] 2 40 ms 40 ms 40 ms AMontpellier-258-1-51-1.w90-48.abo.wanadoo.fr [90.48.186.1] 3 39 ms 44 ms 39 ms 10.125.44.78 4 40 ms 39 ms 40 ms 193.253.87.122 5 46 ms 60 ms 46 ms ge-4-2-0-0.nrlyo301.Lyon.francetelecom.net [193.252.101.154] 6 62 ms 54 ms 54 ms 81.253.131.77 7 53 ms 54 ms 54 ms pos0-9-1-0.pastr1.Paris.opentransit.net [193.251.128.118] 8 55 ms 56 ms 54 ms pos0-6-0-0.auvtr1.Aubervilliers.opentransit.net[193.251.242.149] 9 * 63 ms 63 ms tengige0-3-0-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.242.254] 10 63 ms 62 ms 62 ms ge-5-0-0-0.fftcr4.Frankfurt.opentransit.net [193.251.242.253] 11 69 ms 68 ms 69 ms so-0-0-0-0.amscr1.Amsterdam.opentransit.net [193.251.242.213] 12 136 ms 135 ms 135 ms 64.215.195.57 13 131 ms 130 ms 129 ms so1-0-0-2488M.ar1.AMS1.gblx.net [67.17.65.242] 14 129 ms 125 ms 127 ms XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.178] 15 127 ms 134 ms 126 ms 0.so-1-0-0.xr3.d12.xs4all.net [194.109.5.5] 16 130 ms 129 ms 129 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74] 17 131 ms 130 ms 129 ms vandaag.net [82.94.255.222] Itinéraire déterminé.
Trajan, you just get redirected to much, first over Germany to go to Holland. Marmot just gets pushed around inside Holland, so here ping is a bit lower... But still bounced around way 2 much buy KPN
But thx for the info, guys Maybe the breaks are good after all, cause i think i´m getting addicted