http://bugs.winehq.org/show_bug.cgi?id=31994
--- Comment #10 from Starous starous@volny.cz 2012-10-20 18:17:29 CDT --- (In reply to comment #9)
(In reply to comment #8)
Just out of curiousity... You don't happen to have a really aggressive firewall setup, do you? Error 10013 corresponds to WSAEACCESS, which usually indicates a permissions problem.
No, AFAIK I don't use any firewall and I have default iptables setting. When I start e.g. Wine iexplore.exe, it works fine.
But, if it may be important, I have two network cards, from some historical reasons. First one (eth0) has fixed IP address and it is connected into home network, second card (eth1) is connected into internet (via router) and it is configured via Network Manager and DHCP. There is NO routing between these cards (e.g. for internet sharing etc.). Additionally there is also some network interface named pan0 - I don't know exactly what it is, maybe it is some virtual interface of Oracle VirtualBox (or maybe of N2N). This "card" has no IP address.
Hi Erich, 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...)