Subject:
|
Re: I can't access LUGNET through nntp today
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Fri, 16 Mar 2001 20:01:32 GMT
|
Viewed:
|
724 times
|
| |
|
|
"Todd Lehman" <lehman@javanet.com> wrote in message
news:3ab0c9d3.11522432@lugnet.com...
> In lugnet.admin.nntp, Dan Boger <dan@peeron.com> writes:
> > defenitly doesn't backwards resolve, but that shouldn't be an issue,
> > should it?
>
> That could be it. IIRC, the HTTP server doesn't do reverse lookups but • the
> NNTP server does.
>
> --Todd
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 ??).
BTW, I have the same troubles that Thomas had, but my wait is usually 30 -
35 seconds long. (as you can see in the logs).
I hope you have some time to investigate the issue.
Cheers
Carlo.
P.S.: sorry for the long lines.....
[2001-03-16 20:11:20] <166>%PIX-6-302001: Built outbound TCP connection 50
for faddr 209.68.63.236/119 gaddr 212.92.226.141/2982 laddr
xxx.xxx.xxx.xxx/2982
[2001-03-16 20:11:20] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1572 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:11:22] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1572 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:11:28] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1572 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:11:40] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1572 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:11:58] <166>%PIX-6-302002: Teardown TCP connection 50 faddr
209.68.63.236/119 gaddr 212.92.226.141/2982 laddr xxx.xxx.xxx.xxx/2982
duration 0:00:38 bytes 2825 (TCP Reset-I)
[2001-03-16 20:11:58] <166>%PIX-6-106015: Deny TCP (no connection) from
209.68.63.236/119 to xxx.xxx.xxx.xxx/2982 flags FIN ACK on interface
outside
[2001-03-16 20:18:30] <166>%PIX-6-302001: Built outbound TCP connection 55
for faddr 209.68.63.236/119 gaddr 212.92.226.141/2990 laddr
xxx.xxx.xxx.xxx/2990
[2001-03-16 20:18:30] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1720 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:18:32] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1720 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:18:38] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1720 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:18:50] <162>%PIX-2-106001: Inbound TCP connection denied from
209.68.63.236/1720 to 212.92.226.141/113 flags SYN on interface outside
[2001-03-16 20:19:09] <166>%PIX-6-302002: Teardown TCP connection 55 faddr
209.68.63.236/119 gaddr 212.92.226.141/2990 laddr xxx.xxx.xxx.xxx/2990
duration 0:00:39 bytes 2825 (TCP Reset-I)
[2001-03-16 20:19:09] <166>%PIX-6-106015: Deny TCP (no connection) from
209.68.63.236/119 to xxx.xxx.xxx.xxx/2990 flags FIN ACK on interface
outside
|
|
Message has 1 Reply:
 | | Re: I can't access LUGNET through nntp today
|
| (...) 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 (...) (24 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
Message is in Reply To:
20 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
