MAC: Still can't login?

[jeeptj]

SAME HERE....

Guess I picked a bad day to a re-sub to WWII Online.

Things haven't changed much since the good old days.... has it?

Login host take you to "Finding Best Connection" HANGS then DISCONNECTS

[vstrider]

Groog - I had the same issue...Stalls at "Finding...." then kicked me out the first several times I tried to log-in.

Then one time after a full re-install it stalled at "Finding..." then POOF, I'm in the game.

Now I find I'm back into the kicked out after a long "Finding..." session.

Didn't work one day, worked for the next week...now back to not working.

Any ideas?

[marcus]

So far for me it goes between 2-10 tries until the game finds the connection.

Maybe OS might be an issue for those that never manage, I'm on 10.6, can we get some 10.7 users to post if they manage to log in?

[tiborg]

Running 10.7, having no login issues.

[delems]

It was this last patch; I've been working fine in regards to logging on, CTDs and even cell hosts. Very few. Yes, I get the chat host; but everyone gets those. Then, right before break they posted a new patch and now I can't log in.

However, if I keep trying I usually get in before I give up. Longest was 29 tries, average seems about 15. So, they changed something with logging in.

Amazes me they could break the login code.

[marcus]

Any other 10.7 users NOT having the connection bug issue ?

[dog3]

Any other 10.7 users NOT having the connection bug issue ?

I'm using 10.7.2, ping to ww2ol.playnet.com is about 40ms, no problem logging in.

[macalex]

I run 10.7 and have the connection issue. Usually in after 4 or 5 times though.

[avionyx]

Im on 10.7.2 and always in first time BUT it takes a good 5 minutes for it to connect.

[jeeptj]

I'm on 10.7.2 and it takes about 10 to 15 times to log on.

I got an email from Xoom saying that everyone's on vacation.

You'd think.... think.... that they'd test the connection before taking off.

I'll be asking for extra time on my subscription - for sure!!

Sorry to hear there has been some trouble with the game for you. I have copied our Community Manager (MOTORMOUTH) and our Customer Support Rep (BLOO) to this message to better assist you.

Please know that the Office is closed and they are on vacation, so their response is on their personal time and may be delayed.

Thank you for your patience, and I appreciate you reaching out to support us.

[montyuno]

Can you hear me Major Tom ? ? ?

Krackle fizzz zzz krackle fizzz..

Major Tom... ? ?

Fizzip krackle krackle fizz fizzzz ...

Is there anyone out there.. ? Do you copy ? ?

Krackle krackle fizzzzip fizzz zzz krackle...

.....

Cheers Montyuno

[jeeptj]

Last time, I got lucky.... I only had to try it 23 times before it connected.

Hadn't had the patience to do it today for more than 15 times.

Still won't connect.

[kozzman]

Its the same here sometimes it take only a couple of times to log on others its a no go. How about a little support here. Just let us know your working on it. If not just let us know and I can move on to a different game. I have been playing this game since it first came out. Now that I am using a MAC the support gets less and less. Please fix it.

[toyota]

I believe that only os X 10.7 can log in...right?

Or is that just a question of time and ... time?

[jeeptj]

Xoom says that the patch done and then the office took off for Christmas Vacation!

That's not a smart thing to do without testing it.

Rule #1. Test, test, and test again for verification.

Even when I'm on vacation from the job, I'm required to check my email.

Both Motormouth and Bloo have received emails about the launch problems.

Ignoring the users = losing game players (revenue).

10.7.2 (Lion) isn't the problem. Before the patch - the game would load fine.

Customer Support owes us Macintosh Users additional time on our subscriptions. As a Day 1 subscriber and remembering the terrible first weeks of this game, this problem of the "Finding Best Connection" mirrors those horrible times.

[bloo]

We're very sorry about this problem.

Find best connection simply sends pings down our two possible connection paths and then selects the best one. But this sounds like something is preventing that a lot of the time for some Macs.

It might help to see traceroutes. You can trace a route to our servers by opening a Terminal and entering:

traceroute 66.28.224.141

traceroute 209.144.109.141

[delems]

My last 5 times of logging onto the game has taken 3, 17, 5, 18 and 11 tries. I have never had this problem until the last patch, always could log on with first try.

Traceroutes:

traceroute to 66.28.224.141 (66.28.224.141), 64 hops max, 52 byte packets

1 wireless_broadband_router (192.168.1.1) 0.685 ms 0.336 ms 0.250 ms

2 l100.plspca-vfttp-10.verizon-gni.net (108.43.131.1) 5.400 ms 5.194 ms 4.778 ms

3 g2-0-2-110.plspca-lcr-01.verizon-gni.net (130.81.54.248) 4.895 ms 5.938 ms 5.811 ms

4 130.81.199.46 (130.81.199.46) 9.075 ms 34.197 ms 9.487 ms

5 0.ae1.br1.lax15.br1.lax15.alter.net (152.63.112.1) 19.992 ms 9.343 ms 10.109 ms

6 te7-2.ccr02.lax05.atlas.cogentco.com (154.54.13.85) 9.119 ms 9.825 ms 10.213 ms

7 te0-0-0-2.mpd22.lax01.atlas.cogentco.com (154.54.6.229) 9.779 ms

te0-1-0-1.mpd22.lax01.atlas.cogentco.com (154.54.3.9) 9.722 ms

te0-1-0-1.ccr22.lax01.atlas.cogentco.com (130.117.50.89) 9.676 ms

8 te0-0-0-5.ccr22.iah01.atlas.cogentco.com (154.54.5.193) 49.104 ms

te0-1-0-6.mpd22.iah01.atlas.cogentco.com (154.54.0.246) 49.969 ms

te0-0-0-5.mpd22.iah01.atlas.cogentco.com (154.54.0.242) 49.901 ms

9 te0-4-0-6.ccr22.dfw01.atlas.cogentco.com (154.54.0.206) 50.619 ms

te0-2-0-1.ccr22.dfw01.atlas.cogentco.com (154.54.25.97) 49.767 ms

te0-3-0-5.ccr22.dfw01.atlas.cogentco.com (154.54.24.26) 50.790 ms

10 te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 51.055 ms 48.912 ms 48.966 ms

11 playnet.demarc.cogentco.com (66.28.30.146) 51.742 ms !X * 49.775 ms !X

traceroute to 209.144.109.141 (209.144.109.141), 64 hops max, 52 byte packets

1 wireless_broadband_router (192.168.1.1) 63.786 ms 0.290 ms 0.207 ms

2 l100.plspca-vfttp-10.verizon-gni.net (108.43.131.1) 3.866 ms 4.381 ms 5.380 ms

3 g2-0-2-110.plspca-lcr-01.verizon-gni.net (130.81.54.248) 5.724 ms 5.354 ms 5.013 ms

4 130.81.199.46 (130.81.199.46) 9.092 ms 9.679 ms 9.766 ms

5 0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133) 8.744 ms 8.917 ms 9.625 ms

6 0.so-5-2-0.xt1.lax7.alter.net (152.63.1.225) 9.632 ms 8.930 ms

0.xe-3-1-1.xt1.lax7.alter.net (152.63.114.65) 9.019 ms

7 pos6-0.br2.lax7.alter.net (152.63.112.145) 10.515 ms 9.945 ms 10.245 ms

8 dcr2-so-5-2-0.losangeles.savvis.net (208.172.44.193) 27.853 ms 10.993 ms 11.486 ms

9 cr1-pos-0-0-0-0.dallas.savvis.net (204.70.192.85) 44.329 ms 45.172 ms 45.942 ms

10 bcr1-so0-0-0.dallas.savvis.net (204.70.193.9) 46.492 ms 44.693 ms 46.367 ms

11 t35494-2.savvis-internet.usdlls2-j20c.savvis.net (216.90.2.250) 45.497 ms !X * 45.662 ms !X

[ratatosk]

Are you sure about those IPs, BLOO? I haven't had connection issues and ran them out of boredom with the results below- the strange part is I can get into the game fine.

C:\Windows\System32>tracert 66.28.224.141

Tracing route to 66-28-224-141.playnet.com [66.28.224.141]

over a maximum of 30 hops:

1 1 ms 1 ms 2 ms homeportal.gateway.2wire.net [172.16.0.1]

2 13 ms 13 ms 13 ms 70.159.160.95

3 15 ms 15 ms 15 ms 70.159.178.85

4 15 ms 15 ms 15 ms 70.159.178.43

5 16 ms 15 ms 15 ms 12.81.16.90

6 15 ms 15 ms 15 ms 12.81.16.7

7 14 ms 15 ms 15 ms 74.175.192.230

8 18 ms 17 ms 21 ms cr2.attga.ip.att.net [12.122.140.186]

9 16 ms 15 ms 15 ms attga02jt.ip.att.net [12.123.22.153]

10 37 ms 37 ms 36 ms 192.205.36.238

