• Announcements

    • HEAVY265

      Attention Soldiers Operation Fury Needs you!   02/20/2020

      Attention All Soldiers, Operation Fury needs you.  You need to choose a side and sign up.  
      For more intel on Operation Fury Please click HERE Please go to Special Event Forum (here), And sign up for allied or axis.
      This will be a CRS Lead event on both sides.  Xoom will be heading up the axis side and Heavy265 will be heading up the Allied side. This will be for bragging rights.
      Why are we asking players to sign up you ask. We are trying for a role play experience.   We want this to be a true realistic event.  
      So get up and sign up and let's make this the best event ever!!!!!!!!!!
      Give me your war cry, grrrrrrrrrrrrr
      Heavy265 **out**
Sign in to follow this  
Followers 0
rlnolan

Cannot connect to Authentication Servers

9 posts in this topic

Every time I try to connect this morning I get a message saying I cannot connect to the Authentication servers. I ran the netcheck.bat script and found I cannot ping or tracert auth2.playnet.com. A bit more checking, and I found the connection is failing at 66.28.30.146 [playnet.demarc.cogentco.com]. At first I thought is was just Cogentco farting out (again), but this looks like it's one of playnet's servers not actually part of cogentco's network.

So, please get the authentication servers back up. This is my one day off this week and the only real chance I have to play this game for another 4 days. :D

Share this post


Link to post
Share on other sites
Even though that says "playnet" at the beginning, it isn't actually our server. The important bit is the last: ....cogentco.com.

Can you run the CheckNet app and let me know what you get?

ftp://downloads.wwiionline.com/checknet3.zip

Actually it's ftp://downloads.wwiionline.com/checknet4.zip

The link on the downloads page has been wrong for a while. Also, look here: http://www.gnasche.com/ww2ol/support/loading.htm

The authentication server does not respond to pings. Running a traceroute to it is useless because there are several hops that will only respond to port 27015.

Share this post


Link to post
Share on other sites

That link does not work, tells me there is no such directory. I think you are asking me to run checknet.bat, which I said I already did. Here's the result (minus the DXDiag crap):

netcheck.bat v1.2

Beginning network analysis, this may take a few minutes...

The current date is: Thu 02/02/2006

Enter the new date: (mm-dd-yy)

The current time is: 12:12:46.71

Enter the new time:

======================================

Running: ping ns1.playnet.com -f -l 575 -n 5

======================================

Pinging ns1.playnet.com [66.28.224.252] with 528 bytes of data:

Reply from 66.28.224.252: bytes=528 time=70ms TTL=50

Reply from 66.28.224.252: bytes=528 time=74ms TTL=50

Reply from 66.28.224.252: bytes=528 time=75ms TTL=50

Reply from 66.28.224.252: bytes=528 time=70ms TTL=50

Reply from 66.28.224.252: bytes=528 time=72ms TTL=50

Ping statistics for 66.28.224.252:

Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 70ms, Maximum = 75ms, Average = 72ms

Pinging auth2.playnet.com [66.28.224.240] with 528 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 66.28.224.240:

Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),

======================================

Running: tracert -d ns1.playnet.com

======================================

Tracing route to ns1.playnet.com [66.28.224.252]

over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.2.1

2 2 ms 2 ms 2 ms 192.168.1.1

3 49 ms 47 ms 48 ms 65.40.99.1

4 49 ms 48 ms 49 ms 69.68.225.185

5 52 ms 51 ms 52 ms 144.228.134.189

6 53 ms 53 ms 53 ms 144.232.11.169

7 53 ms 53 ms 53 ms 144.232.11.33

8 53 ms 53 ms 53 ms 144.232.9.136

9 55 ms 54 ms 73 ms 144.232.8.122

10 57 ms 55 ms 53 ms 154.54.10.29

11 56 ms 55 ms 53 ms 154.54.2.21

12 56 ms 55 ms 54 ms 66.28.6.226

13 56 ms 55 ms 56 ms 66.28.30.146

14 * * * Request timed out.

15 56 ms 55 ms 56 ms 66.28.224.252

Trace complete.

Tracing route to auth2.playnet.com [66.28.224.240]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1

2 2 ms 2 ms 2 ms 192.168.1.1

3 49 ms 48 ms 48ms 65.40.99.1

4 48 ms 50 ms 48 ms 69.68.225.185

5 52 ms 54 ms 52 ms 144.228.134.189

6 52 ms 51 ms 54 ms 144.232.11.169

7 51 ms 51 ms 52 ms 144.232.11.33

8 54 ms 55 ms 55 ms 144.232.9.136

9 57 ms 53 ms 53 ms 144.232.8.122

10 53 ms 54 ms 53 ms 154.54.10.29

11 55 ms 55 ms 54 ms 154.54.2.21

12 55 ms 56 ms 55 ms 66.28.6.226

13 54 ms 55 ms 55 ms 66.28.30.146

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

======================================

Running: netstat -s

======================================

IPv4 Statistics

Packets Received = 977979

Received Header Errors = 0

Received Address Errors = 8

Datagrams Forwarded = 0

Unknown Protocols Received = 0

Received Packets Discarded = 2692

Received Packets Delivered = 975287

Output Requests = 1004767

Routing Discards = 0

Discarded Output Packets = 0

