[-Mo-]

Hi guys,

We actually own a COD 1.5 server running on a Windows XP computer. It's running PAM mod with CAL settings. Some days ago, the server begin to crash with that weird log in the console. We've look over the net but can't find any further informations about that problem. I'm wondering if you guys can help us. If you need more informations, please post!

Here's the log

Unknown connectionless packet command.

CL packet 209.51.140.58:-21668: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-16778: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-21602: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-21290: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-21227: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-20900: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-20841: getstatus

Unknown connectionless packet command.

CL packet 216.136.177.202:25888: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-20528: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-20461: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-20142: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-22030: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-20090: getstatus

Unknown connectionless packet command.

CL packet 216.136.180.5:25888: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-19720: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-19661: getstatus

Unknown connectionless packet command.

CL packet 12.207.40.154:3450: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-19355: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-19290: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-18975: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-18902: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27302: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27302: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27302: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27302: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27302: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-24679: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-18607: getstatus

Unknown connectionless packet command.

CL packet 213.103.217.87:2171: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-18548: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:3359: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27499: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27499: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:3359: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27499: getstatus

Unknown connectionless packet command.

CL packet 220.233.48.241:27499: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-18165: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-18084: getstatus

Unknown connectionless packet command.

CL packet 217.71.110.128:-15860: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-17727: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-17677: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-17377: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-17319: getstatus

Unknown connectionless packet command.

CL packet 217.165.87.82:3524: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-17000: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-16924: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-16607: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-16559: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-16246: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-16181: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-15812: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-15758: getstatus

Unknown connectionless packet command.

CL packet 66.28.205.145:-750: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-15462: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-15405: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-15049: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-14980: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-21714: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-14706: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-14640: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-14327: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-14267: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-13909: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-13848: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-13496: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-13444: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-23816: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-13043: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-12982: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-12650: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-12587: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-12263: getstatus

Unknown connectionless packet command.

CL packet 172.206.224.251:1440: getinfo

Unknown connectionless packet command.

CL packet 217.71.110.128:-12184: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-12198: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-11874: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-11780: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-23780: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-11480: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-11390: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-11060: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-11029: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-10670: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-10645: getstatus

Unknown connectionless packet command.

CL packet 83.201.215.234:2577: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-10293: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-10231: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-23728: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-9918: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-9852: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-9470: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-9412: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-9121: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-9059: getstatus

Unknown connectionless packet command.

CL packet 216.136.177.202:25888: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-8755: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-8699: getstatus

Unknown connectionless packet command.

CL packet 66.98.188.29:-26653: getinfo

Unknown connectionless packet command.

CL packet 66.28.205.145:-4701: getinfo

Unknown connectionless packet command.

CL packet 209.51.140.58:-8370: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-8305: getstatus

Unknown connectionless packet command.

CL packet 216.136.180.5:25888: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-7985: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-7917: getstatus

Unknown connectionless packet command.

CL packet 212.87.109.244:1072: getstatus

Unknown connectionless packet command.

CL packet 212.87.109.244:1072: getstatus

Unknown connectionless packet command.

CL packet 212.87.109.244:1072: getstatus

Unknown connectionless packet command.

Hitch warning: 1627 msec frame time

CL packet 209.51.140.58:-7606: getstatus

Unknown connectionless packet command.

CL packet 209.51.140.58:-7540: getstatus

Unknown connectionless packet command.

CL packet 172.206.224.251:2580: getinfo

Unknown connectionless packet command.

[Advertisements]

with that many packets someone may be trying to down your server for some reason....have you banned anyone from your server lately?

[dsenette]

with that many packets someone may be trying to down your server for some reason....have you banned anyone from your server lately?

[-Mo-]

yeah, we ban as usual people who are not nice with us lol..

but can you explain to me the reason of that log... I have good knowledge in networking but didnt know about that!

[dsenette]

well due to the shear amount of packets it looks like someone is trying to just do a DOS attack by packet flooding you....either close the port that those packets are coming into or get a better firewall

[-Mo-]

I heard about security breach on cod sever, is that fixable but any patch or something like that??

and as we see, this is coming from multiple IP and ports.... quiete hazardus to block thoses, dont you think?

[dsenette]

well...those seem to be random ports they are all above the reserved range....it's always best to block all ports except the ones you need for the server to be functional....and i would check the COD website or something to see if there is a patch (not familiar with the actual stuff you're running...just the event)

[-Mo-]

Allright, and the people who own the server just tell me it,s behind a router and only ports to be use are open... I'm a bit confuse right now..

is there a way in windows integrate firewall to block thoses request.. I mean... with the snmp service or some way....

As block ping request etc...

Edited by -Mo-, 18 August 2005 - 08:43 AM.

[-Mo-]

I just read about ICMP options on the ICF of Windows Xp.

an option call Allow outgoing source quench seems to be interesting..

its explain like this:

When this computer's ability to process incoming data cannot keep up with the rate of transmission, data will me drop and the sender will be ask to slow down.

Might be able to avoid flooding with that... what you think?