On Saturday, April 24, 2010 9:58 PM , Dmitry Konnov <[email protected]> wrote:
> Hi All, > > I have a problem, > I can not Bind port at server application startup for listening > if active clients are trying to connect to this port number. > > If i manually plug off of Networking cable then clients are > physically cut off and nothing bothers for server application to > Bind > listening socket. > > Is that possible to implement programmatically? It is a bad approach, IMHO. What was/is the error code reported by bind()? You should be able to bind the port each time it is not used (if you have the right to do it). There maybe some other rather strange reasons (like buggy firewall/ AV scanner causing the TCP/IP API working improperly) too. I have already observed AV scanner with a bug which was the reason for crazy WinSock API behavior. Regards D. Toman ------------------------------------------------------------------------------ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
