Hi,
Am I correct that you are trying to suck from your old server to your new
one?
If so, specifying the port as you have is correct (nntp_feeder server:port
groups user pass).
There are three likely causes of this problem, and you can use telnet to
confirm these -
telnet new.server 119
The most likely cause is access.conf not permitting access. If this is the
case, you will see a permissions error.
Another possibility is a firewall not permitting the connection (Or not
permitting the connection to remain open after accepting it).
Finally inetd or another application may be using the port. If this is the
case, you will probably see an error in your startup logs indicating DNews
was unable to bind to port 553.
In each of these cases you will likely see the error you have given. If none
of the above helps, turn on debugging and send us the resulting dnews.log
showing an attempted connection -
tellnews loglvl debug
tellnews debug chan_read:chan_write:suck:
- Roydon L.
<[EMAIL PROTECTED]> wrote in message
news:<3e1c5bb9$1@netwin1>...
>
> I am moving my server to a dedicated host. My old news host runs on port
553, and my (new) news host also runs on port 553. The tellnews status
reports this error (when run on the new host):
>
> info: (11:34) NNTP closed unexpectedly {myold.host} check dnews.log
>
> The log does not offer much help. I suspected that the port number was the
problem, so I appended the port number to the suck address like this:
>
> myold.host:553
>
> And that has not helped. My question is this: How do I suck news from a
nonstandard port?
>
> -rk
>
