Ticket for can't reach server

[Taxfrogmanful]

I've tried all the different addresses. I've double checked again. I ran a tracert and get timed out at the router/device after THE-OPTIMAL.bar1.Houston1.Level3.net. I've tried directly connecting

I always get the error "Can't reach server"

I just got whitelisted a minute ago. Could this be the problem?

 

[Jonsoon]

We have a greylist, so even if you aren't whitelisted you can still connect, so that does not matter.

Generally from what I have seen, this client side. Can't tell you why or how to fix it, though. Sorry.

 

[Kainzo]

I've tried all the different addresses. I've double checked again. I ran a tracert and get timed out at the router/device after THE-OPTIMAL.bar1.Houston1.Level3.net. I've tried directly connecting to the....

I always get the error "Can't reach server"

I just got whitelisted a minute ago. Could this be the problem?

We block all ping requests - ICMP is completely locked down at the router/switch level.

We aren't actively blocking any ip's at this time. Reboot your router/computer - try again...

 

[TheYeti]

If you are not getting past level3 in houston I would say most likely you are having a routing issue. Attach entire tracert output for anything more usefull besides speculation.

 

[Taxfrogmanful]

Sorry about the delay. Real life and all.


Tracert output:
C:\Users\*****>tracert us.hc.to

Tracing route to us.hc.to [66.187.71.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 20 ms 20 ms ptld-dsl-gw49.ptld.qwest.net [207.225.84.49]
3 20 ms 19 ms 72 ms ptld-agw1.inet.qwest.net [207.225.86.129]
4 24 ms 24 ms 23 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 * 24 ms 31 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
6 78 ms 76 ms 77 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

7 148 ms 162 ms 183 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
8 76 ms 77 ms 76 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

9 102 ms 103 ms 105 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 76 ms 81 ms 76 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

11 144 ms 143 ms 145 ms ae-61-61.ebr1.Dallas1.Level3.net [4.69.151.126]

12 82 ms 84 ms 80 ms ae-1-13.bar1.Houston1.Level3.net [4.69.137.137]

13 110 ms 113 ms 111 ms THE-OPTIMAL.bar1.Houston1.Level3.net [4.78.15.11
4]
14 * * * Request timed out.
15 * * ^C[DOUBLEPOST=1368470190][/DOUBLEPOST]Fixed. My home router was re-routing all my MC traffic to my server computer. I just turned it off.

 

[Kainzo]

Sorry about the delay. Real life and all.


Tracert output:
C:\Users\*****>tracert us.hc.to

Tracing route to us.hc.to [66.187.71.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 20 ms 20 ms ptld-dsl-gw49.ptld.qwest.net [207.225.84.49]
3 20 ms 19 ms 72 ms ptld-agw1.inet.qwest.net [207.225.86.129]
4 24 ms 24 ms 23 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 * 24 ms 31 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
6 78 ms 76 ms 77 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

7 148 ms 162 ms 183 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
8 76 ms 77 ms 76 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

9 102 ms 103 ms 105 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 76 ms 81 ms 76 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

11 144 ms 143 ms 145 ms ae-61-61.ebr1.Dallas1.Level3.net [4.69.151.126]

12 82 ms 84 ms 80 ms ae-1-13.bar1.Houston1.Level3.net [4.69.137.137]

13 110 ms 113 ms 111 ms THE-OPTIMAL.bar1.Houston1.Level3.net [4.78.15.11
4]
14 * * * Request timed out.
15 * * ^C[DOUBLEPOST=1368470190][/DOUBLEPOST]Fixed. My home router was re-routing all my MC traffic to my server computer. I just turned it off.

Ah ha!