Usenet Explorer

I did the automatic update to 2.9.1 64 bit. After that I could get nothing to download. It's like it wasn't even connected.

I put 2.9 back on and it started working again.
I got the same result on the 32 bit side.
Couldn't even manually download headers.

I'm using Giganews Accelerator because it acts as a good middle man managing connections between UE and another reader.

edit: I tried the fix about unchecking compression in general properties. That's not it. It won't connect downloading headers or bodies.

check it is not firewall blocking access.

you should see some errors in tasks menu -> task manager, a red question sign tab, you should also see mishaps/errors in the console tab when downloading article bodies.

I just put 2.9.1 back on to try it. Attempting to download headers I get no error in console. Just a red dot on the ng.

When trying to download bodies through GN accelerator I get error 10061.

If I put 2.9 back on it will just work.

edit: just put 2.9 back to make sure. Download and save bodies works as normal at full bandwidth. Downloading headers works.

I'm wondering if it is another giganews accelerator bug or wrong setup instructions. I now see they advice on their giganews accelerator page "Change the news server address in your news client to "localhost" ".

The question if you named server connection to giganews accelerator as "localhost" do you also have IPv6 installed?

If you have IPv6 installed on your system, localhost for IPv6 capable applications means ::1 which is IPv6 localhost (Usenet Explorer v2.9.1 is IPv6 capable, v2.9 and earlier versions are not) and giganews accelerator is listening on 127.0.0.1 which is IPv4 localhost, it is unlikely to listen on both ::1 and 127.0.0.1 since it should be done explicitly, then it would be their bug.

If you defined the server name as "localhost" launch command prompt and type "ping localhost" it will show where it connects.

If it is ::1 it means you have IPv6 installed, then change "localhost" to "127.0.0.1" (in the servers pane advanced->rename, don't forget the port if it is not 119).

Here in WinXP "ping localhost" pings ::1 even as there is localhost 127.0.0.1 association in the windows hosts file, maybe it is the same in Vista and Win7.

127.0.0.1 fixed it. Thanks alex.

i'll check it out, if there are both IPv6 and IPv4 resolutions of the name as it is the case with the localhost maybe UE should choose IPv4, since it is less overhead (unless IPv6 network will be in place and IPv4 should be routed over IPv6, but probably by then as a rule there will be no IPv4 choice).