Connecting Issue


CuppaManga

 

Posted

Whenever i start up CoH, it comes up with the CoH Updater and it says
"ProjectInfo

Connecting.. #1"

I let this go for a while and it just keeps going and going. I've emptied caché, cleared cookies, used terminal to flush it all out, deleted CoH preferences - All the things that usually fix starting up problems.

Nothing's worked!

Running the latest issue of MAC OS X


 

Posted

Yup, seeing the same thing tonight. Startup and "Connecting... #(n)" where n is a number >=1.

I've let it sit and count up to 15 before backgrounding the window and doing other things, coming back to it about an hour later to finally find the button says "Next".

Yet, I move to the older PC and the startup is fine. No delay.

Usually starts up fine on this machine.

System:

Macbook
CPU: 2.26 Ghz
Mem: 2 GB


 

Posted

I also encountered this yesterday. Taking a page from similar recent connectivity problems reported by Windows CoH users, I flushed the DNS cache, which (apparently) cleared things up. From the Terminal, I used dscacheutil -flushcache (I'm using Snow Leopard).


 

Posted

Quote:
Originally Posted by CuppaManga View Post
I'm keeping an eye on this issue - it seems to happen around the same time every night for about an hour. No idea what's causing it yet, but it seems to be some kind of connectivity problem.
You may be on to something about the time...for me, the 6pm EDT hour has been flaky for the last few days. Later, problems seem much rarer. But of course it could all be observer bias after having read your comment.

Time of day not withstanding, I've seen the "connecting" issue about half a dozen times in the last week but only maybe 3 times in the previous 6 months.


Quote of the moment: This, too, shall pass.
Justice superteamers: We have a website now, in case the forums get closed early. If you've ever run with us, come visit us again before the curtain falls. We're running bucket list characters--anything you've always wanted to play but never got around to.

 

Posted

I'm using Verizon DSL, northern Virginia.


Quote of the moment: This, too, shall pass.
Justice superteamers: We have a website now, in case the forums get closed early. If you've ever run with us, come visit us again before the curtain falls. We're running bucket list characters--anything you've always wanted to play but never got around to.

 

Posted

Haven't seen the issue since last reported.

I'm using a local wireless provider.

@TruGentleman, Hmmm.... that could do it... I'll try it if it crops up again.


 

Posted

Definitely having a problem here around 6:55 CST, Comcast network. Reset router and flushed DNS, no dice.


 

Posted

Reset router (Direct Satellite, I think), and flushed dns cache. Not been able to log in since I first attempted at around 9:15. Currently 10:45.


Too many alts to list.

 

Posted

I haven't, because I haven't had the problem since Monday. I wonder if Someone Did Something About It?


Quote of the moment: This, too, shall pass.
Justice superteamers: We have a website now, in case the forums get closed early. If you've ever run with us, come visit us again before the curtain falls. We're running bucket list characters--anything you've always wanted to play but never got around to.

 

Posted

I haven't either, for the same reason: It hasn't reoccurred.


 

Posted

Getting the same thing (Downloaded 10 minutes ago, never opened the game lol)
Time: 9:38 eastern (Massachusetts USA)...this is a fun way to start off a new game, not being able to play it


 

Posted

Okay, the following advice is at the level of "if you have ANY DOUBTS AT ALL, do not try this".

I poked around a bit. The symptom seems to be that a particular machine that is used to check for updates was not responding. So. I firewalled it, and then once the game was past that stage, unfirewalled it.

In my case, that was:

"ipfw add 02070 deny tcp from any to 216.207.250.196 any out"

If you don't know what that means without even checking the manual, or you aren't sure why that command doesn't work, or where to enter it, PLEASE IGNORE THIS POST. This is in the "things you should only do if you are an experienced sysadmin" category.