See if Re: Winsock is busy long time after disconnecting to remote Message #843906 helps.
>
>I've downloaded the winsock example from msdn. I've adapted it and created separate Client and Server applications, which are both running on my laptop.
>
>Problem is that when the Client disconnects (.object.close) the Server.object.state gets stuck at 8 (Peer is closing the connection) and the server is never able to accept a new connection.
>
>When I threw a messagebox into the winsock "close" method, the messagebox was perpetually called and I'm forced to kill the app...
>
>What do I need to do to work past this so the server can accept a new connection?
>
>Many thanks,
>
>Ellis
>
>P.S. I'm running XP Pro SP2 and VFP 8.0 SP1