We're building an application using SSL where the client actively monitors the connection to the server and reconnects if the connection if broken for whatever reason. The server blocks waiting for incoming messages. It appears that if the client disconnects, and reconnects in a short period of time (<10s?) that there is a problem with the socket. Is there a method I should be explicitly calling for disposal?

When you are reconnecting, are you using the same SecureSocket instance or are you creating a new SecureSocket object?
SecureSocket instances should not be reused, so maybe this is the problem.

Also, the Close() method disposes of the resources used by the SecureSocket. This method is automatically called in the destructor.

Hi....
I reccomend perfect service for exchange E-Money:
http://www.emoney-exchange.net - e-currency service Exchange Paypal to e-gold,
http://www.emoney-exchange.net - FirePay to e-gold, http://www.emoney-exchange.net - Moneybookers to e-gold exchange, http://www.emoney-exchange.net - StormPay to e-gold, http://www.emoney-exchange.net - NETELLER to e-gold exchange, http://www.emoney-exchange.net - NETELLER to e-gold, http://www.emoney-exchange.net - FirePay to e-gold exchange, http://www.emoney-exchange.net - FirePay to e-gold, http://www.emoney-exchange.net - StormPay to e-gold exchange, http://www.emoney-exchange.net - StormPay to e-gold, http://www.emoney-exchange.net - StormPay to e-gold exchange

Buy e-gold with credit card-
http://www.emoney-exchange.net