A20 Dedicated server "INF [NM] DataReceived: bad!" messages spamming

anyone ever get a solution for this?

Or know why we're getting "INF [NM] DataReceived: bad!" while trying to connect to dedicated servers...?

 
Seeing your entire log would help but that error generally means that some of the data being sent/received is being blocked. Depending on if the error is in a client log or a server log will determine which advice is given to you. It's best if you start a thread for your own problem versus tagging on to someone else's thread. Use the pinned topic at the top of the forum for instructions on how to post your logs. Post a copy of a client log and a server log if possible and they should contain the error that you're seeing. The solution to your problem needs more info than just that single line of the error to diagnose your problem.

d3mo said:
anyone ever get a solution for this?

Or know why we're getting "INF [NM] DataReceived: bad!" while trying to connect to dedicated servers...?
Click to expand...

 
i have a windows server that was running fine on A20.1 B5. i updated it to B6 today and starting getting spammed with the "INF [NM] DataReceived: bad!" error. i shut down my server, rebooted it, restarted the 7 Days server and no more errors. hope this helps someone.

 
I've been beating my head against this issue for a few weeks, the same server that is throwing this error has hosted 7d2d through various alphas but now even with 'everything default' dedicated server and the machine set as DMZ host in my router (a step that was previously unnecessary) it's still not working. Are there any dev threads on this issue that anyone can point me to?

 
Ok, I had this problem with "INF [NM] DataReceived: bad" and it was because I was logged into steam on my client PC and my server PC. I shut down steam on the server PC and have not had the problem since and my 7d2d server runs just fine without steam running on the server PC.

 
When I encountered a similar problem, I used wireshark to capture packets. Obviously, my server port was 26900, and someone was attacking port 26902. The processing method is to limit the processing of port 26902 requests, and limit the requests per IP per minute to less than 50, so that this problem can be solved! No matter which external port you are using, limit its +2 port requests

20220713171048.png

 
You must log in or register to reply here.
Back
Top