Socket Error #10061

I keep getting an error when I connect to any group. The error is "Socket Error #10061 Connection Refused". I've ensured the correct port is open using the port checker on portforward.com. I only get this error message when I enable SSL. When it's disabled, it works fine. I have also tried with a different port that I know is open, and it still gives me the same error. I have two clients that I've tried with this, and they both give errors when SSL is enabled. They are Grabit and Thunderbird. I've tried turning off all of the firewalls on the modem and router, and disabling anti-virus protection, and I still get this error message. I'm not sure why I keep getting this. Thanks for any help!

Quote:

---

Originally Posted by Scott-IM

I keep getting an error when I connect to any group. The error is "Socket Error #10061 Connection Refused". I've ensured the correct port is open using the port checker on portforward.com. I only get this error message when I enable SSL. When it's disabled, it works fine. I have also tried with a different port that I know is open, and it still gives me the same error. I have two clients that I've tried with this, and they both give errors when SSL is enabled. They are Grabit and Thunderbird. I've tried turning off all of the firewalls on the modem and router, and disabling anti-virus protection, and I still get this error message. I'm not sure why I keep getting this. Thanks for any help!

---

You are connecting to the right SSL port (it's usually different than the non-SSL) plus that your usenet provider/plan supports SSL?

on a side note you shouldn't need ports forwarded or your firewalls and antivirus down for usenet.
just check your usenet provider, make sure you are connected to the right ssl address and port.

You don't mention if SSL has worked before, or if this is a new account and you're trying to set it up for the first time.

"Connection Refused" means that you do not have authority to connect and the server is actively rejecting your attempt, either from wrong username/password (obviously not the case here if non-SSL works) or more likely - SSL is not authorized on your account.

Most ISP-provided usenet will not include SSL, and many pay-providers charge extra for SSL. I suspect that's the case here.

Yeah, I'm just using Usenet for the first time. My ISP is Windstream, and they automatically give us access to news.windstream.net. They also do not need a username or password to log in. So what I'm understanding is that Windstream may or may not provide SSL? So I need to check/call to see if they include SSL or not?

You should ckeck whether they provide support from ssl or not.

I don't know of ANY ISP that has ever offered SSL usenet. It's possible, I guess, but I highly doubt it. (The primary function of SSL in usenet is to keep your ISP from snooping or throttling you, so a ISP-provided SSL service sort of defeats the whole purpose, don't you think?)

And the fact that SSL does not work for you only reinforces that belief.

Alright, I gave them a call and they said they do not offer SSL, like what was said above. So, my next question is it still safer to use Usenet over torrents, even without the SSL?

Using Usenet to download files is about as close to being 100% safe from copyright complaints as it's possible to be. SSL has no effect on this one way or the other - it is primarily to prevent 3rd-party eavesdropping.

However, if you are downloading patently illegal material (such as Adult porn in China, pro-Nazi material in Germany, or child-porn in the USA) be aware that the government or ISP has the technical ability to see everything you are downloading (or being tipped off by preset 'triggers' in the data stream) unless it is transferred over an encrypted connection.