Made the changes & did a manual poll of one of my hubs. Didn't work...but it did attempt it. Here's the log of it:

! 04 May 12:34:11 [1] binkd.cfg: 38: d:\fe\inbound\insecure: incorrect directory

Made the folder & went away.

! 04 May 12:35:27 [1] binkd.cfg: 39: inbound-temp: unknown keyword

Changed this from inbound-temp to temp-inbound & went to the steps below.

04 May 12:36:48 [1] BEGIN, binkd/0.9.4 binkd.cfg
04 May 12:36:48 [2] clientmgr started
04 May 12:36:48 [1] servmgr started
! 04 May 12:37:27 [1] got signal #4.

04 May 12:39:40 [1] BEGIN, binkd/0.9.4 -P3:770/1 binkd.cfg
04 May 12:39:40 [1] creating a poll for 3:770/1@fsxnet (`i' flavour)
04 May 12:39:40 [2] clientmgr started
04 May 12:39:40 [1] servmgr started
+ 04 May 12:39:40 [3] call to 3:770/1@fidonet
04 May 12:39:41 [3] trying 219.89.83.33...
? 04 May 12:39:41 [3] unable to connect: No route to host
+ 04 May 12:40:40 [3] call to 3:770/1@fidonet
04 May 12:40:40 [3] trying 219.89.83.33...
? 04 May 12:40:40 [3] unable to connect: No route to host
! 04 May 12:40:49 [1] got signal #6.

Tried another hub as well...but got the same information. Looks like it's running & trying to connect. Where do I goto now?

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

Re: Think I had it running...
By: Don Lowery to All on Mon May 04 2020 01:02 pm

04 May 12:39:41 [3] trying 219.89.83.33...
? 04 May 12:39:41 [3] unable to connect: No route to host
04 May 12:40:40 [3] trying 219.89.83.33...
? 04 May 12:40:40 [3] unable to connect: No route to host
Tried another hub as well...but got the same information. Looks like it's running & trying to connect. Where do I goto now?

Those errors indicate that a link is down - either yours or something further upstream.

A good test to know if it is you or further, is to ping your default gateway (if you can figure that out) - or something like 8.8.8.8
...����

... The man who strikes first admits that his ideas have given out.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

04 May 12:39:41 [3] trying 219.89.83.33...
? 04 May 12:39:41 [3] unable to connect: No route to host

Those errors indicate that a link is down - either yours or something further upstream.

Being that Mystic works...it's on my end. Fixing to head to work in a
few...but knowing what the error is...can stew on it for the day & come back
& try something else. Thank you for the information!

A good test to know if it is you or further, is to ping your default gateway (if you can figure that out) - or something like 8.8.8.8

Will do later on this afternoon. At least having a route to go to test the situation is better than using a Ouija board to figure it out.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)