• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/

Server Server crashes.....

ah well i used your script commie and this time someone managed to cause it to not respond and get that "Ucc Has Stopped Working" With your script.

1239or6.png
 
Upvote 0
So anyone with a port lower then 50000 will crash/restart your server? I'm also having the same problem right now with my server and here's some ip's I found in the logs with low ports.

NetComeGo: Open myLevel 05/25/12 22:21:58 189.192.179.224:1987
NetComeGo: Open myLevel 05/25/12 22:38:57 71.34.71.64:49810
NetComeGo: Open myLevel 05/25/12 22:38:20 71.34.71.64:49809
NetComeGo: Close TcpipConnection 72.38.205.161:49551 05/25/12 23:47:09
 
Last edited:
Upvote 0
So anyone with a port lower then 50000 will crash/restart your server? I'm also having the same problem right now with my server and here's some ip's I found in the logs with low ports.

NetComeGo: Open myLevel 05/25/12 22:21:58 189.192.179.224:1987
NetComeGo: Open myLevel 05/25/12 22:38:57 71.34.71.64:49810
NetComeGo: Open myLevel 05/25/12 22:38:20 71.34.71.64:49809
NetComeGo: Close TcpipConnection 72.38.205.161:49551 05/25/12 23:47:09

again same problem 176.19.29.242 an ip from Saudi Arabia
 
Upvote 0
75.70.42.119:3600 low port again.

NetComeGo: Open myLevel 06/01/12 13:07:32 72.240.139.212:4843
NetComeGo: Open myLevel 06/01/12 13:07:32 72.240.139.212:4844
NetComeGo: Open myLevel 06/01/12 13:07:37 72.240.139.212:4845
NetComeGo: Open myLevel 06/01/12 13:07:38 72.240.139.212:4846
NetComeGo: Open myLevel 06/01/12 13:07:38 72.240.139.212:4847
NetComeGo: Open myLevel 06/01/12 13:07:39 72.240.139.212:4848
NetComeGo: Open myLevel 06/01/12 13:07:39 72.240.139.212:4849
NetComeGo: Open myLevel 06/01/12 13:07:39 72.240.139.212:4850
NetComeGo: Open myLevel 06/01/12 13:07:39 72.240.139.212:4851
NetComeGo: Open myLevel 06/01/12 13:07:40 72.240.139.212:4852
NetComeGo: Open myLevel 06/01/12 13:07:40 72.240.139.212:4853
NetComeGo: Open myLevel 06/01/12 13:07:40 72.240.139.212:4854
NetComeGo: Open myLevel 06/01/12 13:07:40 72.240.139.212:4855
NetComeGo: Open myLevel 06/01/12 13:07:40 72.240.139.212:4856
NetComeGo: Open myLevel 06/01/12 13:07:41 72.240.139.212:4857
NetComeGo: Open myLevel 06/01/12 13:07:41 72.240.139.212:4858
NetComeGo: Open myLevel 06/01/12 13:07:41 72.240.139.212:4859
NetComeGo: Open myLevel 06/01/12 13:07:41 72.240.139.212:4860
NetComeGo: Open myLevel 06/01/12 13:07:42 72.240.139.212:4861
NetComeGo: Open myLevel 06/01/12 13:07:42 72.240.139.212:4862
NetComeGo: Open myLevel 06/01/12 13:07:42 72.240.139.212:4863
NetComeGo: Open myLevel 06/01/12 13:07:59 72.240.139.212:4864
 
Upvote 0
Having the same issue, and went through all the old crash logs from the past few months and found about a dozen IP's that low port crashed our server in that time span. Heres a list for you guys

65.128.155.110 Pennsylvania
2.94.15.184 Moscow Russia
74.100.215.182 Las Angeles California
98.66.203.194 Atlanta Georgia
83.20.132.130 Poznan Poland
178.207.53.0 Moscow Russia
31.192.72.3 Prague Czech Republic
109.231.3.55 Warsaw Poland
188.134.42.215 Denver Colorado
41.102.6.155 Algiers Algeria
31.186.32.105 Tralee Ireland
2.5.105.155 Paris France
178.235.59.66 Warsaw Poland
75.168.81.174 Minneapolis Minnesota
62.61.157.213 Vejle Denmark
72.240.139.212 Toledo Ohio
79.197.207.107 Berlin Germany
89.7.101.110 Granollers Spain
46.35.192.200 Orosh
 
Last edited:
Upvote 0
Is this exclusive to Windows servers or both MS and Linux? I haven't noticed this issue with any major prevalence on my servers but I'm running linux. If I did notice this problem I'd just start closing down the low port ranges. Can you close those ports on your Windows firewall, or better yet within your router?

If they can't connect to you on a given port I'd imagine they'd have a hard time using that to crash you then. But not an expert in this issue by any means.
 
Upvote 0