Maybe, and I mean maybe, it's my fault. I have a simple, straight-forward program that connects to a server, sends data to it and gets disconnected immediately and then connects again and so on, you get the point. I tested Win 10 and Win 7 as guest OSs, they both have this particular behaviour: after some number of disconnects new connection is never notified about disconnect (and I mean never, I can even turn off the server it was connected to and still nothing would happen). Socket just keep feeding data using send api and after send buffer is filled up it just gets stuck, WSAPoll don't get notification, nor FD_CLOSE message is received. This program, however, works perfectly on the same OS, but on a real hardware, socket never get stuck. So... 2 different guest OS have same exact behavior, while host OS don't have it. So the question is, does Workstation have something to do with it or it's just my poor coding skills and paranoia?
