Skip to content
Cstolworthy's profile

New Member

 • 

3 Messages

Thu, Jun 26, 2014 2:00 PM

Network traffic being blocked from specific IP?

I have a friend that I am trying to game with, but the problem is that if we play anything that needs to host the server locally it never connects.  We have done a traceroute from his location to mine, and mine to his.  It seems like traffic is being dropped by comcast before it ever has a chance to be delivered.  The same thing happens when he tries to connect to his brother, who also happens to be a comcast customer.  However, if we switch over to a qwest line, we can connect just fine.

 

When he pings me, I can see the ping requests in my firewall logs, so it seems like ICMP traffic is just fine.  However no other connection attempts show up in my firewall logs, so I know the traffic never makes it to me. In his tracert, the last device that talks to him is a comcast device, but it is 2 hops before it would hit me. His IP is 24.243.35.45 and the last comcast device that will respond to him is 68.85.39.53.  The next device it should be talking to is 24.10.184.1, but it never responds.

Responses

Accepted Solution

Problem solver

 • 

305 Messages

7 y ago

Inbound/outbound trace routes could be helpful here. However, as a quick and easy test have both of you bypass your routers and plug directly into your modem and attempt to connect again.

Accepted Solution

New Member

 • 

3 Messages

7 y ago

Here is the tracert from me to him.  I will have to wait until he gets home to get his full tracert.


Tracing route to cpe-24-243-35-45.satx.res.rr.com [24.243.35.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sol.cosmos [10.32.1.1]
2 9 ms 10 ms 8 ms c-24-10-184-1.hsd1.ut.comcast.net [24.10.184.1]
3 13 ms 8 ms 12 ms te-0-6-0-1-sur04.saltlakecity.ut.utah.comcast.net [68.85.39.53]
4 17 ms 11 ms 9 ms te-0-5-0-7-sur03.saltlakecity.ut.utah.comcast.net [69.139.231.53]
5 18 ms 11 ms 11 ms 162.151.9.141
6 26 ms 31 ms 23 ms pos-2-1-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.237]
7 39 ms 35 ms 40 ms be-17-pe04.ashburn.va.ibone.comcast.net [68.86.84.230]
8 38 ms 39 ms 40 ms pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.90]
9 39 ms 33 ms 39 ms 173.167.57.118
10 37 ms 40 ms 42 ms 107.14.19.96
11 37 ms 43 ms 39 ms 66.109.6.53
12 46 ms 47 ms 48 ms agg1.snantxvy01r.texas.rr.com [24.175.32.147]
13 42 ms 45 ms 43 ms tge9-6.snautxep01h.texas.rr.com [24.175.32.191]
14 44 ms 46 ms 49 ms tge1-0-0.snautxep-10k1.satx.rr.com [24.28.132.90]
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.

Accepted Solution

New Member

 • 

3 Messages

7 y ago

The thing about that is that I CAN see his ping requests in my firewall log, and he can see my ping requests in his firewall log.  ANY other connection never makes it.

 

Here is his tracert:

Tracing route to c-24-10-186-17.hsd1.ut.comcast.net [24.10.186.17]
over a maximum of 30 hops:
0 Master-PC [192.168.1.2]
1 192.168.1.1
2 142.254.132.77
3 tge7-1.snautxep02h.texas.rr.com [24.28.132.93]
4 tge8-2.snautxep01h.texas.rr.com [24.175.35.252]
5 tge0-11-0-12.snantxvy01r.texas.rr.com [24.175.32.188]
6 agg23.dllatxl301r.texas.rr.com [24.175.32.146]
7 ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
8 * * ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
9 te-0-14-0-1-pe01.1950stemmons.tx.ibone.comcast.net [173.167.59.21]
10 pos-2-0-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.89]
11 he-2-7-0-0-cr01.denver.co.ibone.comcast.net [68.86.85.53]
12 68.86.94.50
13 te-0-1-0-2-sur03.saltlakecity.ut.utah.comcast.net [162.151.9.194]
14 te-6-1-acr07.saltlakecity.ut.utah.comcast.net [68.85.39.50]
15 * * *

Problem solver

 • 

305 Messages

7 y ago

You'll want to be sure that he has bypassed his router and/or enabled ICMP on it before you run yours so we can confirm nothing is blocking it.

Problem solver

 • 

305 Messages

7 y ago

The idea here is to remove anything from the equation that could be blocking the connection. Bypassing the router and disabling firewalls would be helpful not just so we can see a completed trace, but it could also rule out some unknown block that is occurring. This could also rule out some type of port issue.

 

If trace routes from both ends complete and if an MTR doesn't show any loss, than it's not likely Comcast is blocking the connection. 

 

What type of game server are you running? I have a lot of experience with game servers so I may be able to tailor my answers a bit better.