275 replies to this topic

[Wolfways]

daemur, on 15 July 2014 - 12:21 PM, said:

Do not run the repair tool. It will not solve the problem. Change your DNS or sit tight while we work to address the problem.

Guess I'll have to sit tight then, as all this DNS stuff is like a different language to me

[kazlaton]

The DNS solution worked for me. Thank you for the fix.

[Marak Varn]

Confirming that this is patcher not client. Shuts down before patcher loads.

[TyrEol]

ok well, I was getting this here in the UK too, my ISP is BT if that helps you work out how widely it's affecting UK users.

I could understand some ISPs ignoring caching times on DNS records, but it seems a bit of a coincidence that so many ISPs in the UK suddenly started doing it at once and something didn't get screwed up somewhere.

And why would this never have happened with MWO before now if you already had this system in place?

Changing the primary dns on my PC's connection to google works just fine for patching. But I can't play after I change it back. And I'd like to go back to using BT's/my routers dns servers generally I expect so please don't consider this a "long term" solution (yes the DNS settings on the router are locked down to my ISPs DNS servers at least in the UI).

[Dagada]

same issue:
unable to patch until changing dns server.
location dallas, tx
isp Verizon fios

[Ozric]

Yes confirming this bug too. I tried the repair tool and a reinstall before I found this thread, but now I can't launch the launcher to start the reinstalling process. Le sigh.

[Tipsy McTartan]

I'd been trying to connect for a couple of hours then I disconnected the power to my router for a couple of mins, powered up again and it worked first try.

[Athieros]

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

[Kyle Polulak]

By no means in this a 'long term' solution.

This error is not caused by our code or game files; they are not broken and do not need repair.

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. These are Akamai nodes serving patch content. For an added bonus you can see the different results between your ISP's provided DNS servers and Google's.

[Krist Smith]

Athieros, on 15 July 2014 - 12: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)

[thunderswamp]

I did the dns flush and still get the same thing that the servers are down for maintenance.

pitsburgh PA
verizon

[Ninthshadow]

Just adding my dash to the roster here.

Another UK user suffering the problem on the patcher. Goes straight to 'server is undergoing maintenance' window. Tried solution 1 (FlushDNS) to no effect.

Pedantic as it might sound, not entirely sure/comfortable with solution 2, so pretty sure I'm now in the 'waiting it out' crowd.

[Krist Smith]

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

Well the patcher doesnt even start for me. It's prior to it loading completely. It just displays the MWO logo and after that the error panel. That's about it. No patcher window with server status and play button at all.

That would be the bootstrap patcher. Essentially the same thing (and, specifically, none of the code around this has changed in almost a year in either patcher).

[thunderswamp]

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

Edited by thunderswamp, 15 July 2014 - 12:45 PM.

[Andrius]

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

[t9nv3]

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

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

[Vimeous]

DNS changes can take up to 48hrs to propagate worldwide. Central DNS servers such as those at Google will always update first.

The fact so many of us are having these issues (myself included) is a symptom of how DNS works.

Using your ISP's DNS is not a bad thing - for one leaving your settings on automatic stops you having to change settings every time a DNS server IP changes (rare but it happens). It also means your DNS traffic is initially handled within your own country making DNS response time faster for locally hosted addresses.

If you are using DHCP at home your router is providing your PC its DNS which is in turn gets it from the ISP.
So if you want everyone in the house to use Google DNS it's better to change the router DNS then use ipconfig /flushdns at the command prompt at each PC as described previously.

NB
If your router uses 2 dns servers leave 1 pointing at your ISP and make a record of the one you change so you can switch it back later.

Edited by Vimeous, 15 July 2014 - 12:49 PM.

[Bobzilla]

I fixed it with changing the DNS. Flush didn't work.

I'm in Halifax N.S. so it can effect Canadians too.

[Marak Varn]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\User>nslookup patcher.mwomercs.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100

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


C:\Documents and Settings\User>

[Jon Gotham]

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

Your opinion doesn't help anything. We use DNS to issue different servers addresses to people in different geographical locations; other games tend to use multi-homed setups that do not rely on DNS they also don't allow people from Europe to play on their North American servers. Changing the DNS helps because Google's DNS respects the DNS specifications purely and will update correctly. Once you've patched you may switch your DNS back to it's original value. You computer should keep the correct addresses and cache rules from Google's DNS.

You'll notice this bug outside of MWO if you have pages that load without styles, or sometimes webpages don't load for you but would load on your phone. This happens more often in smaller populated areas with ISP struggling to share a smaller pipe with more users.

Fair enough, ty for the reply.