Subj : Re: Synchronet configuration for fsxnet features
To   : smooth0401
From : Avon
Date : Wed Jul 31 2024 13:58:50

On 30 Jul 2024 at 07:13p, smooth0401 pondered and said...
 
 sm>   7/18  10:30:54a  BINKOUT Attempting callout for 21:2/116@fsxnet, file:
 sm> C:\sbbs\fido\outbound.015\00020074.cut
 sm>   7/18  10:30:54a  BINKOUT JSBinkP/4 callout to 21:2/116@fsxnet started
 sm>   7/18  10:30:54a  BINKOUT connecting to 21:2/116@fsxnet at undefined
 sm>   7/18  10:30:54a  BINKOUT Connecting to 21:2/116@fsxnet at
 sm> f116.n2.z21.fsxnet.nz:24554
 sm>   7/18  10:31:05a  BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554
 sm> failed (Error: Unable to connect).

Rob I think this fail to connect may be related to the fsxnet.nz DNS failing at the time you polled. I have had a power cut (planned) at my home and that shuttered the DNS server I run. I have another planned (and hopefully final) power cut due to occur tonight my time for approx 24 hours.

I'm downing my systems as I am having an electrician coming in to do a chunk of wiring while I am work tomorrow...

All of which is to say this may be the cause of this aspect of your issues but for the wider Synchronet stuff I'm not sure.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz 

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.