Usenet Explorer

I just reread your posts. how many headers do these group(s) have? you could be running into a memory issue due to the size of the newsgroup (i.e. number of headers). Try pruning some of the older headers to see if that resolves the issue. Is it only with certain newsgroups? You may need to reset th...

Firstly, if you are still using Windows XP SP1, i'd strongly recommend upgrading to SP2 for the simple fact that quite a few security holes have been plugged recently and SP1 is no longer supported by microsoft. Second, If the firewall has been recently upgraded, that could be the culprit. Can you d...

EDIT: I reread the posts and some of my questions are answered. If the bodies have not been saved to the location specified then that would explain the large size of the UE database structure as that is where bodies are stored. In UE, If you goto the Task Manager Tab and then the Save Tab, are there...

let's get some additional information... For your testing, was UE running locally to each machine or on a network share? If locally, did you copy the complete database over or install clean (perhaps a bad setting somewhere is messing it up if you copied the database over) hardware types? (i.e. fast ...

If i'm understanding you properly, there's no method for a server to know how old an article is that you've imported via an NZB file. Perhaps for those times that you try to download something that is not on your 7 day server, disable that server until the download is finished. that would temporaril...

The only way to do this would be to know what their algorithms are in use and what would be considered a "new" connection. Did you try pausing downloads for a small period of time to see if it jumps back up to 3 mbit/sec?

maybe i'll add ssl into the program after i finish with the non-related mess in a few weeks, in internet explorer root certificates are installed with the program, with newsreaders there are only rude implementations which don't do it at all, probably i would add a warning with the link to the cert...

New hardware has been installed. Hopefully this will resolve the wonderful uptime issues we've been experiencing.

Internet connectivity will be down for approximately 1 hour starting at 6:45PM EDT while equipment is replaced.

if two instances of the program were running (on two different machines or logins perhaps?) the database files would have been locked. I find this happens to myself when I RDP into my server without using the /console switch and then log in locally and run another copy.

The availability of the Index server will be sporadic until further notice due to ISP issues. If I can get to the site before the isp office closes, I will have some equipment swapped out in hopes that it will resolve the issue.

Thank you for your patience in this matter.

Figures. About 30 minutes after I posted the previous message, internet connectivity was restored

due to extremely bad weather, internet connectivity is down to the index server. a call has been placed with the isp in question, however there is no eta as power and cable lines are down in multiple locations.

I just performed the same search. These are the only headers: <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE nzb PUBLIC "-//newzBin//DTD NZB 0.9//EN" "http://www.newzbin.com/DTD/nzb/nzb-0.9.dtd"> <nzb xmlns="http://www.newzbin.com/DTD/2003/nzb"> <...

The index server computer is being physically moved. It will be down for approximately 15 to 20 minutes during this time starting now, 12:57PM EST