Authentication failed critical error

[Sarasil]

Soo the day of the last event I ran in to this problem. I could log in with the launcher but the game does not seem to connect to the server. I get this empty menu screen (screenshot 1) for about a minute before the game freezes and I get "critical error: Authentication failed- aplication will now terminate." (screenshot 2)

I tried the temporary Hotspot fix but it broke my network drivers .. soo that didn't work.

I changed my password on the forum, re installed the game, but it still doesn't work.

Anyone else having the same problem?

[Sarasil]

Apparently I can log in on someone else's computer ... soo uh .. where could the problem be ? ^^:

[Padraig]

Same problem here, am using windows 8.1 with anti viruses closed

[Sarasil]

I guess we are both screwed then, doesn't seem to be any fix for it. Had the same thing happen a few times on the official server... but since that was on my mac mythic support couldn't help me either...

[MaxHayman]

You managed to get into the game so the hotspot shouldn't have been needed. Usually this happens because the launcher didn't patch the game properly or data.myp wasn't edited with the server information. Try copying WAR.exe and data.myp from the working pc.

[Sarasil]

I tried replacing all my files with the working ones but I'm still having the same problem. I used several launchers even... >.> Jefawk managed to **** up all of them apparently...what a retard....

This is the sniff i took from the connection...if it helps in any way.

The other computer is connected to the same network and it works.


Thanks a lot!

[MaxHayman]

Im guessing it waits a few seconds before showing the error? Seems to be not getting a response to CMSG_AuthSessionTokenReq. Can you sent the logs in the warhammer folder /logs

Thanks

[Sarasil]

Several seconds, yes. Attached

Thanks

[Awiwiwi]

I copied the hole Warhammer-Folder from my Win7-Pc to my Win7-Laptop. And now I have the same problem. At the moment i can't say if there's the same problem on the pc, because i'm not at home. But i had no problmes with Warhammer on my Pc so far.

I thought maybe it's smthing about my copied pc settings, which my laptop can't manage, but I got an message on the first start up, that the game has changed my settings for performance blablabla.

Another odd thing is, that there is no launcher-folder in my directory, so I don't even get to see my launcher-error-report.

I downloaded the launcher again. Tried with administrator and without. My firewall and antivirus doesn't block the game. I have no idea what to do else, but downloading the game again, which wouldn't be worth it. I will be home tomorrow.

In another thread I read that the servers got a restart. But this was about 4h ago. Could this be the problem? Hope anybody has an idea.

Thanks.

Edit: Uh, i found this:

Spoiler:

[2015/01/24 18:50:46] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 18:50:46] Attempting authentication using session token
[2015/01/24 18:50:46] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 18:50:46] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 18:50:47] Active Sockets: Host [0] Client [1]
[2015/01/24 18:50:48] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 18:50:48] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 18:51:03] Active Sockets: Host [0] Client [1]
[2015/01/24 18:51:12] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2015/01/24 18:51:12] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2015/01/24 18:51:12] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2015/01/24 18:51:12] œš§: Failed authentication with session token. Result: 4904840
[2015/01/24 18:51:21] Active Sockets: Host [0] Client [1]
[2015/01/24 18:51:51] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 18:51:51] Attempting authentication using session token
[2015/01/24 18:51:51] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 18:51:51] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 18:51:51] Active Sockets: Host [0] Client [1]
[2015/01/24 18:51:52] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 18:51:52] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 18:52:07] Active Sockets: Host [0] Client [1]
[2015/01/24 18:52:16] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2015/01/24 18:52:16] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2015/01/24 18:52:16] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2015/01/24 18:52:16] œš§: Failed authentication with session token. Result: 4904840
[2015/01/24 18:56:17] Active Sockets: Host [0] Client [1]
[2015/01/24 18:59:20] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 18:59:20] Attempting authentication using session token
[2015/01/24 18:59:20] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 18:59:20] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 18:59:20] Active Sockets: Host [0] Client [1]
[2015/01/24 18:59:21] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 18:59:21] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 18:59:36] Active Sockets: Host [0] Client [1]
[2015/01/24 19:12:17] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 19:12:17] Attempting authentication using session token
[2015/01/24 19:12:17] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 19:12:17] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 19:12:17] Active Sockets: Host [0] Client [1]
[2015/01/24 19:12:18] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 19:12:18] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 19:12:33] Active Sockets: Host [0] Client [1]
[2015/01/24 19:12:42] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2015/01/24 19:12:42] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2015/01/24 19:12:42] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2015/01/24 19:12:42] œš§: Failed authentication with session token. Result: 4904840
[2015/01/24 19:17:18] Active Sockets: Host [0] Client [1]
[2015/01/24 19:22:12] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 19:22:12] Attempting authentication using session token
[2015/01/24 19:22:12] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 19:22:12] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 19:22:12] Active Sockets: Host [0] Client [1]
[2015/01/24 19:22:13] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 19:22:13] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 19:22:28] Active Sockets: Host [0] Client [1]
[2015/01/24 19:31:11] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 19:31:11] Attempting authentication using session token
[2015/01/24 19:31:11] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 19:31:11] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 19:31:11] Active Sockets: Host [0] Client [1]
[2015/01/24 19:31:12] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 19:31:12] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 19:31:27] Active Sockets: Host [0] Client [1]
[2015/01/24 19:31:36] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2015/01/24 19:31:36] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2015/01/24 19:31:36] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2015/01/24 19:31:36] œš§: Failed authentication with session token. Result: 4904840
[2015/01/24 19:31:59] Active Sockets: Host [0] Client [1]
[2015/01/24 19:59:46] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2015/01/24 19:59:46] Attempting authentication using session token
[2015/01/24 19:59:46] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2015/01/24 19:59:46] MythLogin::LoginClient::Connect: Attempting connection to 31.186.229.135:8048
[2015/01/24 19:59:46] Active Sockets: Host [0] Client [1]
[2015/01/24 19:59:47] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2015/01/24 19:59:47] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2015/01/24 20:00:02] Active Sockets: Host [0] Client [1]
[2015/01/24 20:00:11] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2015/01/24 20:00:11] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2015/01/24 20:00:11] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2015/01/24 20:00:11] œš§: Failed authentication with session token. Result: 4904840
[2015/01/24 20:00:18] Active Sockets: Host [0] Client [1]

[JeFawk]

Nothing from what you said is odd.

Performance blabla means your computer is **** and the launcher tried to repair a part of it.

There shouldn't be a launcher folder in your war client folder anyway...