Barry wrote:
> Hi Nigel!
> > NR> + 05 Jan 20:43:58 [1098507] call to 454:1/1@ilink
> > NR> 05 Jan 20:43:58 [1098507] trying cfbbs.no-ip.com
> > NR> [173.61.230.164]:24554... ? 05 Jan 20:43:59 [1098507] connection
> > NR> to 454:1/1@ilink failed: Connection refused
> > I'd refuse to answer at quarter to nine at night too! <bseg> To me
> > "connection refused" is a relatively vague error message -- wrong user
> > name? wrong password? wrong port? Password might look right but has a
> > space at the end. Bad command line is a possibility: there are multiple
> > punctuation characters which look the same to a human but are radically
> > different to a computer -- I'm thinking single and double quote, double
> > hyphens will turn into dashes, etc.
> NR> Connection refused means the other end won't accept my incoming
> NR> connection for some reason. The service may not be running,
> NR> blocked by a firewall, routinng issue. Nothing to do with
> NR> username, it's not got that far.
>
> Right -- I haven't had too much experience with various communications
> protocols; for the stuff I do manually usually I have one combined
> command line to enter the username, password, IP address and if
> necessary port.
> > I tried a quick Google search for "1098507" -- at least ten pages of
> > hits. Tried specifying with Synchronet but that got zero hits; so assuming
> > a different communications transport.
> NR> That's the child pid of the binkd thread that is calling out. It
> NR> helps to track the process in the log file when multiple calls
> NR> are placed at once.
>
> No wonder I couldn't find anything!
I'm still trying to figure out how I'm able to send replies if I cannot connect.
This is an odd state. Maybe we should continue this via
email/netmail.
--- SBBSecho 3.12-Linux
* Origin: ILink:End Of The Line BBS - endofthelinebbs.com (454:1/5016)
|
