PING timeout warning.

[happahappa]

Hello,

we have a private server running, which is whitelisted. But one of us has issues, connecting to it. In the server logs i get a lot of "PING timeout warning. resending ping to RegisteredClient..." messages, before the client exits with a read timeout, without having spawned. But the clients always authentificates itself successfully with the dock before the timeout. Shouldnt really be a latency issue, since we are all from europe. What can we do?


Thanks!

 

[MrGrey1]

Geographical location is a very unreliable method of gauging network connectivity and 'Europe" is a big place... ;p
I'm assuming you've confirmed he's not using wifi or wireles, his PC specs are adequate and he can play the game singleplayer...
PING test or preferably Trace route AKA Tracert in the windows world.
https://support.microsoft.com/en-au...rt-to-troubleshoot-tcp-ip-problems-in-windows
See if there is any issue between him and the server.

 

[happahappa]

yes. he is using ethernet , has broadband, new computer. nobody else has an issue but him, nevertheless. reinstalled the server and client serveral times. tried different settings. traceroute works, which is obvious, because he can connect to the server. he connects, authenticates, then he gets a timeout for some reason. he can play in sp and mp on other servers. so it the issue could be on server side. but the same story. high speed broadband, high end workstation. no latency issues with ping or traceroute(between him and the server). used to work in the past. something has changed. can't nail it down.
[doublepost=1526998151,1526997992][/doublepost]and it has nothing to do with any local networks settings like NAT. the issue is not the connection. everyone connects, including him, but he is the only one getting the timeout after the initial connection and authentification.

 

[MrGrey1]

Yeah short of major issues the tracert will work, it's the latency and packet loss along the way that the tracert will provide you that is important.
If it worked previously and he can also connect and play elsewhere then it suggests something up with his account/character on the server. Disable whitelist temporarily and get him to try with a different character name. It might be something to do with his spawn location. Also if it worked previously what's changed?

 

[arkahys]

the problem could come from port. I don't know for starmade, but for many games first connection aren't done on the ports server, and others authentification is "validated" before client answer to a server request.

As 4242 is a common port for many application. If port is binded by other application on client, starmade can't bind it then client will not receive packets. (but can send on 4242...)
-> To test this, change server port for an unusual number.

May too be a due to firewall/antivirus or virus who have bind or closed ports. This port is used by some trojans.
-> check antivirus (or/and) config, and logs when game is launched.

 

[happahappa]

it's not the AV, it's not the port. also not whitelisting. we tried an untouched new server installation, also port forwarding to a client running a local server on desktop. it's all the same. at this point, i don't know what else it could be. pings are just fine. he even gets a ping ingame for the first few seconds after connecting. he also gets the 'spawning screen', where he is rotating aorund. then the ping freezes ingame (usually somewhere between 50-70), which is shortly before he gets a timeout. all networking tests dont indicate any issues. in his logs, the is obviously reading from the server and then he gets 'server not responing. either connection loss or server is under heavy load" messages. but neither network nor any other resources are under heavy load serverwise. this is rather strange.

 

[MrGrey1]

Well that sounds like a loading problem with something in his sector. What happened(s) when he tried a different character name and loaded a new toon at the default spawn location?

 

[happahappa]

At this point, we actually believe, that it doesn't have anything to do with starmade itself. It is probably some osbscure network related issue.