Jump to content

Error 67, Downloaded Hot Fix, Client Wont Launch


25 replies to this topic

#21 topgun505

    Member

  • PipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 1,625 posts
  • Facebook: Link
  • LocationOhio

Posted 25 May 2016 - 06:42 PM

I played 2 or 3 games ok this evening and then suddenly I disconnected and have not been able to reconnect since, despite rebooting the router, pc, flushing dns.

Did a speed test and my internet is a little slower than normal 25 Mps instead of 30 but is otherwise fine. I can successfully tracert to mwomercs.com and I can log in to the website so I know my account is active and password is working. I ran the repair tool and it came back normal.

I put in a support ticket and got a response within the hour that they have gotten a number of other similar problems and most all of them have either Comcast or TWC as the ISP being used so they suspect the ISP is to blame.

I have to question this considering I can tracert all the way to PGI servers and I can get to all websites I normally do ... but I've exhausted all my options here short of reinstalling.

#22 Sojourner Crim

    Rookie

  • Bad Company
  • Bad Company
  • 9 posts

Posted 25 May 2016 - 07:08 PM

View PostPoorDecisions, on 25 May 2016 - 05:49 PM, said:


I sent in an email to the address listed including a traceroute.

View PostDaoa Hakoke, on 25 May 2016 - 05:59 PM, said:

I have sent an email as well reporting the issue as well. Hope it gets fixed quickly.


I have also sent this. I am on AT&T U-Verse (definitely not TWC)

#23 Zordicron

    Member

  • PipPipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 2,547 posts

Posted 25 May 2016 - 08:47 PM

I did a trace route to the server, and it managed a normal test right up till the last hop, where it timed out.

I am on a Frontier DSL line.

This has pushed me to pull the trigger on the Steam client. With my horrid Frontiernet, where they throttle this type of download, it will take until tomorrow night to finish most likely. However, despite that, just the automatic updates will be convenient enough to justify it after this debacle tonight. I mean, if I can;t play anyway i might as well just concede the downtime and get something useful going in the meantime.

I suspect severe hax attax from China/Russia to be responsible for ruining my fun tonight, but that is pure speculation, and even if true will never be confirmed officially.

#24 PoorDecisions

    Member

  • PipPipPipPipPip
  • Bad Company
  • Bad Company
  • 124 posts
  • LocationOregon, USA

Posted 25 May 2016 - 10:05 PM

View PostZordicron, on 25 May 2016 - 08:47 PM, said:

I did a trace route to the server, and it managed a normal test right up till the last hop, where it timed out.

I am on a Frontier DSL line.

This has pushed me to pull the trigger on the Steam client. With my horrid Frontiernet, where they throttle this type of download, it will take until tomorrow night to finish most likely. However, despite that, just the automatic updates will be convenient enough to justify it after this debacle tonight. I mean, if I can;t play anyway i might as well just concede the downtime and get something useful going in the meantime.

I suspect severe hax attax from China/Russia to be responsible for ruining my fun tonight, but that is pure speculation, and even if true will never be confirmed officially.


I have Frontier (FIOS) and they don't throttle me. :P

If you followed Alex's instructions earlier, you would have received a reply to your email with specific instructions on what IP to ping and a different IP to traceroute to which you should have sent in to PGI like they asked. :)

#25 Chimera_

    Member

  • PipPipPipPipPipPip
  • CS 2024 Gold Champ
  • CS 2024 Gold Champ
  • 446 posts
  • LocationOregon

Posted 25 May 2016 - 10:18 PM

Was able to get on a few hours ago and do a bunch of CW matches just fine - seems fixed, for me at least.

I'm on Frontier (Fiber) in Oregon.

#26 Zordicron

    Member

  • PipPipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 2,547 posts

Posted 26 May 2016 - 03:10 PM

View PostPoorDecisions, on 25 May 2016 - 10:05 PM, said:


I have Frontier (FIOS) and they don't throttle me. Posted Image

If you followed Alex's instructions earlier, you would have received a reply to your email with specific instructions on what IP to ping and a different IP to traceroute to which you should have sent in to PGI like they asked. Posted Image

Well, good for you. I pay 110 bucks a month for 4mb/sec and get 100-250k on anything besides "contract" things like netflix. I get, and I am not kidding, less then 100K upload speeds on average. Ookla speed test rates my connection a "F" and depending on which test I look at the results for over the last two year, rates the connection anywhere from 4% to 10% of the worst connections on the planet

Recently, they did some upgrade work at my local hub, so now I only get 200MS ping on traceroute to their main hub 50 miles from my driveway instead of 300.

My lines are copper, and were buried in the early 80's. I should post a picture of my junction box... well actually it's not even a box, its this giant tube looking thing from 1973, that is still attached to the original telephone line wooden pole(they cut it off about 7 feet tall and moved the junction down) in the corner of my yard.

So yeah, my stuff gets throttled, though they deny it, because well frankly they have to because they oversold the network in my little town so hardcore there is just no F'ing way the copper land lines from 40 years ago can handle the traffic otherwise.

I would love a FIOS.... hell I would love a low end cable connection. Only reason I haven't gone to a dish system is the ping is even worse for gaming on there. Someday a competitor will notice Frontier making MINT on my little town and move in, OR, the FCC will be allowed to actually have some clout against ISP's, OR, there will be a class action lawsuit from my town the next time they try to raise the rates.

Anyway, I didn;t do what they requested because, as I stated earlier, last time this happened I just gave it some time and the issues went away, because indeed, it is an ISP related issue. It did indeed go away, as today I can log in without issue. I just did the trace to see if it would get dropped somewhere in between the server or not, or if there was just a real obvious "bad hop".

edit: on a related note:

http://arstechnica.c...t-top-box-plan/

Edited by Zordicron, 26 May 2016 - 03:17 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users