Can't reach Combatace. Get server not responding messages

[Rends 166]

Hi,

I can only reach the website here and there. A lot of times i get a server not responding message.

Tried it with IE from Pc and with Safari from my iPad.

I can't remember having this trouble with any other website.

Any suggestioned?

[+Erik 1,812]

There should never be that problem and this is the first I've heard of it. Networking wise you should be minimized in this day in age. Can you provide a traceroute to us when you're having this problem and one when you're not? I can give it to our upstream and see what they can get resolved for you.

 

Thanks.

[MigBuster 2,884]

Also posed here http://simhq.com/forum/ubbthreads.php/topics/3895732/Re_CombatACE_server_not_respon#Post3895732

[+Erik 1,812]

The simple answer is. I don't know. Unless I can get more specific information it's impossible to figure out. There's no reason our inbound traffic would be blocked, that's like shooting ourselves in the foot. There are so many connection configurations the answer is too large to even guess at. I need point to point details.

[Rends 166]

Happend today again. No connection with http adress and not with the ip adress.

But icould connect to combatace using a proxy website (http://proxywebsite.org)

I want tohelp but need to know how do i traceroute?

[+Erik 1,812]

Go to whatismyip.org and tell me what your external IP is showing as.

[Rends 166]

84.141.190.144

[+Erik 1,812]

Ok, from our server to you.

 

root@server2 [~]# traceroute 84.141.190.144
traceroute to 84.141.190.144 (84.141.190.144), 30 hops max, 40 byte packets
1  server2.combatace.com (216.104.36.209)  0.696 ms  1.026 ms  1.341 ms
2  dr6506b.ord02.singlehop.net (99.198.126.145)  0.450 ms  0.521 ms  0.595 ms
3  xe-1-2-0.er2.ord2.us.above.net (64.124.200.141)  0.377 ms  0.411 ms  0.403 ms
4  xe-0-1-0.cr2.ord2.us.above.net (64.125.25.109)  0.605 ms  0.600 ms  0.590 ms
5  ae5.cr1.ord2.us.above.net (64.125.28.233)  21.758 ms  21.752 ms  21.742 ms
6  ae5.er1.ord7.us.above.net (64.125.20.38)  0.502 ms  0.531 ms  1.483 ms
7  80.150.171.65 (80.150.171.65)  1.249 ms  1.289 ms  1.263 ms
8  ki-ea1-i.KI.DE.NET.DTAG.DE (62.154.100.58)  121.987 ms  122.784 ms  122.551 ms
9   (217.0.71.9)  118.572 ms  119.010 ms  118.064 ms
10  * * *
11  * * *

 

I get a timeout which means our machine isn't able to reach your IP at #10 so the machine after 217.0.71.9 is the culprit. As you can see from the line above that's already in Germany at DTAG.DE. Now it's possible the machine at #10 is yours and you're running some type of filtering software which means nothing other than I can't see what's happening past that point.

 

To run a trace route here's what you do.

 

> OPEN A CMD PROMPT (start > run > CMD + [ENTER]) or (start > all programs > accessories > cmd prompt)

> At the command line enter: tracert combatace.com [ENTER]

 

Let the trace complete and then highlight and copy all the lines it returned. (right click in header of command window > choose mark > highlight text > [ENTER])

 

Then paste what you copied here.

 

Thanks.

[Rends 166]

Ok, here is what i got:

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Michi>tracert combatace.com

Routenverfolgung zu combatace.com [216.104.36.210] über maximal 30 Abschnitte:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    10 ms    10 ms    10 ms  217.0.116.101
  3    11 ms    12 ms    12 ms  217.0.71.2
  4   133 ms   131 ms   132 ms  chi-sb1-i.CHI.US.NET.DTAG.DE [62.154.15.161]
  5   198 ms   204 ms   212 ms  80.150.171.66
  6   131 ms   130 ms   138 ms  ae0.cr1.ord2.us.above.net [64.125.20.37]
  7   128 ms   132 ms   129 ms  xe-1-1-0.er1.ord2.us.above.net [64.125.26.186]
  8   128 ms   128 ms   128 ms  64.124.200.138.allocated.above.net [64.124.200.1
38]
  9   133 ms   134 ms   132 ms  asw-c16g.r02.ord02.singlehop.net [99.198.126.142
]
 10   128 ms   128 ms   127 ms  trinity.combatace.com [216.104.36.210]

Ablaufverfolgung beendet.

[+Erik 1,812]

Well your outbound to us is solid, 10 hops and 128ms from Germany to the US is great. You are resolving us correctly at 216.104.36.210. So the only thing I can see is that it's us returning anything to you. Known fixes might be call your ISP, reset your router and system, check any firewall or internet security suite you might have, unplug from any router and go straight to the internet modem. You can give the trace routes to and from us above to your ISP if needed.

 

I would have more complaints about this if it were more widespread so I have to hope this is isolated. We are in a highly robust data center with a datacenter in copenhagen which they carry back from.

 

Please keep me advised as to what you find out. As a precaution I have submitted this information to our upstream provider to see what they can sort out.

 

Thanks and I apologize for the trouble you're having.

[Rends 166]

Ok , thx for your help.

Will check everything soon and call my ISP if needed.

Will report if i find a solution.

 

Rends

[Fubar512 1,350]

  1     1 ms     1 ms     1 ms  192.168.1.1    =    This is your default gateway, and from the address, I can tell  that you're going through a router
  2    10 ms    10 ms    10 ms  217.0.116.101   =   This is your public IP as provided by your ISP, and this where the data stream is being dropped
  3    11 ms    12 ms    12 ms  217.0.71.2   =  This is your ISP's address

[MigBuster 2,884]

Ok , thx for your help.

Will check everything soon and call my ISP if needed.

Will report if i find a solution.

 

Rends

 

You mentioned you could get to CA using a Proxy site (when you couldn't otherwise) - so that says to me is has to be your ISP screwing around with its infrastructure. Have rang mine in the past and they admit to doing maint - so could be a case of being patient if so.

[Rends 166]

Happened a few minutes ago again.

 

...

C:\Users\Michi>tracert combatace.com

Routenverfolgung zu combatace.com [216.104.36.210] über maximal 30 Abschnitte:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    11 ms    12 ms    12 ms  217.0.116.101
  3    12 ms    12 ms    11 ms  217.0.71.2
  4   132 ms   131 ms   134 ms  chi-sb1-i.CHI.US.NET.DTAG.DE [62.154.15.161]
  5   129 ms   144 ms   128 ms  80.150.171.66
  6   131 ms   131 ms   145 ms  ae0.cr1.ord2.us.above.net [64.125.20.37]
  7   128 ms   127 ms   179 ms  xe-0-1-0.er1.ord2.us.above.net [64.125.25.106]
  8   129 ms   128 ms   129 ms  64.124.200.138.allocated.above.net [64.124.200.1
38]
  9   133 ms   133 ms   132 ms  asw-c16g.r02.ord02.singlehop.net [99.198.126.142
]
 10     *        *        *     Zeitüberschreitung der Anforderung.
 11     *        *        *     Zeitüberschreitung der Anforderung.
 12     *        *        *     Zeitüberschreitung der Anforderung.
 13     *        *        *     Zeitüberschreitung der Anforderung.
 14     *        *        *     Zeitüberschreitung der Anforderung.
 15     *        *        *     Zeitüberschreitung der Anforderung.
 16     *        *        *     Zeitüberschreitung der Anforderung.
 17     *        *        *     Zeitüberschreitung der Anforderung.
 18     *        *        *     Zeitüberschreitung der Anforderung.
 19     *        *        *     Zeitüberschreitung der Anforderung.
 20     *        *        *     Zeitüberschreitung der Anforderung.
 21     *        *        *     Zeitüberschreitung der Anforderung.
 22     *        *        *     Zeitüberschreitung der Anforderung.
 23     *        *        *     Zeitüberschreitung der Anforderung.
 24     *        *        *     Zeitüberschreitung der Anforderung.
 25     *        *        *     Zeitüberschreitung der Anforderung.
 26     *        *        *     Zeitüberschreitung der Anforderung.
 27     *        *        *     Zeitüberschreitung der Anforderung.
 28     *        *        *     Zeitüberschreitung der Anforderung.
 29     *        *        *     Zeitüberschreitung der Anforderung.
 30     *        *        *     Zeitüberschreitung der Anforderung.

 

Solved it this time by disconnecting/reconnecting my Internet Connection. Guess i got a new IP afterwards.

Edited January 19, 2014 by Rends

[pcc001 1]

I have this issue consistently. So much so that I gave up on the site for quite some time. My ip is 98.17.119.60. I've spoken at length to my ISP and they say they are not blocking the site. In fact, the tech I spoke with said they could pull up the site. I have performed a tracert to the server (216.104.36.210 as reported by a DNS lookup). The trace times out after 67.212.190.90. Please email me what my next step should be. Thanks!

[+Erik 1,812]

This is an ISP problem. I've contacted Windstream if this persists please open a new ticket with them.

 

Thank you.

[pcc001 1]

Thanks for your call to Windstream. After literally months of trying to get this resolved with them, tonight, miraculously, I can get to the site. I greatly appreciate the help!