Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Lag on SourceOP

  1. #11
    Retribution's Avatar



    Join Date
    Apr 24, 2006
    Last Online
    Nov 02, 2008
    Posts
    934
    Threads
    67




    well that don't help much, i'm trying help the laggers on COD4 not lag anymore

  2. #12
    avy's Avatar



    Join Date
    Dec 06, 2007
    Last Online
    Jul 14, 2011
    Posts
    579
    Threads
    16




    sorry... most people use google.

    Go to command prompt and type in the following:

    tracert anywebaddress.com or ip

    There are also a few extra things that you can add to the string but for the most part you wont need them. (ie, max number of hops, timeout wait limit etc.)

  3. #13
    Retribution's Avatar



    Join Date
    Apr 24, 2006
    Last Online
    Nov 02, 2008
    Posts
    934
    Threads
    67




    ok thaks i found the trace route, no how do you find packet loss?

  4. #14
    avy's Avatar



    Join Date
    Dec 06, 2007
    Last Online
    Jul 14, 2011
    Posts
    579
    Threads
    16




    packet loss is generally reported using the ping command...

    ping anywebaddress.com or ip

    The results should show up generally along these lines:

    Code:
    Pinging www.apple.com [17.254.0.91] with 32 bytes of data:
    
    Reply from 17.254.0.91: Bytes=32 time=37ms TTL=46
    Packet loss is reported in the results as a percentage. So if/when I ping I generally ping with 25 packets just to get a decent percentage.

    As before, there are additional options on the ping command.

    ping www.google.com -t would continually ping google until you interrupt the process.

    ping www.google.com -n 7 would ping google 7 times.

    ping www.google.com -l 1024 would ping google with packets 1024 bytes in size. Default is 32 if I remember right and 8192 is the max.

    enjoy.

Page 2 of 2 FirstFirst 12

Tags for this Thread