Sophos Firewall blocking debugging on VS 2013

Hello Jess,

[t]he firewall log doesn't say much

does it say at least something and what? What is the error (firewall or other) they get. The solution in the MSDN community isn't very clear (and perhaps not quite correct in the details) - is the solution to disable the firewall (and the user didn't have the necessary rights initially) or has the behaviour changed after reinstall?

A blocked loop-back connection (if this is what's meant by a fake connection to emulate x64) should be recorded in the firewall logs together with the rule or the reason.

Christian

The firewall log makes no mention of Visual Studio or anything related to it, nor any mention of loopback connection. Disabling the firewall allows them to debug locally but that is not a solution for our organisation. The article says reinstalling worked but in our case it doesn't. 

I have attached a screen shot of the error they have when debugging. 

I found this article but not sure if it relates as the error mesage is different

http://stackoverflow.com/questions/21329899/vs2013-professional-local-64-bit-debugging-msvsmon-issue

Hello Jess,

any mention of loopback

is permitted in the default global rules. No SCF log entries at all from around the start of the debugging? Does disabling the firewall immediately allow debugging?

Christian

Yes, disabling the firewall immediately allows debugging. In the global rule, loopback is allowed by default but looking a the logs, there is no mention of it in the SCF. there are log enteries but just the usual blocks. Dropbox, Spotify etc

Hello Jess,

loopback in the global rule is to 127.0.0.1 only, but anyway a blocked connection should be recorded (though it's a single line and could easily be missed). Is this Windows 8? If not it might help to turn on interactive mode.

Christian

Yes it is windows 8. We have turned on Monitor mode but still no luck. I have asked the user to send logs of when firewall is disabled and when enabled to compare

Did you find a solution to this problem? Currently having same problem..

Ok I know this is a very old thread but I had been trying to figure out what the issue was for the last year. I was stuck on Windows 7 for my development machine. Because on Windows 8 and above I was not able to Debug due to this issue. Today was the day where we figured out the problem, with an unrelated product that was having similar issues. The solution was to unblock IPV6 traffic by default. Configure Firewall --> Primary Location -> Configure --> Global Rules --> now uncheck the checkbox at the top that Blocks all IPv6 traffic. 

I experienced this exact issue recently.  DevInDreams' solution does work; however, I am curious if Sophos can provide a way within the firewall policy to block all IPv6 traffic OTHER than loopback (::1).  It seems custom rules only allow you to specify IPv4 addresses.  Any suggestions?