connecting.. #8

So i'm sure most of you are familiar with this message. I was able to connect yesterday no problem, today, I can not.

I'm running win7 pro 64 bit.
i7 920 (stock)
3x1G ram
ati 4870

hmm connected at about #12 closed then reopened and connected first try. anyone know why that may have happened. I'm glad it's working but magic and luck is not something i want to rely on forever.

Try out the network troubleshooting tool http://help.ncsoft.com/cgi-bin/ncsof...p_sid=KAXfW6_j.

We've been saving Paragon City for eight and a half years. It's time to do it one more time.

I'm getting this too. And I'm on OSX, so a windows network tool won't do me any good. Got up to #22 before giving up. Have tried rebooting (which.. should never really matter on OSX) and no luck.

This is happening to me right now. It wasn't earlier today, and my spouse is logged in successfully, but I can't connect. Pinging the server in question does indeed show it to be non-responsive. It's 216.107.250.196, or at least, that's the server I've got an open connection to in SYN_SENT, and it has the plausible name "216-107-250-196.plaync.com". So if that's the machine, well, it's offline. I'm assuming I don't actually need any updates, having updated an hour ago.

ETA: Set firewall to reject packets to that host, updater failed gracefully and now I'm playing. Removed firewall rule in case of future updates.

Same problem, I'm connecting through AT&T dsl in Ohio.

tracert to 216.107.250.196 shows the following if it's any help

Tracing route to 216-107-250-196.plaync.com [216.107.250.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 2 ms 3 ms 192.168.0.1
3 9 ms 12 ms 8 ms adsl-75-33-47-254.dsl.bcvloh.sbcglobal.net [75.33.47.254]
4 9 ms 8 ms 18 ms dist1-vlan62.bcvloh.sbcglobal.net [76.222.39.129]
5 10 ms 9 ms 11 ms bb1-g4-2-0.bcvloh.sbcglobal.net [151.164.43.152]
6 17 ms 17 ms 17 ms 151.164.99.105
7 17 ms 24 ms 24 ms as22822-llnw.eqchil.sbcglobal.net [151.164.250.170]
8 40 ms 33 ms 41 ms tge16-2.fr3.lga.llnw.net [68.142.125.46]
9 55 ms 45 ms 34 ms tge13-1.fr3.iad.llnw.net [69.28.189.30]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * *

**Edit**
tried again later and connected at try #8, but still I don't normally see the "connecting attemp #" at all

Had the same problem here. After logging out after playing for a hour or so earlier today the wife and I both find we can't log back in again.

Both our systems are Windows 7 Ultimate, Norton 360 security with different video cards. I tried deleting the firewall rule for CoH off Nortons as that has helped with some connection errors in the past but no joy this time.

Then I restarted my router and then I could reconnect. I've no idea why but it seemed to fix it.

Just a quick work-around whenever you're having problems with the updater and there is not a new update out. These commands will manually start the game skipping the updater. If there's a new patch that you haven't installed, you will be unable to login. Don't get into a habit of using these commands instead of the Updater.

On Windows 32bit, press Win+R on your keyboard, and type the following into the Run dialog:
C:\Program Files\City of Heroes\cityofheroes.exe -project coh

On Windows 64bit, press Win+R on your keyboard, and type the following into the Run dialog:
C:\Program Files (x86)\City of Heroes\cityofheroes.exe -project coh


You could also make a new shortcut, and point it to:
32bit: "C:\Program Files\City of Heroes\cityofheroes.exe" -project coh
64bit: "C:\Program Files (x86)\City of Heroes\cityofheroes.exe" -project coh

Make sure you use the correct version, and adjust the path if you installed CoX into a non-default location.

---

On OS X (from the Terminal, or a shortcut-thingy-linker-thing-a-ma-bobber):
/Applications/City\ of\ Heroes.app/Contents/MacOS/cider --use-dos-cwd c:/coh -- c:/coh/cityofheroes.exe -project coh

We've been saving Paragon City for eight and a half years. It's time to do it one more time.