03 Oct 23: One server has been relocated, the server currently doesn't have a public IP address in the meantime. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform (since around 24 July 2008). In the unlikely case I disengaged the server because of some problem the retention is 1200-3800 days depending on newsgroup. If you experience any issue please let me know.
29 Nov 23: Because of encrypted and "obfuscated" flood mass posted by few nzb websites and newzbin-like communities using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic, since posts are disguised in such a way, that users must use the satellite ecosystem (whish is not a part of Usenet) exclusively to download them, when the website disappears - the encrypted scattered posts just eat usenet providers' disk space uselessly. If you can't find something specific please let me know what exactly you can't find for me to check how it is possible to retain the posts. Legible posts shouldn't be affected at all, let me know if you notice anything missing.
08 Aug 24: After being unchanged for many years the search service communication protocol had to be updated a few times in part to resolve a server side set feature limitation and properly handle trial searches on the relocated server. The searches themselves are not affected and it looks like the work is now complete.
15 Mar 25: It looks like the search service is currently down as there are no pings. The other server is no more on starlink, but the search requests are still routed and the access to it is through the first server, since it is safer, but the direct access is no problem if this will be a repeated issue. The connection will be restored or server restarted as soon as possible.
16 Mar 25: One server is currently still down, the other server was reconfigured and already connected directly, so the search service is running with minimum possible retention gaps.
yes back then the computer with the server locked and had to be restarted. also the hard drive needed to be defragmented. database intact, it is working since then.
restarted, i improved things quite a bit, there were few words like par2 which weren't searched well when the exact file name is entered, i fixed that.
i'll check bug reports with v2.1, i'm planning to release version with changed protocol version, we have now a lot of parasite server users through server trial hack using newsleecher as client, it shouldn't happen again since i got an agreement from the hack author (otherwise the option to close the server for trial accesses for import header stage will be the most real possibility, i don't want to play a cat mouse game, for registered version a serial derivative is used to protect data so it is not possible to hack). the problem is continues already for some time, i just was sick so work wasn't moving well, but all appears to be better now.
Marten Fokkens wrote:I receive this message since a few hours:
"Search failed
No connection could be made because the target machine
actively refused it. (System: 10061)"
Probably still applying the microsoft hotfix?
Dutch? Visit the Dutch UE/Newspro forum at: http://www.binaries4all.nl
Nederlandse UE handleiding op http://www.binaries4all.nl/ue
English UE tutorial online at http://www.binaries4all.com/ue/
Handy links at: http://jpfx.zapto.org/
