275 replies to this topic

[LawDawg]

[color=#A4A4A4]
Posted Today, 04:36 PM[/color]


Athieros, on 15 July 2014 - 04:33 PM, said:


Alas it did not work for me. I got a little further and got to the log in screen but it crashes shortly after.



Wow, that's gotta be something else altogether. Is it possible you're having this issue?
http://mwomercs.com/...-nothing-works/
(Hint: if you're not running Windows 8.1, then this is something else)


WELL, thats comical...........

[Kyle Polulak]

thunderswamp, on 15 July 2014 - 12:40 PM, said:

here is the dns look up Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. DNS request timed out. timeout was 2 seconds. Non-authoritative answer: DNS request timed out. timeout was 2 seconds. Name: a1982.d.akamai.net Addresses: 23.212.52.11 23.212.52.35 Aliases: patcher.mwomercs.com patcher.mwomercs.com.edgesuite.net

Andrius, on 15 July 2014 - 12:41 PM, said:

C:\Users\Andrius>nslookup patcher.mwomercs.com DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.1.254 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. Non-authoritative answer: Name: a1982.d.akamai.net Addresses: 23.212.109.168 23.212.109.138 Aliases: patcher.mwomercs.com patcher.mwomercs.com.edgesuite.net

From your results, your DNS is provided by your router/modem that your ISP has provided to you. If you could, try rebooting your router and see if that clears it's internal cache.

[Ninthshadow]

Kyle Polulak, on 15 July 2014 - 12:36 PM, said:

If you guys would like to aid in our ability to pinpoint the servers in question, while your DNS settings are set where you cannot proceed with patching; please type into a CMD window: nslookup patcher.mwomercs.com and paste the output here.

This what you were talking about?

non-authoritative answer:
name: a1982.d.akamai.net
addresses: 109.144.113.159
109.144.113.143
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

[Cyphersphere]

"There was an error while connecting:
Unable to connect to the remote server
Would you like to retry?"

• I use google DNS by default.
  
• FlushDNS did not help.
  
• Computer restart did not help.
  
• Using a VPN to connect to various locations across the US and Canada did not work.

[Kyle Polulak]

t9nv3, on 15 July 2014 - 12:42 PM, said:

This is what I get when I run the CMD line Location....Canada Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. >nslookup patcher.mwomercs.com DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 64.71.255.204 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out

As for you, your ISP is the literally the worst ISP on the planet, their DNS servers are the worlds worst; second only to Bell Canada's DNS servers back in the Sympatico days....ugh.

If Rogers is not resolving our domain at all, that is their problem entirely. We have world wide propegation of our records and externally your DNS server resolves correctly. I would suggest rebooting your computer/router and hope Rogers is kind enough to give you something nearly called Internet Access.

[Kyle Polulak]

Cyphersphere, on 15 July 2014 - 12:49 PM, said:

"There was an error while connecting: Unable to connect to the remote server Would you like to retry?"

• I use google DNS by default.
• FlushDNS did not help.
• Computer restart did not help.
• Using a VPN to connect to various locations across the US and Canada did not work.

Just to confirm, this is in the patcher; correct?

[Egomane]

Lobotomite, on 15 July 2014 - 12:52 PM, said:

nslookup patcher mwomercs.com

DNS request timed out.
timeout was 2 seconds.
server: unknown
adress: 70.42.29.74
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.

(location germany)

It's patcher.mwomercs.com

You missed a dot in your attempt

[Andrius]

Rebooting my router didnt help.

[thunderswamp]

still getting the unable to connect server maintenance

[t9nv3]

Kyle Polulak, on 15 July 2014 - 12:51 PM, said:

As for you, your ISP is the literally the worst ISP on the planet, their DNS servers are the worlds worst; second only to Bell Canada's DNS servers back in the Sympatico days....ugh.

If Rogers is not resolving our domain at all, that is their problem entirely. We have world wide propegation of our records and externally your DNS server resolves correctly. I would suggest rebooting your computer/router and hope Rogers is kind enough to give you something nearly called Internet Access.

HAHAHAHA...Thanks man. I've rebooted everything and will just try to be patient.

Edit: I tried rebooting my router twice....but for some reason rebooting my computer resolved this. Sorry for all the hate guys

Edited by t9nv3, 15 July 2014 - 12:59 PM.

[Biaxialrain]

In 3 out of the last 6 games post patch today I have had to quit.


Other mechs start to walk in place, jumping from spot to spot, I can't use the chat, or lock targets.

I can quit and rejoin, then it shows me as dead but I'm still able to go and shoot other mechs with no effect.

[Vimeous]

Despite changing the router DNS to 8.8.8.8 and 8.8.4.4 and flushing I still get servers down for Maint.

C:\Windows\system32>nslookup patcher.mwomercs.com
Server: buffalo.setup
Address: <<PC Internal IP>>

DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 23.212.109.138
23.212.109.168
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

[Cyphersphere]

Kyle Polulak, on 15 July 2014 - 12:54 PM, said:

Just to confirm, this is in the patcher; correct?

Upon launching "E:\Program Files\Piranha Games\MechWarrior Online\Bin32\MechWarriorOnline.exe", before the patcher comes up.

[Marak Varn]

One thing I will add, is that I have had this problem in the past caused by my Firewall. For almost everyone here, that's not the problem this time, but it might be worth just checking connection with your firewall off for a few moments.

Normal user firewall caution recommended of course.

Just some friendly advise. Nothing official.

[Marius Gage]

Server: BThomehub.home
Address: 192.168.1.254

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 23.212.109.168
23.212.109.138
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

I just get "The servers are currenlty undergoing maintenance. Please try agin later"

In the UK, never had an issue before.

also tried flushdns, still doesn't work

Edited by Marius Gage, 15 July 2014 - 01:03 PM.

[Samophlange]

After patching, I changed it back to automatically detect DNS, and it gave me the maintenance message again.

[Vimeous]

Fixed:

If you are changing your ROUTER DNS servers make sure the Google DNS server is the PRIMARY DNS server. (Probably also true for your PC DNS settings)

IF not that change will not work.

nslookup results should look something like:

C:\Windows\system32>nslookup patcher.mwomercs.com
Server: buffalo.setup
Address: <<Your PC Internal IP>>

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 62.255.7.83
62.255.7.66
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

Edited by Vimeous, 15 July 2014 - 01:05 PM.

[Cyphersphere]

From Montreal:

C:\Users\SM1>nslookup patcher.mwomercs.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 184.29.105.80
184.29.105.50
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

================================================

From California:


C:\Users\SM1>nslookup patcher.mwomercs.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 165.254.42.18
165.254.42.33
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

================================================

From Miami:


C:\Users\SM1>nslookup patcher.mwomercs.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 96.17.177.24
96.17.177.25
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

================================================

From New York:


C:\Users\SM1>nslookup patcher.mwomercs.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 184.29.105.50
184.29.105.80
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

Still receive the "unable to connect to remote server" error.

[mechbane]

I changed the DNS to google to patch the game and I was able to play, but after the change I changed back to my paid DNS and now I get the same error on the launcher (launcher wont even open) I change back to google and I can play. (I'm in UK)
im not happy using google and im not sure why I need to I have never seen this before in all the online games iv played and MWO was fine until this patch, come on guys you messed up didn't you?

Edited by mechbane, 15 July 2014 - 01:25 PM.

[TyrEol]

Here's what I get with the local dns resolver on my router / through my ISP

Server: BThomehub.home
Address: 192.168.1.254

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 109.144.113.159
109.144.113.143
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

Here's what I get when using google dns locally from my desktop

Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 23.63.98.26
23.63.98.18
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

Rebooted the router and tried unplugging it to completely power it off, still gives the original result

Server: BThomehub.home
Address: 192.168.1.254

Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 109.144.113.143
109.144.113.159
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net

Edited by TyrEol, 15 July 2014 - 01:16 PM.