11 50 ms 50 ms 50 ms te0-0-0-1.ccr21.atl01.atlas.cogentco.com [154.54

.0.165]

12 50 ms 50 ms 50 ms te0-1-0-2.ccr21.iah01.atlas.cogentco.com [154.54

.2.82]

13 51 ms 50 ms 50 ms te0-4-0-6.ccr21.dfw01.atlas.cogentco.com [154.54

.0.138]

14 49 ms 50 ms 50 ms te4-2.ccr01.dfw02.atlas.cogentco.com [154.54.26.

162]

15 Playnet.demarc.cogentco.com [66.28.30.146] reports: Destination net unreac

hable.

Trace complete.

C:\Windows\System32>tracert 209.144.109.141

Tracing route to 209.144.109.141 over a maximum of 30 hops

1 1 ms 1 ms 1 ms homeportal.gateway.2wire.net [172.16.0.1]

2 13 ms 13 ms 13 ms 70.159.160.95

3 16 ms 13 ms 15 ms 70.159.178.85

4 15 ms 15 ms 15 ms 70.159.178.41

5 15 ms 15 ms 15 ms 12.81.16.90

6 12 ms 15 ms 31 ms 12.81.16.19

7 14 ms 15 ms 15 ms 74.175.192.74

8 20 ms 19 ms 19 ms cr1.attga.ip.att.net [12.122.141.186]

9 15 ms 15 ms 15 ms attga03jt.ip.att.net [12.122.84.41]

10 15 ms 15 ms 15 ms 208.173.60.237

11 17 ms 17 ms 15 ms cr2-te-0-0-0-0.atlanta.savvis.net [204.70.200.2]

12 36 ms 35 ms 37 ms cr2-pos-0-3-0-0.dallas.savvis.net [204.70.192.70

]

13 162 ms 234 ms 204 ms bcr1-so5-0-0.dallas.savvis.net [204.70.198.110]

14 t35494-2.savvis-internet.usdlls2-j20c.savvis.net [216.90.2.250] reports: D

estination net unreachable.

Trace complete.

[delems]

Just realized those are not the IPs my system is looking at, note the different IP numbers:

12/29/11 3:34:12 PM [0x0-0x78078].com.playnet.ww2ol[619] WW2OL Started

12/29/11 3:34:58 PM [0x0-0x78078].com.playnet.ww2ol[619] Wed Dec 31 22:17:33 1969 network election of 2 addresses: 66.28.224.143:FAILED. 209.144.109.143:FAILED. *** ELECTION FAILED - NO NETWORK ***

12/29/11 3:34:58 PM [0x0-0x78078].com.playnet.ww2ol[619] NETWORK ERROR: Unable to complete network selectionExited Program: file: /Users/ahwulf/ww2ol/1.34/WW2/src/rn/rnmain.cpp, line: 410, App Version: 1.34.6

12/29/11 3:34:58 PM [0x0-0x78078].com.playnet.ww2ol[619] Message string: Unable to complete network selection

12/29/11 3:34:58 PM [0x0-0x78078].com.playnet.ww2ol[619] Exited Program: file: /Users/ahwulf/ww2ol/1.34/WW2/src/rn/rnmain.cpp, line: 410, App Version: 1.34.6

12/29/11 3:34:58 PM [0x0-0x78078].com.playnet.ww2ol[619] Message string: Unable to complete network selection

[delems]

Well, another 25 tries and still can't logon. Pretty sad. It's one thing to play a game that has some bugs to it. It's entirely different when you can't even log on to said game.

Pretty unbelievable you can sit at home while your users can't log in at all, or only with multiple repeated attempts. Not going to write anything else, because it would be very unkind. Not happy.

[jeeptj]

traceroute 66.28.224.141

traceroute to 66.28.224.141 (66.28.224.141), 64 hops max, 52 byte packets

1 homeportal (192.168.1.254) 3.401 ms 2.539 ms 2.340 ms

2 99-1-216-2.lightspeed.tukrga.sbcglobal.net (99.1.216.2) 26.753 ms 26.523 ms 26.192 ms

3 76.201.208.40 (76.201.208.40) 28.695 ms 28.023 ms 26.625 ms

4 * * 76.201.208.14 (76.201.208.14) 29.302 ms

5 70.159.177.168 (70.159.177.168) 26.799 ms

70.159.178.24 (70.159.178.24) 29.368 ms

70.159.177.168 (70.159.177.168) 27.668 ms

6 12.81.0.34 (12.81.0.34) 29.335 ms

