SABnzbd

Wiki

User Manual FAQ Contact Introduction Installation Configuration Scripts Advanced Topics Extensions for SABnzbd

Incorrect or missing information? Firewalls and Virus scanners

Firewalls

Firewalls are only too happy to interfere with a program's Internet communication.
Of course they don't tell you about this :)
So check your Firewall logging and settings.

SABnzbd uses the following types of communication:

Outgoing:
DNS traffic: during startup it may communicate with an external DNS server to find out network information.
It communicates with external Usenet servers (obviously!) (port 119 and maybe others).
It may communicate with NZB sites (port 80 and 443).
It may try to send email (port 25, 587 or others).
It may access sourceforge.net to check for the latest release (port 80)

Incoming:
Webserver: The user interface is a website, so SABnzbd has to "listen" on a port of your choise (default 8080).
Some firewalls will even complain about the use of localhost.

Virus scanners

Some virus scanner behave like firewalls, so look under "Firewalls".

Some virus scanners see SABnzbd as a problematic program.
Especially the sqlite3.dll file is disliked and some just remove that file.
SABnzbd needs sqlite3.dll to maintain its history database.

Further not all virus scanners handle large and growing files very well.
Suppose you are downloading a large ISO file, the scanner may want to scan every time a piece is added to the ISO.
It's probably better to disable the so-called on-access scan for all SABnzbd's working folders.
Your scanner's scheduled system scan will check for viruses later.
SABnzbd doesn't execute any downloaded file, so no viruses will be activated.

Windows 7

There is a serious bug in Windows 7 and Server 2008 that can make the combination of SABnzbd
and virus-scanners/firewalls problematic, due to heavy memory leaks.
Microsoft has released a hotfix for this that is not in the monthly patches.
Information: [http://support.microsoft.com/kb/979223/en-us]
Download of the hotfix: [http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=979223&kbln=en-us]