10060 error

[pantzoid]

Updated my Newsbin for Giganews version to 6 and although it does download the files, I get this 10060 error flagged up with every download. Any ideas ?

[Quade]

Sounds like at least on connection is failing to connect. How many connections are you using?

[pantzoid]

On the previous Gnews version I wasn't getting any errors. The settings were picked up from my old version which was set at 2 servers each with 25 connections. My account allows 50 connections.

[mho]

On the previous Gnews version I wasn't getting any errors. The settings were picked up from my old version which was set at 2 servers each with 25 connections. My account allows 50 connections.

Lower them (quite a:-)) bit.

When newsbin is done with a connection, it will sometimes close and re-open quicker than the server in the other end realizes, so it will "count" more connections than you actually configure. Unless you have very strange connectivity (or your ISP is purpously messing with you!), 4-8 connections should let you download with max speed.

Try setting each server to 4 connections!

- mho

[Quade]

I was thinking 10 per but, I agree with the "fewer connections is more reliable".

[pantzoid]

Thanks. I'll give that a go and post back whatever the outcome.

[pantzoid]

Tried 10 connection for each server and also 4 connections each server with restarts in between. Still got the errors. Any other ideas ?

[Quade]

What kind of connection are you using? Wired or wireless?

[pantzoid]

It's a wired connection. I haven't been suspect of the network state as it worked perfectly with the old newsbin.

[mho]

Tried 10 connection for each server and also 4 connections each server with restarts in between. Still got the errors. Any other ideas ?

Check the Server Address, for both servers. Maybe one of them is wrong? Do you have any trace of Giga's Accellerator? (It is not needed, anymore, and can only cause trouble)

- mho

[pantzoid]

Never used Giga's accel. Checking the server addresses was the first thing I done. It actually picked them up itself during upgrade so I didn't have to input them manually. I checked them again anyway but they are ok.

[pantzoid]

Finally seem to have fixed it. Had a look at the connections while downloading and noticed that it was exclusively one of the servers that was posting the error. I had recently (in old newsbin) changed the port on this server to 81 and it worked ok on it. This seemed to be causing issue and when I changed back to 563 on the new version it downloaded without error.

Thanks for all pointers.