275 replies to this topic

[TinFoilHat]

Changing DNS settings has allowed me to patch (UK based). Not sure why this patch was a pain when most others have gone ok, but hey, not gonna complain too much.

[Firebeyer]

Man Devs people will complain about everything... so much hate. Google DNS is going to be far superior to your "Paid For" DNS services from your ISP anyway. You can always set google as your primary DNS and then set your ISP as secondary if you really think your going to miss something oh so special. Also running "ipconfig /flushdns" in your windows command line couldn't hurt things if your still having problems.

Edited by Firebeyer, 15 July 2014 - 11:57 AM.

[C E Dwyer]

Having this glitch myself, still not able to get into the game, though I can launch, world of tanks, Aion, Ever quest 2 Swtor The Secret world but not this, so are you sure its DNS, as surely it would effect all ?

[Smudge504]

changed DNS sorted this out straight away, thanx

[Want0n]

The fix hasn't worked for me. It appears as though BT parental controls are interfering with something. I've turned off the parental controls, but BT are still throwing a hissy-fit for using alternative DNS server settings. Could be the ISP...

[Jon Cunningham]

For those of you *still* having problems post DNS update, hit your start button, type into the run box the letters

CMD

then in the console box that comes up, type ipconfig /flushdns

and hit enter. Let us know if that works.

[LawDawg]

Run Verizon FIOS, Never had this issue, Live in the USA! "MERICA!"

Was there a reason yall changed protocol? Warning would have been nice...........as you can see the issues that have arisen.

[Mcgral18]

Changing the IPv4 fixed it for my client.

[Jon Gotham]

Kyle Polulak, on 15 July 2014 - 11:24 AM, said:

Remember if a Google DNS change results in a 'fix' to your problem then your ISP is to blame not us.

ISP's want to squeeze as much money out of plebeians; one way they do this is by ignoring DNS caching rules and holding onto data to serve to your computer as long as possible to save pennies here and there. They break your experience, not us.

So when we ask you to switch your DNS to fix a problem it doesn't reside on either of our ends; look to your ISP as the culprit.

Kyle, this is not really an appropriate thing to say frankly. I tried the google thing and it worked..but should I have to change DNS settings on my pc to make your game work, when EVERY other game I have works fine? Your game worked fine pre patch yet post patch I'm having to let google have a look at everywhere I go so I can log onto MWO....?

My ISP didn't set out this morning to ruin my mwo experience:)

[Kyle Polulak]

kamiko kross, on 15 July 2014 - 12:06 PM, said:

Kyle, this is not really an appropriate thing to say frankly. I tried the google thing and it worked..but should I have to change DNS settings on my pc to make your game work, when EVERY other game I have works fine? Your game worked fine pre patch yet post patch I'm having to let google have a look at everywhere I go so I can log onto MWO....? My ISP didn't set out this morning to ruin my mwo experience:)

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.

[Jon Cunningham]

Order of steps to take to fix this issue:

1) Hit Start, open or type in the Run prompt the following:

CMD

type

ipconfig /flushdns

hit enter, then retry

2) Try changing your DNS provider following this guide:

https://developers.g...-dns/docs/using

3) If neither works, open a support ticket or post to the forums here with the following info:

a) who your ISP is
approximate location (if you are comfortable sharing it)
c) the results of opening the command prompt and issuing this command: nslookup patcher.mwomercs.com
d) the results of tracert patcher.mwomercs.com


--------------------------

SLDF LawDog, on 15 July 2014 - 11:59 AM, said:

Run Verizon FIOS, Never had this issue, Live in the USA! "MERICA!"

Was there a reason yall changed protocol? Warning would have been nice...........as you can see the issues that have arisen.

We did not change protocol. We use a CDN (akamide) and have for a long time now to deliver patches and content. For whatever reason, either the CDN has failed update the content quickly enough to all possible nodes, or DNS servers have cached an incorrect IP address for our systems. Since you can publicly verify that neither our IP address has changed nor have we changed companies for CDNs....

http://whois.domaint...om/mwomercs.com
http://www.downforev...om/mwomercs.com
https://www.whatsmyd...#A/mwomercs.com

When we know what caused this - and we're not ruling out that it's something stupid we did, we don't know yet - we'll be able to talk about it and apologize if it's appropriate. But right now this bears every sign of being a limited problem caused by DNS servers not updating, or local ISPs breaking down. And our priority is getting this fixed for people, so please don't badger the support staff or the GMs. Let them help people get into the game.

[Arn0ldSchwarzenegger]

Worked for me, not sure why I have to do this but thanks for the rapid workaround

[Jabilo]

"Servers are down for maintenance" for me too.

After every previous patch being available for me instantly since open beta I am reluctant to believe it is entirely the fault of my ISP.

Altering your DNS to Google servers can have both positive and negative effects on your connection (depending on a multitude of factors, though most will not likely notice much difference). In any case I will hang on for a fix.

Edited by Jabilo, 15 July 2014 - 12:22 PM.

[Rebel Roshak]

Also having this issue too.

[Andrius]

Same here. Doing the repair tool thingie right now...

[JesterMWO]

Flush DNS did not work for me but changing DNS to 8.8.8.8 did. I'd have preferred not to have to do that as I've never had an issue connecting to the servers before now...

[Krist Smith]

When we publish a new patch, there are a subset of files that aren't new - they're changed and require a refresh across all the CDN nodes in order for the changes to show up in all locations around the world. Sometimes (very rarely) this refresh doesn't hit all the locations for some reason. One explanation is that it's on the ISP not recognizing a change and not accepting the new version of the file into their cache, and another one is that the CDN node itself didn't get the refresh instruction. We have re-issued the refresh command and, at this point, it's highly unlikely that the same node would have skipped the instruction twice.

We aren't interested in placing blame on any one culprit, we are only interested in explaining what went wrong, fixing it, and creating a plan that avoids having to deal with it again. We aren't saying your ISP sucks or is going out of their way to prevent you from doing anything, but if a caching policy is too conservative and isn't tuned to recognize a changed file, then we are pretty much stuck for a solution (short of re-issuing the refresh command multiple times with our fingers crossed, hoping that at least one of those times the changes will be detected).

I have one particular request to anyone still having this issue - could you please specify if it's happening in the patcher or the game client? At this point, we're assuming it's in the patcher, but if that's incorrect we need to broaden our search.

[GroxGlitch]

I'm in California and had this error, Google DNS change has corrected the issue without requiring a DNS flush. Glad to hear there's some explanation as to what went awry, hopefully this issue doesn't strike again.

At least we know it's not localized to the UK, I suppose. I wonder why it's mainly striking in the UK, though, with lower incidences elsewhere.

EDIT: It struck at the patcher, for the record.

Edited by GroxGlitch, 15 July 2014 - 12:29 PM.

[Andrius]

I don't want to mess with my network settings. I would rather reinstall/redownload the game, i have 80mbps fibre anyway so that would not take very long...

Oh.. It seems like mechwarrior is limited to ~3mbps... Guess it will take a while after all...

Edited by Andrius, 15 July 2014 - 12:36 PM.

[t9nv3]

I'm personally having this issue in the patcher....which I cant even connect to.

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