Frequent error-codes and messages

by Obbe-Jan Bakker

Hamster-Logfile

Start of local XXXX-server failed

The given local server could not be started, mostly due to another program which is already using the port-number, e.g. a virus-scanner for mails like "Norton's AntiVirus" (NAV), which itself works like a POP3-server.

As no two servers can use the same port-number at the same time, you have to configure one of the programs to use another port-number.

Hamster-Replies

500 Permission denied - closing connection. [local NNTP/SMTP]

-ERR Permission denied - closing connection. [local POP3]

The connecting IP-address is not permitted to access Hamster's local server. See IPAccess.hst for details.

500 Permission denied (not authorized by POP3). [local SMTP]

Hamster's local SMTP-server is configured to only grant access after client has authenticated itself by a successful POP3-login

See SMTP-after-POP3 for details.

WinSock-Errors

10048 WSAEADDRINUSE

Possible reasons:* Firewall prevents local Hamster-servers from starting.

10049 WSAEADDRNOTAVAIL

The server is known but could not be reached

Possible reasons:

* You are/were not "online", i.e. not connected to the internet.
* Internet-connection was interrupted.
* The server is temporarily down - try again later.

10053 WSAECONNABORTED

Possible reasons:* Internet-connection was interrupted or lost while connecting to remote server was still in progress.

10061 WSAECONNREFUSED

Possible reasons:

* The Hamster-server is not activated (see Menu: Local / Start/Stop Server... and Menu Configuration/Local Server&Accounts/ Mails and News.

* The Hamster-server failed to start (restart Hamster and look out for "red" errors).

* The default port-settings for the Hamster-server and/or the newsreader/mailclient were changed and are not equal any more.

* The port-number is blocked by a firewall.

10065 WSAEHOSTUNREACH

Like 10049 above, but the connection was lost after a valid connection to the server.

10071 WSAEREMOTE

Possible reasons:* Connection-request was refused by remote server because you are not permitted to use it with your current internet-connection, e.g. to access the server of provider X you have to dial-in to provider X.

11001 WSAHOST_NOT_FOUND

Possible reasons:* A server with the given name could not be found - perhaps you've misspelled it.


Unable to open file