11 replies to this topic

[EDLOVER]

Does anyone know if the comstar na ts3 server is down? (na1.mech-connect.net)
Teamspeak says "failed to resolve hostname"
I can not connect. been unable to connect for 2 days. any info would be appreciated thanks.

[crustydog]

I heard something to this effect, yes.

Rumor says someone is looking into it:)

[Lyoto Machida]

How embarrassing for Comstar to be out of c-bills...

[Appogee]

Update your TeamSpeak bookmark to this IP address: 54.172.1.90

[JohnnyWayne]

The dark age has begun.

[Mechwarrior Buddah]

Grisbane, on 03 October 2015 - 05:37 AM, said:

so does this mean i can get my Jupiter now?

No, youre stuck with this:

[JohnnyWayne]

It means we can wait about 40 years now before something new happens. xD

Edited by JohnnyWayne, 03 October 2015 - 07:38 AM.

[STEF_]

Comstar is been interdicted!

LOL

[Aceramic]

There was another thread (somewhere here in General Discussion, but this one was first when I started scrolling down the list...) that I responded to, in which the information was mostly correct.

The domain name for Comstar was transferred from our old host to Amazon (to condense everything into one provider), during that process, Comstar went down. The server is back up (and available at the IP address, I think the correct one was posted above), but DNS has not propagated yet. We're currently waiting on a response from Amazon about the issue (it typically takes 24 hours, it has now been more than 48, and it has not propagated out of Amazon's network. DNS lookups to Amazon's servers will return the IP address for the domain, but not from any other DNS that we have tested).

I'll update whatever thread about Comstar is closest to the top whenever we know more. >.>

Edit: If you don't want to connect by IP, a temporary server is also available at mwo.syn-games.com.

Edited by Aceramic, 03 October 2015 - 05:31 PM.

[EDLOVER]

Thanks, Aceramic.

[Aceramic]

Comstar should be back up via DNS now. Apparently, Amazon was propagating the DNS... To servers that don't exist. They have the correct addresses now, so things should return to normal shortly. If you still can't connect, either give it some time (24 hours, for real this time), or you can try entering "ipconfig /flushdns" without the quotes at a Windows command prompt (you Linux people are out of luck, I can't help you. ).