Re: nntpservice delay on connect
  By: Ragnarok to DOVE-Net.Synchronet_Discussion on Fri Apr 15 2022 03:20 pm

 > I am experiencing delay when connecting to the nntp service.
 > It only happens to me with this one.
 > The rest of the js services respond perfectly and banners when
 > connecting to their ports.
 > There is no firewall rule regarding this port.
 > I still can't find what's going on. Nothing appears in the sbbs log
 > until the connection is made after a certain time.
 > any experienced problems with the nnstservice.js ?

You could try adding some log() lines to nntpservice.js to find out if it's event executing immediately upon connect?

If it's not, enabling debug-level log output for the services server and pasting that log output here would be helpful. e.g.

  4/15  12:05:58p  7608 NNTP connection accepted from: 71.95.196.36 port 55342
  4/15  12:05:58p  7608 NNTP JavaScript service thread started
  4/15  12:06:03p  7608 NNTP Hostname: synchro.net [71.95.196.36]
  4/15  12:06:04p  7608 NNTP Logging in Guest

That 5 second delay there between "JavaScript service thread started" and reporting the hostname (of the client) is likely just the DNS name resolution. That's followed by ip*.can and host.can filter file checking. And then of course, if there's been any failed login attempts from the client IP, that could invoke some throttling (delays). So there are a lot of opportunities for delay in this process and the log output should provide you the clues you need to find out what those are in your case.
-- 
                                            digital man (rob)

Synchronet "Real Fact" #117:
Synchronet v1b r0 (for MS-DOS) was released on September 25, 1992
Norco, CA WX: 66.6øF, 42.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux