Follow us on Steam Follow us on FB Follow us on Twitter Subscribe on Youtube

Announcement

Collapse
No announcement yet.

Damn Packet loss

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Damn Packet loss

    As some of you already know I've been experiencing horrid packet loss recently and I'm really pissed off with my ISP. I had no problems for a year and now I have major PL. So now I'm wrestling with their support staff and NOC staff to identify and correct the problem. I was just wondering if you guys had any good input on how to prove packet loss besides tracert/pathping, good websites/utils things of that nature.
    For you HTM server admins I could really use some connection stats, or any other serverside network info from my ip address. Also if any of you have any routing resources on the net, like a buddy who works @ a backbone ISP or something. Any help would be great, thanks.

    All else fails I'm already looking @ other ISP's, hoping beyond hope that Verizon FIOS is available in my area. Eeeee fiber...
    Mind as muscle, Body as energy, Spirit as thought.
    sigpic
  • #2

    Tracert from Dallas NOC:

    Code:
    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.
    
    C:\Documents and Settings\**********>tracert 208.58.61.18
    
    Tracing route to 208-58-61-18.c3-0.eas-ubr10.atw-eas.pa.cable.rcn.com [208.58.61.18]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  72.249.10.33
      2    <1 ms    <1 ms    <1 ms  206.123.64.97
      3     1 ms    <1 ms    <1 ms  206.123.64.37
      4     1 ms     1 ms     1 ms  border4.g3-2.colo4dallas-3.ext1.dal.pnap.net [216.52.189.9]
      5     1 ms     1 ms     1 ms  core2.tge5-2-bbnet2.ext1.dal.pnap.net [216.52.191.97]
      6     1 ms     1 ms     1 ms  ge-6-22-117.car1.Dallas1.Level3.net [209.246.152.245]
      7     1 ms     1 ms     1 ms  ae-2-52.bbr2.Dallas1.Level3.net [4.68.122.33]
      8    33 ms    33 ms    33 ms  ae-0-0.bbr2.Washington1.Level3.net [4.68.128.210]
      9    34 ms    34 ms    34 ms  ae-43-99.car3.Washington1.Level3.net [4.68.17.197]
     10    40 ms    40 ms    41 ms  RCN-CORPORA.car3.Level3.net [63.210.25.210]
     11    41 ms    41 ms    41 ms  ge9-3-0.core3.lnh.md.rcn.net [207.172.19.65]
     12    41 ms    40 ms    41 ms  pos6-0.core2.phdl.pa.rcn.net [207.172.19.20]
     13    40 ms    41 ms    41 ms  ge6-1.aggr1.phdl.pa.rcn.net [207.172.15.53]
     14    48 ms    49 ms    48 ms  ge0-1.eas-ubr10.atw-eas.pa.cable.rcn.net [208.59.252.75]
     15    57 ms    55 ms    55 ms  208-58-61-18.c3-0.eas-ubr10.atw-eas.pa.cable.rcn.com [208.58.61.18]
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
    I assume the timeout is where I hit your firewall. I cannot check for PL with your firewall enabled, for it will show 100% PL.

    Comment

    • #3

      yes those would be my internal ip's, thats fine the last three addresses are not the problem, no pl on them. I sent 4 traces of the UR^ 1v1 servers to my ISP 's NOC and will send this along too. thank you for the trace.
      Mind as muscle, Body as energy, Spirit as thought.
      sigpic

      Comment

      Working...
      X