Cannot Authenticate

[tohuwbohuw]

<Login Timeout> I can't get into the game

-This happens when the server is down
-This happens when the server is laggy

Check the website first if the server is down or other people have this problem too.

Otherwise follow this:

download Hotspot Shield VPN: http://www.chip.de/downloads/Hotspot-Sh ... 00785.html

Then just start the game and it should work.

(Own risk)

This is my issue, but the solutions didn't work. Server appears to be up, Hotspot VPN didn't help. I also tried many times (~10), per the video in the same thread.

My WAR folder:


My login log contains entries like:

Code: Select all

[2020/03/20 00:05:19] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2020/03/20 00:05:19] Attempting authentication using session token
[2020/03/20 00:05:19] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2020/03/20 00:05:19] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2020/03/20 00:05:19] Active Sockets:  Host [0] Client [1]
[2020/03/20 00:05:21] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2020/03/20 00:05:21] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2020/03/20 00:05:35] Active Sockets:  Host [0] Client [1]
[2020/03/20 00:05:45] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2020/03/20 00:05:45] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2020/03/20 00:05:45] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2020/03/20 00:05:45] œš§: Failed authentication with session token. Result: 4904840

I have ensured the files are not read only, Administrators have full control, and I'm running the launcher as an administrator. Windows Firewall is disabled. I don't have any anti-malware software installed. I closed other running programs. I've tried deleting the cache folder.

I'm using Windows 10 Pro 64-bit, v1909.

I ensured my password was only alphanumeric and less than 16 characters. I tried a variation of passwords, and I created a new account and tested that. I get the same results.

Here's a capture showing the traffic is passing to the auth service, but the process itself is failing, as the logs indicate:

Code: Select all

No.	Time	Source	Destination	Protocol	Length	Info
248	13.976727	10.0.1.32	46.105.54.77	TCP	66	50955 → 8000 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1
250	14.125211	46.105.54.77	10.0.1.32	TCP	66	8000 → 50955 [SYN, ACK] Seq=0 Ack=1 Win=32120 Len=0 MSS=1460 SACK_PERM=1 WS=1
251	14.125334	10.0.1.32	46.105.54.77	TCP	54	50955 → 8000 [ACK] Seq=1 Ack=1 Win=262656 Len=0
252	14.128404	10.0.1.32	46.105.54.77	TCP	59	50955 → 8000 [PSH, ACK] Seq=1 Ack=1 Win=262656 Len=5
253	14.283951	46.105.54.77	10.0.1.32	TCP	60	8000 → 50955 [ACK] Seq=1 Ack=6 Win=32115 Len=0
254	14.352588	46.105.54.77	10.0.1.32	TCP	433	8000 → 50955 [PSH, ACK] Seq=1 Ack=6 Win=32115 Len=379
255	14.464049	10.0.1.32	46.105.54.77	TCP	54	50955 → 8000 [ACK] Seq=6 Ack=380 Win=262400 Len=0
274	16.604023	10.0.1.32	46.105.54.77	TCP	208	50955 → 8000 [PSH, ACK] Seq=6 Ack=380 Win=262400 Len=154
275	16.747358	46.105.54.77	10.0.1.32	TCP	60	8000 → 50955 [ACK] Seq=380 Ack=160 Win=31961 Len=0
276	16.791787	46.105.54.77	10.0.1.32	TCP	112	8000 → 50955 [PSH, ACK] Seq=380 Ack=160 Win=31961 Len=58
277	16.793053	46.105.54.77	10.0.1.32	TCP	60	8000 → 50955 [FIN, ACK] Seq=438 Ack=160 Win=31961 Len=0
278	16.793098	10.0.1.32	46.105.54.77	TCP	54	50955 → 8000 [ACK] Seq=160 Ack=439 Win=262144 Len=0
280	16.879425	10.0.1.32	46.105.54.77	TCP	54	50955 → 8000 [FIN, ACK] Seq=160 Ack=439 Win=262144 Len=0
284	17.026168	46.105.54.77	10.0.1.32	TCP	60	8000 → 50955 [ACK] Seq=439 Ack=161 Win=31961 Len=0
432	28.222544	10.0.1.32	46.105.54.77	TCP	66	50965 → 8048 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1
435	28.372394	46.105.54.77	10.0.1.32	TCP	66	8048 → 50965 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=2 SACK_PERM=1
436	28.372527	10.0.1.32	46.105.54.77	TCP	54	50965 → 8048 [ACK] Seq=1 Ack=1 Win=262656 Len=0
441	29.064483	10.0.1.32	46.105.54.77	TCP	56	50965 → 8048 [PSH, ACK] Seq=1 Ack=1 Win=262656 Len=2
442	29.064512	10.0.1.32	46.105.54.77	TCP	102	50965 → 8048 [PSH, ACK] Seq=3 Ack=1 Win=262656 Len=48
443	29.211160	46.105.54.77	10.0.1.32	TCP	60	8048 → 50965 [PSH, ACK] Seq=1 Ack=51 Win=65486 Len=2
444	29.280911	10.0.1.32	46.105.54.77	TCP	54	50965 → 8048 [ACK] Seq=51 Ack=3 Win=262656 Len=0
447	29.426021	46.105.54.77	10.0.1.32	TCP	92	8048 → 50965 [PSH, ACK] Seq=3 Ack=51 Win=65486 Len=38
448	29.426763	10.0.1.32	46.105.54.77	TCP	56	50965 → 8048 [PSH, ACK] Seq=51 Ack=41 Win=262656 Len=2
449	29.426790	10.0.1.32	46.105.54.77	TCP	104	50965 → 8048 [PSH, ACK] Seq=53 Ack=41 Win=262656 Len=50
452	29.578939	46.105.54.77	10.0.1.32	TCP	60	8048 → 50965 [ACK] Seq=41 Ack=103 Win=65434 Len=0

