Windows socket error due to firewall/antivirus software (?)

[aaaaalbert]

During a Sensibility Hackathon, a Windows 8 user ran into a socket error 10013 when uploaddirring files. The error message said that "an attempt was made to access a socket in a way forbidden by its access permissions".

See this Microsoft forum discussion for a lead on firewall/antivirus software. The Windows Socket Error Codes docs from MSDN say that

WSAEACCES (10013) --- Permission denied.

An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

---

Help in replicating the problem would be appreciated!