Wv>> + 02 May 22:45:54 [630] call to 1:261/38@fidonet Wv>> 02 May 22:45:54 [630] trying filegate.net [72.43.242.234]... Wv>> ? 02 May 22:45:54 [630] connection to 1:261/38@fidonet failed: Wv>> Connection refused
WD> Here's a log extract ... a session 10 minutes before your example and WD> one 5 minutes after your example .. works excellent ...
WD> + 02 May 22:35:19 [9884] call to 1:261/38@fidonet WD> 02 May 22:35:19 [9884] trying filegate.net [72.43.242.234]:24555... WD> 02 May 22:35:19 [9884] connected WD> + 02 May 22:35:19 [9884] outgoing session with filegate.net:24555 WD> [72.43.242.234] - 02 May 22:35:19 [9884] SYS Prism bbs - 02 May WD> 22:35:19 [9884] ZYZ Janis Kracht - 02 May 22:35:19 [9884] LOC WD> Slaterville Springs, NY
WD> + 02 May 22:55:19 [7240] call to 1:261/38@fidonet WD> 02 May 22:55:19 [7240] trying filegate.net [72.43.242.234]:24555... WD> 02 May 22:55:19 [7240] connected WD> + 02 May 22:55:19 [7240] outgoing session with filegate.net:24555 WD> [72.43.242.234] - 02 May 22:55:19 [7240] SYS Prism bbs - 02 May WD> 22:55:19 [7240] ZYZ Janis Kracht - 02 May 22:55:19 [7240] LOC WD> Slaterville Springs, NY
Janis' system is refusing connections on the standard BinkP port (24554.) It is, however, answering them on an alternate port (24555) with BBBS. Her BBBS setup is presenting both 1:261/38@fidonet and 1:261/100@fidonet as AKAs, among others. To fix the problem, she needs to either open port 24554 for BinkP connections, or update her nodelist entry to reflect the alternate port by replacing IBN with IBN:24555. 1:261/100 is listed with the alternate port, so apparently it was an oversight on her part or her NCs.