Output Packet No Route = 0

Reassembly Required = 0

Reassembly Successful = 0

Reassembly Failures = 0

Datagrams Successfully Fragmented = 0

Datagrams Failing Fragmentation = 0

Fragments Created = 0

ICMPv4 Statistics

Received Sent

Messages 248 192

Errors 0 0

Destination Unreachable 115 0

Time Exceeded 110 0

Parameter Problems 0 0

Source Quenches 0 0

Redirects 0 0

Echos 2 190

Echo Replies 21 2

Timestamps 0 0

Timestamp Replies 0 0

Address Masks 0 0

Address Mask Replies 0 0

TCP Statistics for IPv4

Active Opens = 9725

Passive Opens = 129

Failed Connection Attempts = 3755

Reset Connections = 499

Current Connections = 0

Segments Received = 880921

Segments Sent = 961467

Segments Retransmitted = 7265

UDP Statistics for IPv4

Datagrams Received = 94118

No Ports = 246

Receive Errors = 0

Datagrams Sent = 35633

======================================

Running: netstat -e

======================================

Interface Statistics

Received Sent

Bytes 320225730 109482660

Unicast packets 759840 550933

Non-unicast packets 2414 1184

Discards 0 0

Errors 0 0

Unknown protocols 322

======================================

Running: netstat -rn

======================================

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x20002 ...00 11 50 35 8d 59 ...... Belkin 802.11g Network Adapter - Packet Scheduler Miniport

===========================================================================

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.51 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.2.0 255.255.255.0 192.168.2.51 192.168.2.51 20

192.168.2.51 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.2.255 255.255.255.255 192.168.2.51 192.168.2.51 20

224.0.0.0 240.0.0.0 192.168.2.51 192.168.2.51 20

255.255.255.255 255.255.255.255 192.168.2.51 192.168.2.51 1

Default Gateway: 192.168.2.1

===========================================================================

Persistent Routes:

None

Route Table

======================================

Running: netstat -an

======================================

Active Connections

Proto Local Address Foreign Address State

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING

TCP 192.168.2.51:139 0.0.0.0:0 LISTENING

UDP 0.0.0.0:445 *:*

UDP 0.0.0.0:500 *:*

UDP 0.0.0.0:1026 *:*

UDP 0.0.0.0:1041 *:*

UDP 0.0.0.0:1042 *:*

UDP 0.0.0.0:1197 *:*

UDP 0.0.0.0:1255 *:*

UDP 0.0.0.0:1272 *:*

UDP 0.0.0.0:1273 *:*

UDP 0.0.0.0:2900 *:*

UDP 0.0.0.0:3157 *:*

UDP 0.0.0.0:4500 *:*

UDP 127.0.0.1:123 *:*

UDP 127.0.0.1:1900 *:*

UDP 127.0.0.1:2514 *:*

UDP 127.0.0.1:2937 *:*

UDP 192.168.2.51:123 *:*

UDP 192.168.2.51:137 *:*

UDP 192.168.2.51:138 *:*

UDP 192.168.2.51:1900 *:*

Share this post


Link to post
Share on other sites

rlnolan, the results you're seeing are exactly the same results that you'd see if you could connect fine. The traceroute just doesn't help much. See my link above. The most common cause is firewall or router.

Share this post


Link to post
Share on other sites

I am running a router to connect multiple computers. But, Ive been running the same router for more than 1 year with no problems. I did recently re-install Windows XP and am running Windows Firewall, but disable that when going to play the game. Routers and firewalls are not the problem here.

Here is the result of the checknet.exe program:

Test Starting.

Test 1: Auth Pri -OK- 47ms

Test 2: Main Pri -OK- 47ms

Test 3: Main Alt -OK- 62ms

Test 4: Main PingPri -OK- 47ms

Test 5: Main PingAlt -OK- 47ms

Test 6: Main Chat -OK- 47ms

Test 7: Event Pri -OK- 47ms

Test 8: Event Alt -OK- 47ms

Connection tests completed OK.

it had no problems getting connected. I am also able to log into the game now, so whatever the problem was seems to have corrected itself. For now, at least. :)

Share this post


Link to post
Share on other sites

There were at least 5 people with the 1.21.3 patch that started having problems with connecting through their router/firewall that had never had a problem in the past 5 years. Something changed somewhere. I'm not sure what each of them did to fix it, but they narrowed it down to the firewall.

Share this post


Link to post
Share on other sites

I believe the issue is/was the same as a recent MAC issue which was patched. Recently they added the ability for WWIIOL to try multiple routes to the server and pick the best one. The problem was (for MACs) if it didn't pick the first one it tried, it wouldn't connect.

It's possible it's the same, but maybe they just put the fix in the mac patch.

Share this post


Link to post
Share on other sites
There were at least 5 people with the 1.21.3 patch that started having problems with connecting through their router/firewall that had never had a problem in the past 5 years. Something changed somewhere. I'm not sure what each of them did to fix it' date=' but they narrowed it down to the firewall.[/quote']

In that case, something changed in the game, not the router or the firewall. In any case, this has only been happening to me this morning, which makes me think it's a network problem not software or anything to do with my computer or any patches for the game in the last 2 months. More than likely CogentCo is just living down to their reputation. :)

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.