From Newsgroup: alt.bbs.synchronet


Hello everybody!

In trying to connect to a Synchronet system usin BinkIT as a mailer.
I keep getting the following error when trying to connect:

+ 02.19.2021 21:05:34 1-RB Socket read status 113
+ 02.19.2021 21:05:34 1-RB Socket read result 113
+ 02.19.2021 21:05:34 1-Connection lost
+ 02.19.2021 21:05:34 1-Authorization failed
+ 02.19.2021 21:05:35 Polled 1 systems

We have an agreed upon session password in use. This is a Mystic to
BinkIT connection being attempted. As I recall this has to do with the authorization process. Any thoughts on where the problem might be?

Jeff


--- Mystic v1.12 A47/LNX (2020/12/04) GoldED+/LNX 1.1.5-b20170303
* Origin: Region 14 IP Server - ftn.region14.org (1:14/5)
--- Synchronet 3.19a-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Jeff Smith
Re: Authorizion Errors?
By: Jeff Smith to All on Fri Feb 19 2021 09:22 pm

Hello everybody!

In trying to connect to a Synchronet system usin BinkIT as a mailer.
I keep getting the following error when trying to connect:

+ 02.19.2021 21:05:34 1-RB Socket read status 113
+ 02.19.2021 21:05:34 1-RB Socket read result 113
+ 02.19.2021 21:05:34 1-Connection lost
+ 02.19.2021 21:05:34 1-Authorization failed
+ 02.19.2021 21:05:35 Polled 1 systems

We have an agreed upon session password in use. This is a Mystic to
BinkIT connection being attempted. As I recall this has to do with the authorization process. Any thoughts on where the problem might be?

The log output from your side would be helpful, but yes, it looks to be a session password issue.
--
digital man

Sling Blade quote #16:
Karl Childers (to Doyle, re: lawn mower blade): I aim to kill you with it. Mmm. Norco, CA WX: 57.9øF, 42.0% humidity, 2 mph SSE wind, 0.00 inches rain/24hrs --- Synchronet 3.19a-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Digital Man

Hello Digital!

In trying to connect to a Synchronet system usin BinkIT as a
mailer. I keep getting the following error when trying to connect:

+ 02.19.2021 21:05:34 1-RB Socket read status 113
+ 02.19.2021 21:05:34 1-RB Socket read result 113
+ 02.19.2021 21:05:34 1-Connection lost
+ 02.19.2021 21:05:34 1-Authorization failed
+ 02.19.2021 21:05:35 Polled 1 systems

We have an agreed upon session password in use. This is a Mystic to
BinkIT connection being attempted. As I recall this has to do with
the authorization process. Any thoughts on where the problem might
be?

The log output from your side would be helpful, but yes, it looks to
be a session password issue.

I polled the system moments ago. Here is a log of the poll attempt:

--------------------- POLL v1.12 A47 2020/12/04 Sat, Feb 20 2021 (loglevel 3) + 02.20.2021 04:05:08 Poll BINKP node via address lookup: 1:282/9999
+ 02.20.2021 04:05:08 1-Polling 1:282/9999 on slot 1 via BINKP
+ 02.20.2021 04:05:08 1-Connecting to filecabinet.ddns.net on port 24554
+ 02.20.2021 04:05:09 1-Using address 188.193.24.47
+ 02.20.2021 04:05:09 1-Connected by IPV4 to 188.193.24.47
+ 02.20.2021 04:05:09 1-RB Socket read status 113
+ 02.20.2021 04:05:09 1-RB Socket read result 113
+ 02.20.2021 04:05:09 1-Connection lost
+ 02.20.2021 04:05:09 1-Authorization failed
+ 02.20.2021 04:05:10 Polled 1 systems

I should note that this system is not yet in the nodelist as he is in the process
of joining Fidonet and I was/am helping him get setup and his connection abilities
verified prior to assigning him a node number. I asked him what session password he
would prefer to use. I implemented the session password that he provided me and asked if he had installed the same password on his end and he responded in the affirmative. I also tried polling him with the agreed upon session password removed on my
end and the poll log entry is exactly the same as the above log entry. For the sake
of checking polled another Synchronet system that also uses BinkIT and I could connect
fine. I will also be posting a query in the Mystic support echo on the subject.

Jeff


--- Mystic v1.12 A47/LNX (2020/12/04) GoldED+/LNX 1.1.5-b20170303
* Origin: Region 14 IP Server - ftn.region14.org (1:14/5)
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Jeff Smith
On Sat 20-Feb-2021 4:12 , Jeff Smith@1:275/201.0 said to Digital Man:

I should note that this system is not yet in the nodelist as he is in the process
of joining Fidonet and I was/am helping him get setup and his connection abilities
verified prior to assigning him a node number. I asked him what session password he
would prefer to use. I implemented the session password that he provided
me and
asked if he had installed the same password on his end and he responded in the
affirmative. I also tried polling him with the agreed upon session
password removed on my
end and the poll log entry is exactly the same as the above log entry. For the sake
of checking polled another Synchronet system that also uses BinkIT and I could connect
fine. I will also be posting a query in the Mystic support echo on the subject.

Jeff

The issue sounds like a password issue. I have used Mystic and several other bbs software to exchange FidoNet mail and it worked for me.
--- CNet/5
* Origin: 1:275/201.0 (1:275/201.30)
þ Synchronet þ sbbs.dynu.net 2025
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113