Greetings,

I have been trying for weeks to get connected to DoRENET, I get authorization failed when polling. I have double and triple checked everything that I have setup is correct. DM when asked says that everything on his end is how I put it on the application but without checking whether or not he made a typo is a little frustrating but oh well. However I was just going to try and send a netmail to his areafix as he claims he can poll my system, when I enter into the netmail area for dorenet and enter areafix in the to: field it then
prompts me for node address I enter it and then it shows me his two nodes so
I enter it again and it keeps showing me his two nodes it never lets me proceed... Any ideas what I can check?

Regards,

Nitro

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/64)
* Origin: Abacus BBS (1:340/202)

Hello Rick,

I have been trying for weeks to get connected to DoRENET, I get authorization failed when polling.

Authorization failed could be a password error. Session passwords are case sensitive so if you currently have the session password upper case try lower case.

Not sure about the netmail issue. I wonder if the nodelist is in good shape?

Do you have Force NL match set in your message base config? Turning it off might help in this case.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: That's odd. That's very odd. Wouldn't you say that's odd (1:153/757)

Greetings Al!

Tuesday April 07 2020 14:57, you wrote to me about an urgent matter!:

Hello Rick

Authorization failed could be a password error. Session passwords are
case sensitive so if you currently have the session password upper
case try lower case.

Yeah I verified by logging into his BBS email, for one reason or another thats the only way to communicate with him, the problem is he wont check to make sure
its entered on his side correctly he repeats that it is how it was on my application? I Have sp
But thank you for your kind response as always..

Oh and I had force NL off and the netmail thing is bizzare.. No worries though I gave up and deleted DoRENET

Regards,

Nitro


----

... HALF A CENTURY OLD BBSing GRANNY *&&*
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ----> Abacus BBS (bbs.abon.us:2323) <---- (1:340/202)

I just had a similar issue we finally chased down.

Turns out the Synchronet blacklist file was blocking my IP address. The NC was was wanting to block '46.' he had a 46.~. As it turns out, it blocked all
IP's with a '46.' in them anywhere even though my IP was a '146.'.

It wasn't until another sysop tested things out and just by coincidence we
both had a '46.' in our IP address.

Maybe this could be the issue.

Beery

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/64)
* Origin: 9640 News BBS (1:2320/108)

I just had a similar issue we finally chased down.

Could be I suppose I dont have a 46 in my address and he whitelisted my node
I believe. Communication is not the greatest unfortunately so I am not sure what there is left to do.

Thank you for the suggestion tho, he does have another BBS assigned to the
node he gave me now that just may be the nodelist but if that BBS's info is still in the hub that could keep me from polling.?

Regards.

Rick

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/64)
* Origin: Abacus BBS (1:340/202)

Could be I suppose I dont have a 46 in my address and he whitelisted my node I believe. Communication is not the greatest unfortunately so I am not sure what there is left to do.

My NC also whitelisted me, however it looks like the blacklist superceded anything with the wildcard blocking feature Synchronet was using.

In part of the debugging process, we tried telnetting to the 24554 port where
I was immediately dumped without the CRAM code being sent.

Beery

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/64)
* Origin: 9640 News BBS (1:2320/108)