12.81.0.4 (12.81.0.4) 28.298 ms

12.81.0.82 (12.81.0.82) 29.723 ms

7 12.81.0.101 (12.81.0.101) 29.426 ms 28.452 ms 26.930 ms

8 74.175.192.114 (74.175.192.114) 28.838 ms 118.848 ms 74.465 ms

9 cr2.attga.ip.att.net (12.122.140.170) 31.048 ms 31.185 ms

cr1.attga.ip.att.net (12.122.117.26) 31.655 ms

10 attga02jt.ip.att.net (12.123.22.153) 29.630 ms

attga02jt.ip.att.net (12.123.22.25) 28.952 ms 28.216 ms

11 * * 192.205.36.238 (192.205.36.238) 46.364 ms

12 te0-0-0-1.ccr21.atl01.atlas.cogentco.com (154.54.0.165) 62.999 ms

te0-0-0-1.ccr22.atl01.atlas.cogentco.com (154.54.0.161) 63.229 ms

te0-0-0-1.mpd21.atl01.atlas.cogentco.com (154.54.40.249) 63.714 ms

13 te0-2-0-7.mpd22.iah01.atlas.cogentco.com (154.54.42.221) 63.412 ms

te0-2-0-1.ccr21.iah01.atlas.cogentco.com (154.54.29.6) 63.919 ms

te0-0-0-6.ccr22.iah01.atlas.cogentco.com (154.54.24.22) 63.760 ms

14 te0-3-0-2.ccr21.dfw01.atlas.cogentco.com (154.54.2.206) 62.907 ms

te0-0-0-1.ccr22.dfw01.atlas.cogentco.com (154.54.25.221) 65.112 ms

te0-1-0-5.ccr22.dfw01.atlas.cogentco.com (154.54.5.137) 63.827 ms

15 te4-2.ccr01.dfw02.atlas.cogentco.com (154.54.26.162) 63.383 ms

te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 64.280 ms

te4-2.ccr01.dfw02.atlas.cogentco.com (154.54.26.162) 64.007 ms

16 playnet.demarc.cogentco.com (66.28.30.146) 63.703 ms !X * 63.486 ms !X

traceroute 209.144.109.141

traceroute to 209.144.109.141 (209.144.109.141), 64 hops max, 52 byte packets

1 homeportal (192.168.1.254) 2.847 ms 2.703 ms 2.381 ms

2 99-1-216-2.lightspeed.tukrga.sbcglobal.net (99.1.216.2) 26.670 ms 27.012 ms 25.298 ms

3 76.201.208.40 (76.201.208.40) 28.490 ms 27.010 ms 27.432 ms

4 * * *

5 70.159.177.168 (70.159.177.168) 26.880 ms

70.159.178.24 (70.159.178.24) 28.406 ms

70.159.177.168 (70.159.177.168) 26.384 ms

6 12.81.0.0 (12.81.0.0) 29.571 ms

12.81.0.70 (12.81.0.70) 39.716 ms

12.81.0.66 (12.81.0.66) 30.965 ms

7 12.81.0.101 (12.81.0.101) 28.551 ms 27.222 ms 27.204 ms

8 74.175.192.210 (74.175.192.210) 29.564 ms 27.752 ms 28.119 ms

9 cr1.attga.ip.att.net (12.122.117.26) 32.351 ms 31.336 ms

cr2.attga.ip.att.net (12.122.140.170) 31.401 ms

10 attga03jt.ip.att.net (12.122.84.21) 77.449 ms

attga03jt.ip.att.net (12.122.84.41) 28.580 ms 28.716 ms

11 208.173.60.237 (208.173.60.237) 29.765 ms 28.270 ms 28.246 ms

12 cr2-te-0-0-0-0.atlanta.savvis.net (204.70.200.2) 30.481 ms 27.901 ms 31.739 ms

13 cr1-tengig0-7-0-0.dallas.savvis.net (204.70.196.213) 49.409 ms 48.150 ms 47.569 ms

14 bcr1-so0-0-0.dallas.savvis.net (204.70.193.9) 47.658 ms 46.449 ms 47.597 ms

15 t35494-2.savvis-internet.usdlls2-j20c.savvis.net (216.90.2.250) 48.790 ms !X * 47.532 ms !X

[thorpug]

bump

[jeeptj]

bump

[jeeptj]

Still can't log in.

What is being done to fix the problem?

????

[stankyus]

No problem the other day getting in, now cant..... ugggg... so the best solution is to keep doing it.