Page 1 of 1
Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 2:51 pm
by Motive133
I've setup a headless dedicated server on my home server running version 12.24. I'm running the server with the command "Factorio.exe --start-server save1.zip" and I am able to connect over LAN.
The problem exists while trying to connect VIA WAN. I have port forwarded the port.
I also tested my client by connecting to a server from the multiplayer forums, which i was able to connect to.
I have several questions:
1. Is peer-to-peer disabled by default in 12.24?
If so, disabled by default on both the client and server?
2. Does the "--peer-to-peer" command enable P2P? (I don't want to enable it, just asking for knowledge sake.)
3. Is UDP 34197 the only port that needs to be opened for a server?
I assume since I was able to connect to the Server from the multiplayer forums that the server I am running is set to P2P, I know for sure that port 34197 is closed on my client end. (I manage the firewall at the company I work for)
Any suggestions or help would be appreciated. Thanks.
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 3:58 pm
by starholme
1. Yes, and yes.
2. Also yes.
3. Yes again.
I like these questions, easy to answer!
Anyway, to help troubleshoot you problem, try these items:
Are you trying to run the client and server on the same computer? Factorio doesn't play nice this way. Host on a separate computer, or a VM works surprisingly well(playing with a coworker this way)
Ensure the port really is open - Check with an external tool such as
http://www.yougetsignal.com/tools/open-ports/
Let us know what happens!
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 4:15 pm
by Motive133
Thank you for the response.
The Client and Server are 2 separate computers.
According to the external tool, the port is "closed". That being said, I checked the port on a known working server and it also appeared "closed" to the tool. So I assume the software doesn't respond to the port probe?
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:10 pm
by Motive133
Okay, I've also tried doing a full reinstall of Factorio on the server. I've changed the port number to a known working port. I've added the server to the DMZ. None of these things have resulted in a connectable server.
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:17 pm
by starholme
Strange. It's always worked for me if the server was running. I just tried, against this public server:
viewtopic.php?f=53&t=13579
The IP listed there responded to my port check of 34197.
I don't have one running myself to check as I'm at work...
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:21 pm
by Motive133
Well, I figured out the issue...
User error. /facepalm
Turns out I had a port range that conflicted with Factorio's default port pointed to another internal IP.
That being said, no clue why the known working port did not resolve the issue.
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:22 pm
by daniel34
starholme wrote:Strange. It's always worked for me if the server was running. I just tried, against this public server:
viewtopic.php?f=53&t=13579
The IP listed there responded to my port check of 34197.
I don't have one running myself to check as I'm at work...
My server might be an exception to that port checker (
http://www.yougetsignal.com/tools/open-ports/), as I also have a web server running on TCP 34197 for the modpack download and some other stuff.
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:23 pm
by Motive133
FYI I can connect fine to the server now, the port still shows "closed" on the Port Tester that you linked. /shurg
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:41 pm
by prg
There are no open or closed UDP ports, that's only a TCP thing.
Re: Can't connect to my dedicated server
Posted: Wed Mar 02, 2016 5:47 pm
by starholme
prg wrote:There are no open or closed UDP ports, that's only a TCP thing.
Suddenly it all makes sense. It's always worked for me because I always port forward UDP and TCP. It's just a habit. So the port checking would work for me, but not for anyone who only picks UDP.