newsbin.com

Hi,

I've been having this issue for awhile since starting to use version 6 beta. When downloading headers in a group it downloads 100,000 or so and then I get the following error:

[19:18:20] ERROR - SSL Read Failed: 10060A connection attempt failed because the connected party did not properly respond after a period of time, or established connect
[19:18:20] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Compressed Headers - Timeout Waiting for Server to send Data: Socket - Read or Write Timeout
[19:18:20] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout
[19:18:56] ERROR - SSL Read Failed: 10060A connection attempt failed because the connected party did not properly respond after a period of time, or established connect
[19:18:56] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Compressed Headers - Timeout Waiting for Server to send Data: Socket - Read or Write Timeout
[19:18:56] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout
[19:19:36] ERROR - SSL Read Failed: 10060A connection attempt failed because the connected party did not properly respond after a period of time, or established connect
[19:19:36] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Compressed Headers - Timeout Waiting for Server to send Data: Socket - Read or Write Timeout
[19:19:36] ERROR NNTPSocket news-europe.giganews.com - NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout

Is there a setting I can set so that the headers will continue to download automatically if a timeout occurs?? It seemed to do that with version 5.5.

Thanks

Did you ever find out what the problem was and how to fix it?

Typically it's your virus scanner or firewall. I'd suggest making the V scanner ignore the Newsbin data folder and the traffic between Newsbin and the news server.

What version are you using?

Hi. Different poster.....

I'm having the same problem with Newsbin 6. Not sure if it is my usenet service provider, newsbin itself, or the machine. Service provider is PowerUseNet.


[16:21:35] ERROR NNTPSocket - Server:news.powerusenet.com NNTPServer: Compressed Headers - Connection Failed while reading Data: Socket - Read From Server Failed
[16:41:42] ERROR NNTPSocket - Server:news.powerusenet.com NNTPServer: Compressed Headers - Connection Failed while reading Data: Socket - Read From Server Failed


Running Newsbin 6.30.b5.1795, but I've seen the failures on most versions of Newsbin 6.2x. Have been hoping it would go away in an update, but no joy.

Details about the computer:
Processor: AMD Athlon II X4 640 Processor, 4 cores, 4 threads, 3.00Ghz
Mainboard: BIOSTAR TA890GXE, Socket AM3
RAM: 4.00GB PC3-10700, 667Mhz, 3.25GB usable, NB/HT-Link Freq: 2000Mhz
OS: Windows 7 Ultimate SP1, 32-bit
Graphics: ATI Radeon 4290, 384MB
Net: Verizon FiOS, 25/25Mbps

I am using AVG Free 2012.0.1913 as my antivirus. Told AVG to ignore the folders where newsbin's files are kept. Unfortunately, it doesn't appear to have helped. Anything else I can do on my side to help isolate the problem?

Regards,

...three additional errors posted by NB while I was composing the previous message:


[17:00:14] ERROR Socket - Error: WSARecv Socket Error Code: 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[17:00:14] ERROR NNTPSocket - Server:news.powerusenet.com NNTPServer: Compressed Headers - Timeout Waiting for Server to send Data: Socket - Read or Write Timeout
[17:00:14] ERROR NNTPSocket - Server:news.powerusenet.com NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout

NB shows two Usenet News Groups, that haven't downloaded properly. I didn't delete them from the download queue after the previous errors.

Regards,

Well, you need to tell it to ignore the network connections Newsbin makes to the news server.

I'd try alternate ports too if PowerUsenet supports them. Change the port (in the server options), restart Newsbin and test.

Thank you for the reply. Have tried different port numbers with no success. Not sure how to get AVG to ignore internet traffic to/from a specific web site.

Completely disable the thing. Test that it works fine. Now you know for a fact it's the source of your problem. You can go the the av software support site and ask the same question, you're more likely to get a walkthrough there. There's also google, which is probably faster. Odds are it's more about getting whatever you've installed to ignore Newsbin, as opposed to other sites, but it depends.

DT

OK, to eliminate the possible issue with AVG, I uninstalled it and restarted the system. I also made sure that Windows defender was turned off. I'm still getting the timeouts. It didn't help.

What should we try next, please?

Regards,

Probably the next step is the router. Also, double check your windows firewall has allowed newsbin (the installer normally does this for you automatically unless something went wrong). Basically, something is preventing newsbin from talking to the server, so you need to go through anything that might be responsible for that and fix it. For the vast majority of users, it 'just works', but if you've got a more buttoned down security setup on your network, then intervention is required. The AV was chosen first simply because the vast majority of these problems are traced to AV.

DT

Yeah router is a possibility.

I don't really know. Why can I download headers (I use them pretty much exclusively) with no timeouts and you get timeouts. It's not clear at all. I might try checking "disable XFeatures" in the server options, restart and then see if this changes the symptoms.

I assume you're connected to the net through an Ethernet cable? Wifi isn't really designed for long term connections like this.

Do they eventually download? I mean connection issues that still allow things to work can probably be ignored.

I'm pretty much baffled, myself, Quade.

I tried to disable Xfeatures a while ago and that didn't help. I'm running 1GB/s hard wired Ethernet in the house. I recently converted to FiOS TV and got a new router as part of the package. I'm running their Series 3 9100EM, now (I was running FiOS Internet before the upgrade). Line speed is 25/25 Mbps and I typically get 30 MB/s when NB is running at full speed. The new router didn't help. If this was a firewall issue, I would have expected a complete block/failure of the session between myself and PowerUseNet.

Most of the groups I subscribe to download perfectly. It's just one or two of the really big volume groups that are giving me trouble. I even tried deleting and then re-adding the biggest troublemaker and that didn't help. The only other thing I can think of is if this has something to do with Jumbo Packets or packet frames. Is there anything in Newsbin that would cause it to choke on a large packet (> 1500)? I'll go back and make sure I don't have anything in the network configured for jumbo packets, just to be sure. Looks like I may need to make friends with WireShark again and do some serious packet surfing.

There's also still the possibility that there's something going on over at PowerUseNet. However, if that was the case, I suspect there'd be a lot more people than me complaining.

Thanks for all the advice, guys. Despite the issues, I'm still a satisfied NB user. I can live with the nuisance, but the developer in me wants to figure this out.

Regards,

I think packet sizes is too low level to matter to newsbin. It's relevant that only the large groups give you grief. I wonder if it's just a problem with a sustained transfer of a single call i.e. a single range of headers being asked for, it's done in one interaction with the server, and the weak spot in the infrastructure breaks before it's done? I suppose it's possible it's some sort of imposition by the isp, but personally I'm doubting that. Odd one.

DT

Hey, guys. Wanted to follow-up on this thread. For reasons I can't explain, this problem cleared up around the time you released v6.30.1832. When I installed the build, virtually all of the time-outs went away. I can't tell whether it was something in the release or something in the environment that changed. I chose to wait a while to be sure the problem didn't come back, again. I can only tell you that NB is running fine.

Thanks for staying with the thread while you did. The bottom line is that everything is working well, again.

Best regards.

That's good to hear. Astra had an issue today. Some hardware failure that was causing timeouts. Looks like it's fixed now.