Agree completely with Richard.J

In fact, SO_REUSEADDR raises a security issue that MS addressed in a newer option called SO_EXCLUSIVEADDRUSE, as described here: "Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE" at http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx