We recently found an issue dealing with Microsoft Firewall Client and are currently working with Microsoft to determine a feasible workaround. Just disabling the firewall client doesn't work as the problem is the very existence of the firewall DLLs being installed. When you install Microsoft Firewall Client, it installs the FwcWsp.dll which is hooked onto every process that does anything with Winsock. Every winsock command that is sent goes through this DLL. We found the hacky solution was to remove the entire software from the client system, or just cut and paste this DLL to some other location.
Did your IT department just install some new Windows patch or update that installed this software on your system. We have seen several customers recently getting this software installed and I was curious if you could help provide some insight.
Since the behavior you are seeing isn't related to the firewall client software, we are going to need to take this issue offline so we can provide you with some debuggable DLLs. I need your permission to get your contact information from our web support team unless you are okay with posting your email address here.
