Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
here is another thread which I believe is the same issue (at least for me):
http://steamcommunity.com/app/346110/discussions/0/517141624283049149/
btw, from what I can tell the SteamNetDriver_ starts at 0 and increases each time you try to connect, so SteamNetDriver_0 on the first fail, SteamNetDriver_9 on the 10th fail, and I've personally had it up to SteamNetDriver_12. I just want in my game so bad! My dinos are likely starving to death!
* We reset my router, my modem and the pc.
* Verified my game files and reset the router, modem and pc.
* Accessed the router and had my pc designated the DMZ host (should take away any port issues)
* Used a proxy server to rule out any IP issues;
* We also logged into my account from another computer and tried to access the server that I have the issue on with no success.
None of the above allowed me to log into OfficialServer49 with success and access my character.
This really seems to be a server-side issue. We're hoping that the next server reboot fixes the issue.
That was succesfull, I was able to conect with different account. Then switched to my account again..and guess what...no luck...couldnt get on that server with my account. So for 1 thing I am sure..it is not a pc or ip adress issue.
Now waiting for patch 207 to be released somewhat later today. I will cross fingers that a server restart will solve the issue. Will update later.
It does get frustrated though...
I experienced this same UNetConnection Tick Connection TIMED OUT error when trying to set up a dedicated server for the game Satisfactory. Here's the solution I found:
Short answer: If the server you are connecting to is on your LAN, you cannot use a public IP to connect, you must use your local IP.
Long answer: I set up the server on dedicated server hardware, forwarded necessary ports to that IP, and set up a free DNS to point to my public IP (so I don't have to give every player my real IP address). Before telling my friends to try connecting to my server, I wanted to test it myself. I booted up the game on my desktop PC, typed in the DNS and port, and tried to connect. That gave me the error message. I pulled my hair out for hours trying to figure out why "my server was broken". In actuality, it was not broken, I just could not use my public IP (or my DNS) to connect to my own server. I tried using my local IP (192.168.1.128), and it connected with no problems. I instructed my friends to connect using my public IP or DNS and they could connect just fine.
This may not be the same cause/solution of the error message that you are experiencing, but this was the solution for me. Hope that helps.
Locate your Game.ini file on the server under FactoryGame/Saved/Config/(WindowsServer/linux)/game.ini and add the following lines:
[/script/onlinesubsystemutils.ipnetdriver]
InitialConnectTimeout=60.0
ConnectionTimeout=60.0
Then restart the server
I ran the server on Ubuntu 22.04 and it is now running without any errors.