I don\'t know if I have all the information needed to phrase this question well, so bear with me.
I have a local web page (local meaning 192.168.*) that is protected
I've hit this issue myself when dealing with Ssl3, though I'm not sure if the same advice would work for SSL2?
To work around the issue I set the Ssl3 flag on the security protocol like so:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;
Check out these links for more details:
system.net.servicepointmanager.securityprotocol on MSDN
security protocol enumeration on MSDN
They might point you in the right direction if you're lucky :)