Sac Posted August 15, 2015 Share Posted August 15, 2015 I imagine there's probably a few people having trouble trying to get a server working nicely with the new steam integration stuff, so feel free to use this thread for your problems too. My issue is the following: I ran through steamcmd to download all the appropriate new bits and launched a server which appears to be functioning. Trouble is that I just cannot seem to join it. Here's a screencap of the problem from the serverside cmd window: And here is the same attempt from the clientside window: Which looks very much like a port problem, only I absolutely have all of the relevant ports opened - including the two new ones listed in the server's .ini file for SteamPort1 and SteamPort2 Anybody reckon they might know what I'm missing? Link to comment Share on other sites More sharing options...
ModdedTibby Posted August 15, 2015 Share Posted August 15, 2015 i had the same issue. I rebooted the server a few times and it was good for me. Link to comment Share on other sites More sharing options...
CaptKaspar Posted August 17, 2015 Share Posted August 17, 2015 I had an issue that my router port forwarding for the Steam ports had to be both TCP/UDP. This was with a NetGear Router Link to comment Share on other sites More sharing options...
code3211 Posted August 28, 2015 Share Posted August 28, 2015 I had an same issue on my Billion and Asus n12u router too. (error changed if you disable firewall on your router)but after i try to add -nosteam on my launcher issue is gone. seem like this is steam port problem. Link to comment Share on other sites More sharing options...
Brybry Posted August 28, 2015 Share Posted August 28, 2015 At first glance it looks like TCP port 16262+ is blocked in some way (firewall, not being forwarded, client or server jvm trying to use ipv6 instead of ipv4, etc) and so the client can't connect to that for the map info and is doing a normal clean disconnect. Link to comment Share on other sites More sharing options...
Brybry Posted August 28, 2015 Share Posted August 28, 2015 Ok, so due to a potential bug or just weird behavior make sure you have TCP ports forwarded on your router to your server, even if you are connecting from within your internet network or localhost. I think this issue is related. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now