Thank you for providing some independant verification that NetworkComms.Net is not the primary issue here. Unfortunately, and this is something we have dealt with in the past, networking can be VERY os specific. As such an implementation that works on one may not work on the other. These are also amongst the most tricky problems to solve without potentially breaking something else. We can only apologise again for the delay in finding a comprehensive solution to this problem, we understand how frustrating these issues can be. We are working on this issue, amongst others, and hope to have a suitable fix soon.