"Connecting #X..."

There seems to be a glitch on the European servers that the updater isn't working, and just cycles through the "Connecting #X" text. Is anyone else getting this?

Try this from the tech forums

Yeah, I've given it a go already, thanks though.

It's become quite common since the server move to the US. It's likely down to your ISP's routing table sending you down a poor route to the servers

Getting this the last few days as well. Usually have to quit retry quit retry for 5-10 mins , eventually works.

Will try that techie tip when i get home from work tonight.

Wish I'd known this before I reinstalled CoH.

Apparently though it's not helping and I can't access still.

Has anyone contacted Av or the techies?

Am also experiencing the hang time before updater connects, although if I try the test server it works perfectly?

This happens to me regularly but it has been happening more since the move to the US along with increased rubberbanding when I do get in. The flushdns trick works once in a blue moon but most of the time it's time to stick the kettle on while the downloader tries to connect. I'm trying the shortcut idea but for some reason, the route in the target box is 'invalid'. Ho hum.

I wouldn't mind so much if I hadn't of crashed out of an ITF last night and spent half an hour trying to get back on.

This has been happening to me a lot recently, I find a combination of, ipconfig /release ipconfig /renew, restarting the router and / or PC and lots of swearing and sacrificing of first borns gets it working again

Yeah, I'm getting it too. It's intermitant, but I got up to "connecting #34" before giving up just now.

Also, I'm running Windows 7.

I've reported it to the Devs and all the questions I'm getting are trying to make it seem as if its my fault, I also said to check on the forums as I pointed out it was not just me, the answer was "what forums?".

So far I've been directed to use two different bits of software to see where MY problem lies, one of which costs 40 bucks which I am not going to pay as I believe its quite simply down to them and is quite probably due to the move to the states.

After a week of useless help from TechSupport I'm now getting a bit fed up with it all, as they don't seem to be taking use Euroserver users seriously enough.

Moan over and back to TechSupport now as after playing this afternoon, I logged out whilst my wife stayed AFK. She's still logged in whilst I cannot connect to the update server yet again. Maybe my suggestion that its down to traffic volumes through the update server is correct after all.

Yeah, the only thing that works for me is skipping the updater when it gets tetchy. Not ideal, but it works, I suppose.

I didn't realise this was such a widespread issue...

Flushing your DNS cache won't do anything unless the DNS server you're currently telling your computer to use has a valid entry for the address you're trying to talk to.

Usually your PC uses your router as its primary DNS server, which in turn uses a DNS server provided by your ISP. DNS Servers don't update their records immediately with new information whenever stuff on the network they're connected to changes. The time between updates on DNS Servers provided by different ISPs can vary, but when you start getting this problem it will likely persist for at least a week (assuming that they catch the error and fix it fairly quickly)

Change your Primary DNS Server setting to something different, and you will use a completely different set of lookup tables immediately (after a /flushdns) to talk to the CoH servers and this problem will likely go away.

Quoting myself from another thread -

All I do is exit and try again, I have been stuck on the loop a few times but it seems, for me, that closing the updater and starting it again works.

Fury

For those of you still encountering this issue regularly, could you PM me the name of your ISP and your tracert to cohupdateeu.coh.com?

Thank you!

Have not encountered the problem again since the update to I19.

My SG-mate's getting a similar but different problem.

She's in Britain but we play on the US servers. I'm in Poland. I can login to our main server, Freedom, no problem. She, however, gets a 'no response from this server. Please try another server or try this one again later' message when she tries to login. The updater works for her, everythings cool until it comes to server select.

I've asked for advice in the Tech forum to no avail yet. Any advice?

Eco.

Quote:

Originally Posted by Samuel_Tow [The Incarnate System is] Jack Emmert all over again, only this time it's not "1 hero = 3 white minions" it's "1 hero = 3 white rocks."

I had these problems not long after the eu servers underwent the migration, flushing the dns didn't help but resetting my router did the trick. Post I19 I haven't needed to do that at all so far.

Gets this problem a lot.
Hope we get it solved. Weird thing it happened a few weeks after the server move. Now not one night/session goes by that I do not see the "connecting...".

Oh Avatea, will do, when I remember how to get the info you requested

I've been having this issue for the past couple of weeks but tonight it's finally fallen over for good. No amount of rebooting of PC or router is working.

Quote:

Originally Posted by Avatea For those of you still encountering this issue regularly, could you PM me the name of your ISP and your tracert to cohupdateeu.coh.com? Thank you!

I can do the first but could someone explain the second so I can send a report? Thanks!

Get me your tracert reports and I'll forward to our engineers. That's the first thing I mentioned yesterday but we're still looking into getting it resolved.

Lovely thank you, I will do that.

Thanks for looking into it Avatea.