16 Replies Latest reply: Feb 6, 2013 6:14 AM by Arti4 RSS

tracert and pingtest to others players in my match. Strange

cottonsocks

Just played a few games connected via net limiter on the xbox, If you didnt know, it gives you the ip addresses of all people in your game and you can work out who is host becouse all the traffic travels thru their ip address. 

 

Thing is i was doing a tracert and it was only working about 15% of the time to the host of each game,most timed out after a while but it would go far enough to see most isp's names like sky or virgin or what ever...The ones it did work on i was able to do a ping test and all were under 50ms, all the others timed out.

 

Why would some work and some not????? 

 

Could this be causing the lag?????

 

Here is a couple of  examples

 

 

Tracing route to [Removed by Moderator.]

over a maximum of 30 hops:

 

 

[Removed by Moderator.]

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

14     *        *        *     Request timed out.

15     *        *        *     Request timed out.

16     *        *        *     Request timed out.

17     *        *        *     Request timed out.

18     *        *        *     Request timed out.

19     *        *        *     Request timed out.

20    45 ms    45 ms    48 ms  [Removed by Moderator.]

 

Trace complete.

 

 

 

 

 

 

Another example tracert and ping to host that worked. Was a cracking connection by the way..

 

Pinging [Removed by Moderator.] with 32 bytes of data:

Reply from 108.61.230.200: bytes=32 time=19ms TTL=109

Reply from 108.61.230.200: bytes=32 time=22ms TTL=109

Reply from 108.61.230.200: bytes=32 time=20ms TTL=109

Reply from 108.61.230.200: bytes=32 time=20ms TTL=109

 

 

Ping statistics for [Removed by Moderator.]

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 19ms, Maximum = 22ms, Average = 20ms

 

 

--------------------------------------

 

 

[Removed by Moderator.]

over a maximum of 30 hops:

 

 

[Removed by Moderator.]

  9     *        *        *     Request timed out.

10     *        *        *     Request timed out.

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

14     *        *        *     Request timed out.

15     *        *        *     Request timed out.

16     *        *        *     Request timed out.

17     *        *        *     Request timed out.

18     *        *        *     Request timed out.

19     *        *        *     Request timed out.

20    21 ms    21 ms    31 ms  [Removed by Moderator.] [Removed by Moderator.]

 

 

Trace complete

  • Re: tracert and pingtest to others players in my match. Strange
    cottonsocks

    the ones that didnt work went the full 30 hops and timed out

    • Re: tracert and pingtest to others players in my match. Strange
      cottonsocks

      Heres another 1 to a host that didnt work????

       

      Pinging 92.21.48.xxx with 32 bytes of data:

      Request timed out.

      Request timed out.

      Request timed out.

      Request timed out.

       

       

      Ping statistics for 92.21.48.xxx:

          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

       

       

      Pinging 92.21.48.xxx with 32 bytes of data:

      Request timed out.

      Request timed out.

      Request timed out.

      Request timed out.

       

       

      Ping statistics for [Removed by Moderator.]:

          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

       

       

       

      Microsoft Windows [Version 6.1.7601]

      Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

       

       

      C:\Windows\System32>tracert [Removed by Moderator.]

      Unable to resolve target system name [Removed by Moderator.].

       

       

      C:\Windows\System32>tracert [Removed by Moderator.]

      Unable to resolve target system name [Removed by Moderator.].

       

       

      C:\Windows\System32>tracert [Removed by Moderator.]

       

       

      Tracing route to 108.61.230.200.choopa.net [Removed by Moderator.]

      over a maximum of 30 hops:

       

       

      [Removed by Moderator.]

        9     *        *        *     Request timed out.

      10     *        *        *     Request timed out.

      11     *        *        *     Request timed out.

      12     *        *        *     Request timed out.

      13     *        *        *     Request timed out.

      14     *        *        *     Request timed out.

      15     *        *        *     Request timed out.

      16     *        *        *     Request timed out.

      17     *        *        *     Request timed out.

      18     *        *        *     Request timed out.

      19     *        *        *     Request timed out.

      20    21 ms    21 ms    31 ms  [Removed by Moderator.]

       

       

      Trace complete.

       

       

       

      C:\Windows\System32>tracert 92.21.48.xxx

       

       

      Tracing route to host-92-21-48-xxx.as13285.net [92.21.48.xxx]

      over a maximum of 30 hops:

       

       

      [Removed by Moderator.]

        8     *        *        *     Request timed out.

        9     *        *        *     Request timed out.

      10     *        *        *     Request timed out.

      11     *        *        *     Request timed out.

      12     *        *        *     Request timed out.

      13     *        *        *     Request timed out.

      14     *        *        *     Request timed out.

      15     *        *        *     Request timed out.

      16     *        *        *     Request timed out.

      17     *        *        *     Request timed out.

      18     *        *        *     Request timed out.

      19     *        *        *     Request timed out.

      20     *        *        *     Request timed out.

      21     *        *        *     Request timed out.

      22     *        *        *     Request timed out.

      23     *        *        *     Request timed out.

      24     *        *        *     Request timed out.

      25     *        *        *     Request timed out.

      26     *        *        *     Request timed out.

      27     *        *        *     Request timed out.

      28     *        *        *     Request timed out.

      29     *        *        *     Request timed out.

      30     *        *        *     Request timed out.

       

       

      Trace complete.

  • Re: tracert and pingtest to others players in my match. Strange

    Some Routers block ping requests with their firewalls, if you get a "request time out" then its most likely because of his firewall.

  • Re: tracert and pingtest to others players in my match. Strange
    jaysonsp

    Some people configure their router to block ping responses so nosey people like you cannot find out this information.    

     

    I rarely have any lag in this game so I do not understand why so many people are complaining about it.   

  • Re: tracert and pingtest to others players in my match. Strange
    NiteFalken

    Which net limiter are you using?

     

    I would be interested inseeing this for myself.

  • Re: tracert and pingtest to others players in my match. Strange

    Did you build a gateway to do this?  Ive got a linux gateway that I use for testing the effects of latency sometimes, but never tried it with a windows gateway.

     

    The timeouts are pretty normal.  Lots of routers are not pingable, but as long as you got the destination, everything is working.  In the one with choopa, the timeouts are probably choopa routers.

  • Re: tracert and pingtest to others players in my match. Strange
    gdexter

    I don't think it's wise to post people's IP addresses here on a forum...

  • Re: tracert and pingtest to others players in my match. Strange
    Foxhound-Pro

    Removing text. Sorry, but you can't simply come to the boards and start posting people's personal IP addresses. That's a huge no-no.

  • Re: tracert and pingtest to others players in my match. Strange
    adeadfox

    I've noticed this to, I setup a script to automatically grab everyone's IP address, geolocate them and test latency. What I found was about 50% or more people simply don't respond to ping requests. What others have said is partly true, people do set there routers to block ping requests.

     

    But I don't think it it's the end user that is blocking ping requests, it's their ISP that is doing it at an attempt to stop the spread of worms/viruses.

     

    I'm sure Treyarch has already found a way around this, it wouldn't be too hard. You don't have to use the traditional "ping" method, you could just create your own that mimics it. You send a special message to another player on port 3074 which you know is open, and just time how long it takes for the other player to respond.

  • Re: tracert and pingtest to others players in my match. Strange
    cottonsocks

    I used netlimiter pro 3 and shared my wireless connection threw my laptop to the xbox via ethernet..It shows all the people in the lobby and all the traffic. Dont really know what a gateway is tho??