Thanks for the assistance!

[Floscrendron]

same problem for me

[sasmus]

Same here.

[Minkua]

can you goto command prompt on your pc and type

tracert 46.105.54.77

and paste the output here? (removing any personal IP info of course) im pretty sure its not an isp issue but this will confirm.

Any time ive seen that error its normally cache based, instead of deleting the cache folder can you delete your cache through I.E or your chosen browser? from my exp its normally an IE cache issue which causes those kind of errors

[sasmus]

1 <1 ms <1 ms <1 ms mynetwork [192.168.1.1]
2 * * * Request timed out.
3 * 14 ms 14 ms 141.208.186.161
4 14 ms 15 ms 14 ms 141.208.186.162
5 * * 14 ms 141.208.186.163
6 * * * Request timed out.
7 17 ms 17 ms 17 ms 62.115.143.50
8 25 ms 25 ms 25 ms s-bb3-link.telia.net [62.115.123.26]
9 48 ms 48 ms 48 ms ffm-bb1-link.telia.net [62.115.138.237]
10 46 ms 47 ms 51 ms ffm-b1-link.telia.net [62.115.121.5]
11 54 ms 53 ms 53 ms be100-112.fra-1-a9.de.eu [37.187.231.232]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 58 ms * 59 ms be101.sbg-g2-nc5.fr.eu [91.121.215.196]
16 61 ms 62 ms 61 ms be7.sbg-vac1-a75.fr.eu [213.186.32.143]
17 59 ms 60 ms 60 ms sbg-vac1-a75-1-firewall.fr.eu [178.33.99.143]
18 56 ms 55 ms 56 ms sbg-vac1-a75-2-shield.fr.eu [178.33.99.144]
19 61 ms 61 ms 61 ms sbg-vac1-a75-3.fr.eu [178.33.99.142]
20 * * * Request timed out.
21 59 ms 60 ms 60 ms vl1250.rbx-g1-a75.fr.eu [37.187.232.26]
22 57 ms 56 ms 57 ms vl1247.gra-d1-a75.fr.eu [37.187.231.235]
23 61 ms 61 ms 61 ms be50-5.gra-3b-a9.fr.eu [37.187.231.90]
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.

[Minkua]

Thanks sasmus, can you delete your IE cache from your browser and try again?

your output had a few missing hops there but i dunno where the logon server is in that chain (thats one for the GM's), you can try the browser cache for now

[Turkish11223]

I have the same tracert as sasmus with a few more timeouts. Deleting the Internet Explorer cache hasn't done anything to change it though.

[Minkua]

hmm well a last shot from me is there's a prob with the firewall settings though the OP said hes disabled the windows firewall.

There’s one last solution you can try. Temporarily changing your DNS settings is a possible quick fix to the problem.
To do this, open Control Panel,
click on Network and Internet,
Network and Sharing Center,
and then Change adapter settings.
Once you’re there, right-click on your network (either Ethernet or Wi-Fi),
and select Properties.Next,
choose and check the Internet Protocol Version 4 (TCP/IPv4) option,
and once again, click Properties. Now, click the Use the following DNS server addresses option and change it to Google’s Public DNS.
To do this, type 8.8.8.8 in the first box, and 8.8.4.4 in the second. After that, you should be set.
**Please screenshot your settings before you change them so you can always switch back should this workaround not work**

[sasmus]

Still not working :/

[Minkua]

sorry chaps im out of ideas, my only ideas at this point is it could be active directory related or your router holding open a stale connection, i know it may sound a bit of a cop out but a full power cycle of your broadband router (leave powered off for one min) may help. This ones prob best left with the GM's best of luck guys