I've found this on my Field Server.

Quote:

---

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 112.210.56.38, UserNum -1, ID , GarbageMSG K9IHANA GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3287

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 58.182.133.60, UserNum -1, ID , GarbageMSG M7HSET GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3287

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 58.182.133.60, UserNum -1, ID , GarbageMSG O5FDASEOT GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3927

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 58.182.133.60, UserNum -1, ID , GarbageMSG K9IHANA GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3029

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 58.182.133.60, UserNum -1, ID , GarbageMSG M7HSET GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3029

CNetUser::Client invalid Garbage Msg!! Channel -1, IP 121.54.47.60, UserNum -1, ID , GarbageMSG L8IDUL GTRL MESSAGE!! GTRL_MSG NUM 2887, MSG NUM 3317

---

Someone encountered this already? If yes, then have you figure it out already this errors? It is flooding my field server.

O5FDASEOT <-- Shout.

thats what am i pin pointing on my new method attack on the discussion XD

Lol, its different, what you have on your thread was a user using a server manager, here they are using CE, WPE and RPE to send bad packets to the server.

oh.. its easy to block WPE/CE/RPE :D HEX and ASM is the solution :)

How sir?

i'll tell you but first thing to do is study the basic things on OLLYDBG :)

I already know how to hook, just give me an example of a dll file which will block the cheating applications.