http://bugs.winehq.org/show_bug.cgi?id=31994
--- Comment #11 from Bruno Jesus 00cpxxx@gmail.com 2012-10-21 08:00:28 CDT --- (In reply to comment #10)
could You tell me some advice(s) how can I do some more detailed tracing inside WS2_sendto function to check exactly where and why it set WSAEACCESS error? E.g. where could be useful to add some more TRACE into winsock code and which information there are important etc... (I have some C language knowledges but I have no idea about (win)sockets...)
I guess that the application is sending a broadcast packet to 255.255.255.255 which behaves differently from windows, in linux it does not work and return the EPERM error. You can dump the "const struct WS_sockaddr *to" parameter from WS2_sendto using the helper function *debugstr_sockaddr to check that.