Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

RATs! Seconday connection route dead?


OLDZEKE
 Share

Recommended Posts

  • Registered Users

Myself and at least on other squaddie can't connect via secondary connection route. Just started today. May want to check it.

Link to comment
Share on other sites

had to change to "Use Primary Connex" while it took forever and threw a tcp error at start it finally got me in... not sure if related, but the ts server seems a bit garbally too.

Link to comment
Share on other sites

change your connect settings to say "use best" ... do not select "secondary" as a hard choice

alternatively "use primary" will also work but it is recommended as a fall back if "use best" does not work

Edited by DOC
Link to comment
Share on other sites

Added to this a lot of folks were experiencing much higher ping results which made for rather interesting gameplay in towns.

As an example from where I am atm (NY) ping is usually in the 50ms level and today it was up at mid 90's.

Could this be related?

Link to comment
Share on other sites

I am seeing high ping latency from here in Northern California, checking into my other remote servers I have access to I see normal 40-60ms ping rates. I am pretty sure this is not related to our server network, will begin checking things out.

Link to comment
Share on other sites

Still not the only one thats getting it, certainly not in squad.

Have tried all connection variables in settings to no avail.

Have done a few ping tests averages as below.

Ping Tests - Averages

66.28.224.227 is timing out.

66.28.224.142 average ping is 97

66.28.224.144 average ping is 95

Tracerts

66.28.224.227 Timing out.

66.28.224.142

Tracing route to 66-28-224-142.playnet.com [66.28.224.142]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]

2 6 ms 6 ms 7 ms L100.NWRKNJ-VFTTP-163.verizon-gni.net [108.35.14

.1]

3 8 ms 12 ms 11 ms G0-3-4-4.NWRKNJ-LCR-22.verizon-gni.net [130.81.1

80.194]

4 23 ms 14 ms 10 ms xe-2-1-4-0.NWRK-BB-RTR2.verizon-gni.net [130.81.

199.194]

5 13 ms 14 ms 14 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]

6 93 ms 97 ms 93 ms 204.255.168.110

7 95 ms 94 ms 97 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47

.57]

8 93 ms 97 ms 94 ms te0-4-0-2.mpd21.dca01.atlas.cogentco.com [154.54

.42.33]

9 98 ms 92 ms 89 ms te0-3-0-7.mpd22.atl01.atlas.cogentco.com [154.54

.27.98]

10 95 ms 94 ms 95 ms te0-0-0-1.ccr22.iah01.atlas.cogentco.com [154.54

.5.94]

11 93 ms 94 ms 94 ms te0-2-0-1.ccr21.dfw01.atlas.cogentco.com [154.54

.2.14]

12 91 ms 89 ms 90 ms te4-2.ccr01.dfw02.atlas.cogentco.com [154.54.26.

162]

13 89 ms 92 ms 96 ms Playnet.demarc.cogentco.com [66.28.30.146]

14 93 ms 97 ms 94 ms 66-28-224-142.playnet.com [66.28.224.142]

Trace complete.

Tracing route to 66-28-224-144.playnet.com [66.28.224.144]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]

2 8 ms 6 ms 7 ms L100.NWRKNJ-VFTTP-163.verizon-gni.net [108.35.14

.1]

3 11 ms 11 ms 12 ms G0-14-2-7.NWRKNJ-LCR-22.verizon-gni.net [130.81.

189.118]

4 9 ms 9 ms 12 ms so-4-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.

22.64]

5 11 ms 12 ms 12 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]

6 96 ms 92 ms 89 ms 204.255.168.114

7 83 ms 84 ms 86 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31

.9]

8 92 ms 95 ms 91 ms te0-4-0-2.ccr21.dca01.atlas.cogentco.com [154.54

.42.17]

9 93 ms 91 ms 87 ms te0-2-0-6.mpd22.atl01.atlas.cogentco.com [154.54

.28.234]

10 87 ms 90 ms 92 ms te0-2-0-7.ccr22.iah01.atlas.cogentco.com [154.54

.42.213]

11 91 ms 90 ms 84 ms te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54

.25.97]

12 90 ms 91 ms 94 ms te4-4.ccr01.dfw02.atlas.cogentco.com [154.54.26.

34]

13 91 ms 92 ms 87 ms Playnet.demarc.cogentco.com [66.28.30.146]

14 95 ms 89 ms 86 ms 66-28-224-144.playnet.com [66.28.224.144]

Trace complete.

Hope this helps.

Edited by expatpom
Link to comment
Share on other sites

Those are good ping times, I'm around 300 right now. It's not our servers.

BTW: Some of our servers do not respond to pings, thus the timeouts.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...