![]() ![]() It presents combat, crafting, looting, mining, exploration, and character growth, in a way that has seen a rapturous response from fans worldwide.Įxplore – Huge, unique and rich environments, offering the freedom to play the game any way you want.Ĭraft – Craft and repair weapons, clothes, armor, tools, vehicles, and more.īuild – Take over a ruin, or build from the ground-up. So only 26900 TCP and 26900-26903 UDP need to be open external ports on the router in all cases? If I may suggest an improvement there: the FAQ talks about "opening ports in firewall" versus "required ports", the distinction is not even clear to me (firewall is ambiguous, router isn't mentioned at all), how can it be clear for users without any network knowledge.Set in a brutally unforgiving post-apocalyptic world overrun by the undead, 7 Days to Die is an open-world game that is a unique combination of first person shooter, survival horror, tower defense, and role-playing games. Nothing I have been able to do on our end has alleviated it so far.Īh, I was a little unsure about which ports exactly have to be **forwarded** by the router (so that the port can be "contacted cold" from external sources) and which ones are just used with initial connection always coming from the server (in most cases those need no special attention). All I can see in the log is regular SteamAuth failures. A few of the players on the servers we host have been frequently getting kicked off the servers with a "network timeout" error. I've been seeing a lot of this happening though since the major Steam update a few weeks ago, and can't help but think it might be something happening on Steam's side of things. If it's just a case of bad routing, this will typically resolve the issue. Wait for it to fully setup and get a connection. Open an administrative command prompt window as an administrator Steam may also use additional ports in the 27000-27099 range for processing data, but that isn't something you will typically need to forward like you do with the server ports.īased on the data I can see, I would advise the following steps for both the host and the client. Default range for the server is TCP 26900 and UDP 26900-26903. AFAIK the port range is still accurate, and I'm pretty sure I updated the FAQ when it changed in a17. I'm not sure on the port SteamAuth is using offhand. Were you thinking of those ports too when you said they were open? Or did you simply open all do you know on which port this callback should come in? Is it possible that something changed with steam authentication? It seems quite a few people suddenly have the same problem. There is pinned thread called "Support FAQ" here in general support, an old thread and possible outdated in parts, but there is a list of ports you should have open. I'm pretty sure that your server expects some answer from steam which isn't getting in. So the problem seems to be the connection between server and steam. If it would work then this should be followed by " Authentication callback."īut in your server logfile 10 seconds go by and then it presents the error message "ERR GameServer.LogOn timed out" So there are the lines " AuthenticateUser()" and then " Authenticating player.". Then the server tries to authenticate you with steam. the server checks if you are allowed to login, if the version is compatible. ![]() On the server I see that when you login, you are first checked with the server (all the lines with ), i.e. ![]() Whatever the result, please tell us, it may pinpoint the problem for other players and for TFP.Įdited Septemby meganoth (see edit history) Specifically you might try to follow the solution he found (create another steam account for the server) IF you started the server headless (which your logfile seems to suggest since I can't see a local player login on the server). I'm not sure his and your case is comparable but that case seems to imply that there may be rule changes within steam what is acceptable and what not. Could you do a test with EAC off on both server and client and see if that works?Īnother problem might be the way the server is started, see this thread. We also know that steam worked a lot on EAC lately so it might be specifically an EAC problem here. That error message seems to pop up a lot lately and seems to be connected to recent steam and possibly windows updates Then the client tries to connect again but the server reports an error "ERR GameServer.LogOn timed out" and the logon attempt fails again. Then the client wants to connect but gets kicked because EAC says there is something wrong with it. As far as I can see your logfiles seem to tell the following story: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |