 | | Re: I can't access LUGNET through nntp today —Carlo Ottolina
|
| | | "Todd Lehman" <lehman@javanet.com> wrote in message news:3ab0c9d3.115224...net.com... (...) the (...) Yes, it does. This is a small log from my firewall, (Cisco PIX 515) where you can see that the nntp server needs a TCP connection on port 113 (auth (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | |
| | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | (...) I think it's doing ident lookups... and I think the reason you have to wait 30 secs or so is cause you're dropping the auth packets and not rejecting them... so it's waiting for an answer. if you modified your firewall to reject connections to (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Carlo Ottolina
|
| | | | "Dan Boger" <dan@peeron.com> wrote in message news:3AB27414.909030...ron.com... (...) that (...) 30 - (...) Dan, thanks for your suggestions! Unfortunately, rejecting connections to port 113 is exactly what I am doing now. (See, I usually don't (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | (...) if it's sending back a RST ACK that means the port is closed on your workstation, and that's all the server wanted to know... since from your earlier log didn't mention anything about resets being sent back to lugnet, I just assumed it was (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | |
