Natter Posted November 15, 2005 Share Posted November 15, 2005 (edited) think theres no help CAIP I got the problem yesterday...my ping jumps like bugs bunny.... it starts at 18.00 and was over at 20.00...time the most europeans turned on their TV and leave the Internet its definitiv a problem of heavy traffic over the ocean Edited November 15, 2005 by {SFI}Natter Quote Link to comment Share on other sites More sharing options...
MajorPayne Posted November 15, 2005 Share Posted November 15, 2005 Have you guys contacted your Internet service providers? They may be able to explain things to you (maybe it's network problems etc) Quote Link to comment Share on other sites More sharing options...
Moody Posted November 15, 2005 Share Posted November 15, 2005 Today I have a nice ping of 380 Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 15, 2005 Share Posted November 15, 2005 Lookilooki at my traceroute in my post above. Things seem to get slow near cybercon. Is it possible that your NS server is hosted by them? Ah, 64.37.104.75 IS the NS-server's IP.... Quote Link to comment Share on other sites More sharing options...
Moody Posted November 15, 2005 Share Posted November 15, 2005 Tonight i saw an american having the same problem too (Achilles) and my ping was 706 in sfi server. Quote Link to comment Share on other sites More sharing options...
NiXsa Posted November 15, 2005 Share Posted November 15, 2005 My ping was about 500 Quote Link to comment Share on other sites More sharing options...
Eliteone Posted November 15, 2005 Share Posted November 15, 2005 See how your pings are in the two DM servers I have them in a different location that the SFI DD server. Quote Link to comment Share on other sites More sharing options...
Moody Posted November 15, 2005 Share Posted November 15, 2005 Usually my ping is getting better around this time but today it was high all day. One time it was 1400!! Quote Link to comment Share on other sites More sharing options...
Caip Posted November 16, 2005 Author Share Posted November 16, 2005 , please stop it. I will do this tracing shiz tonight and post about it here! Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 16, 2005 Share Posted November 16, 2005 Are you STILL having the same problem? Didn't get any better? Better write to your ISP's support then, think Major is right there. I'm still convinced that the NS server's problem is another one, but my ping on the SFI server is "better" now. Feels jumpy, but that's only a feelin'. I just played on the mod test server Elite put up. My ping was around 180 from start, but every 2-3 minutes I had a bigtime lag, for about 10 secs or so. Perhaps your problems are different, Caip. And post something about your connection, router or not, which DSL modem you're having etc... Quote Link to comment Share on other sites More sharing options...
Eliteone Posted November 16, 2005 Share Posted November 16, 2005 You could try the flush DNS then renew DNS commands in case that was an issue with your ISP. also the ipconfig /renew But best recourse is to let your ISP know you are having issues. Quote Link to comment Share on other sites More sharing options...
Caip Posted November 16, 2005 Author Share Posted November 16, 2005 Routenverfolgung zu 64.34.47.10 über maximal 30 Abschnitte 1 2 ms 1 ms 1 ms p549EE5C9.dip.t-dialin.net [84.158.229.201] 2 112 ms 22 ms 20 ms 217.0.116.67 3 18 ms 18 ms 18 ms 217.0.68.198 4 209 ms 210 ms 208 ms nyc-e5.NYC.US.net.DTAG.DE [62.154.14.53] 5 207 ms 206 ms 205 ms 62.156.138.46 6 206 ms 206 ms 206 ms dcr3-so-1-1-0.NewYork.savvis.net [204.70.192.209 ] 7 209 ms 208 ms 210 ms kar2-ae1.NewYork.savvis.net [208.174.228.18] 8 209 ms 253 ms 249 ms 204.70.150.254 9 228 ms 206 ms 338 ms 216.187.115.217 10 210 ms 209 ms 208 ms 216.187.115.158 11 * 212 ms 211 ms 216.187.115.162 12 207 ms 206 ms 209 ms 64.34.47.10 Ablaufverfolgung beendet. Routenverfolgung zu Cisco1.VSK.GS-75 [64.37.104.75] über maximal 30 Abschnit 1 2 ms 1 ms 1 ms p549EE5C9.dip.t-dialin.net [84.158.229.201] 2 22 ms 32 ms 22 ms 217.0.116.67 3 18 ms 18 ms 18 ms 217.0.68.194 4 208 ms 208 ms 208 ms 62.156.131.150 5 204 ms 206 ms 206 ms dt-gw.n54ny.ip.att.net [192.205.32.57] 6 134 ms 134 ms 135 ms tbr2-p032301.n54ny.ip.att.net [12.123.3.110] 7 136 ms 136 ms 199 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54] 8 135 ms 169 ms 134 ms tbr1-cl27.wswdc.ip.att.net [12.122.9.149] 9 184 ms 137 ms 199 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30] 10 136 ms 138 ms 135 ms gbr2-p10.sl9mo.ip.att.net [12.122.11.102] 11 135 ms 134 ms 136 ms gar1-p370.sl9mo.ip.att.net [12.123.24.213] 12 135 ms 137 ms 136 ms cybercon.com [12.118.144.70] 13 596 ms 239 ms 258 ms gig408.sw2.cybercon.com [216.15.195.53] 14 239 ms 238 ms 238 ms Cisco1.VSK.GS-75 [64.37.104.75] Ablaufverfolgung beendet. That's what I got...so...what does it mean? Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 16, 2005 Share Posted November 16, 2005 Traceroute shows us the route your packets are taking and the roundtrip time for each hop (=>from server to server). The time seems to be relatively high in Germany but that doesn't have to mean a thing. For statistical analysis of the ping (response time) the command "pathping" is used. You could do one more thing: I see you're directly connected to a DSL modem. When you start up your PC, go quickly to the shell and type: ping -n 20 64.34.47.10 Interesting would be if your ping stays constant or jumps and more importantly if you're experiencing packet losses. That would point to a problem of your ISDN connection. The fact that your ping gets better after a while points to the same. Repeat this after 10 minutes or so to see if the ping changed. Here's what I got back with the command above: E:\>ping -n 20 64.34.47.10 Ping wird ausgeführt für 64.34.47.10 mit 32 Bytes Daten: Antwort von 64.34.47.10: Bytes=32 Zeit=144ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=140ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=142ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=141ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=140ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=140ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=142ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=141ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=141ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=141ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=144ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=137ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=143ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=141ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=139ms TTL=117 Ping-Statistik für 64.34.47.10: Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 137ms, Maximum = 144ms, Mittelwert = 140ms Finally, one more thing you could do: Unless you have the old, big, white standard T-Com Siemens DSL-modem, which is DAMAGED when you pull the plug, try to pull the plug of your DSL-modem and reconnect it after 30 secs or so. That way the modem will take a new measurement of the DSL transmission channel. And some modems allow the reading out of channel information from their memory, though I don't know exactly how (since mine doesn't). Sometimes the manufacturer releases appropriate tools. Quote Link to comment Share on other sites More sharing options...
Eliteone Posted November 17, 2005 Share Posted November 17, 2005 I'm curious have any of your having these issues contacted your ISP yet? If so what did they tell you? Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 17, 2005 Share Posted November 17, 2005 I've found a German site with some manuals about reading out the channel data from DSL modems. Not too many modems described on the page, but perhaps you're lucky. http://www.modemhilfe.de.vu/ Usually, when the Deutsche Telekom tech support is contacted, they can't find the fault. If you insist that it's there, they send over a technician to "reset the port" as they call it. If the problem persists and you're really really lucky, they change the port. And if that doesn't help, and if you're as lucky as I was a few weeks ago, they can connect you to a differen DSLAM. But that's rather unlikely. Quote Link to comment Share on other sites More sharing options...
Natter Posted November 17, 2005 Share Posted November 17, 2005 Heres a good DSL-help forum: www.dslclub.de Quote Link to comment Share on other sites More sharing options...
Caip Posted November 17, 2005 Author Share Posted November 17, 2005 thanks a bunch folks, Antwort von 64.34.47.10: Bytes=32 Zeit=207ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=209ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=203ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=204ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=208ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=202ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=206ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=204ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=205ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=207ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=203ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=204ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=206ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=206ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=206ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=208ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=207ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=205ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=208ms TTL=117 Antwort von 64.34.47.10: Bytes=32 Zeit=208ms TTL=117 Ping-Statistik für 64.34.47.10: Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 202ms, Maximum = 209ms, Mittelwert = 205ms so...what does this say? Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 17, 2005 Share Posted November 17, 2005 No packet losses, stable ping. That means you don't want to make it too easy for us, do you? No idea besides contacting your ISP. If you can find the time check if there is software for reading out modem data available for your DSL modem type. Should be available from the manufacturers site. But prolly even these data won't give a hint. I'm wondering why your ping was so low anyway. My best ping on the regular SFI DD server is 140. Yours always has been 113 you say. Another question: is it possible that you got switched over from fastpath to interleaving? Did you have fastpath? As a Telekom customer I'd have to pay extra for it. Quote Link to comment Share on other sites More sharing options...
Caip Posted November 17, 2005 Author Share Posted November 17, 2005 I have fastpath...I hope I still do have it Will contact my IPS tomorrow... Quote Link to comment Share on other sites More sharing options...
RXS Posted November 20, 2005 Share Posted November 20, 2005 Maybe this will help, please don't tell me you opened it.... If you receive an email entitled "Bedtimes" delete it IMMEDIATELY. Do not open it. Apparently this one is pretty nasty. It will not only erase everything on your hard drive, but it will also delete anything on disks within 20 feet of your computer. It causes your ping to wildly fluctuate and it demagnetizes the strips on ALL of your credit cards. It reprograms your ATM access code, screws up the tracking on your VCR, and uses subspace field harmonics to scratch any CD's you attempt to play. It will program your phone auto dial to call only 0898 numbers. This virus will mix antifreeze into your fish tank. IT WILL CAUSE YOUR TOILET TO FLUSH WHILE YOU ARE SHOWERING. It will drink ALL your beer. FOR GOD'S SAKE, ARE YOU LISTENING?? It will leave dirty underwear on the coffee table when you are expecting company. It will replace your shampoo with Nair and your Nair with Rogaine. If the "Bedtimes" message opens in a Windows 95/98 environment, it will leave the toilet seat up and leave your hair dryer plugged in dangerously close to a full bathtub. It will not only remove the forbidden tags from your mattresses and pillows, it will also refill your skim milk with whole milk. WARN AS MANY PEOPLE AS YOU CAN. And if you don't send this to 5000 people in 20 seconds, you'll fart so hard that your right leg will spasm and shoot straight out in front of you, sending sparks that will ignite the person nearest you. Send this warning to everyone!!! Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 20, 2005 Share Posted November 20, 2005 Mah, I had the same problems again today (and yesterday) on the NS server. Ping of 270 ms. Today it dropped after a while to 180, which is quite "normal". Gonna shout at tech support too I think. RXS, could you please verify that my firewall is set up correctly? The link below takes you to a picture of my firewall settings. My firewall Quote Link to comment Share on other sites More sharing options...
RXS Posted November 20, 2005 Share Posted November 20, 2005 Quote Link to comment Share on other sites More sharing options...
Natter Posted November 20, 2005 Share Posted November 20, 2005 (edited) Best prevent vs a virus and all kinda cold is a warm pair of Knickerbocker-trousers Edited November 20, 2005 by {SFI}Natter Quote Link to comment Share on other sites More sharing options...
Caip Posted November 26, 2005 Author Share Posted November 26, 2005 Sooo...I called my ISP today asking them wth is up. They checked my line and said that everything was running smoothly. Thus I doubt it's my line who messes it up. The good news is that my ping on the DM servers is quite normal and my ping on sfi dd server is stable at 190 now I think (hope). E1, did you change something on the servers maybe? Like new server location or shix? And if not...what shall I do? :S Quote Link to comment Share on other sites More sharing options...
Alexa Posted November 26, 2005 Share Posted November 26, 2005 Well, I did several pathpings to the NS server (on which my ping is nearly double as high as a month ago). Down here is a summary of the results: pathping 64.37.104.75 Routenverfolgung zu Cisco1.VSK.GS-75 [64.37.104.75] über maximal 30 Abschnitte: 0 cola [192.168.1.34] 1 192.168.1.1:...........0ms 2 217.0.116.64 3 217.0.68.150...........53ms 4 62.156.131.150...........156ms 5 dt-gw.n54ny.ip.att.net [192.205.32.57]...........140ms 6 tbr1-p012201.n54ny.ip.att.net [12.123.3.106] 7 tbr1-cl14.cgcil.ip.att.net [12.122.10.2] 8 tbr2-cl22.cgcil.ip.att.net [12.122.9.134] 9 tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 10 gbr1-p40.sl9mo.ip.att.net [12.122.11.114] 11 gar1-p360.sl9mo.ip.att.net [12.123.24.209] 12 cybercon.com [12.118.144.70]...........276ms 13 gig408.sw2.cybercon.com [216.15.195.53]...........299ms 14 Cisco1.VSK.GS-75 [64.37.104.75]...........272ms As you can see the ping at No. 4 is already relatively high. Great that No. 6 to 11 don't respond to pings. Apparently the trouble starts there somewhere I think. What makes me wonder is that Nat from Bavaria had a reasonable ping on the NS server while I had the usual 280...Perhaps another gateway? I think the Telekom changed the networks structure or such. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.