Problem resolved!
Turns out the issue was caused by one of AV, IPS or WAF on the subnet involved. Later this week (hopefully tomorrow) we will try adding back the services one at a time to see which was causing the problem.
For reference, here is a screenshot of the error message
