 | | Re: I can't access LUGNET through nntp today
|
|
(...) 199? You mean 119, ya? (...) Odd... traceroute from 209.68.63.236 (lugnet.com) to your IP address just sits there and hangs, then gives a "can't find" error. Same with nslookup. Either this is some low-level TCP/IP networking issue or some (...) (23 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) Tracing route to 152.10.28.104 over a maximum of 30 hops 1 <10 ms <10 ms 10 ms cisco.rv.tis.com [204.254.155.1] 2 <10 ms 10 ms <10 ms Loopback0.GW3.DCA1.ALTER.NET [137.39.4.22] 3 <10 ms 10 ms <10 ms 106.at-3-0-0.XR2.DCA1.ALTER.NET (...) (23 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) That could be it. IIRC, the HTTP server doesn't do reverse lookups but the NNTP server does. --Todd (23 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) hmmm... would that cause the 440 error (new users start here)? I've been getting that with slrn when I tried to post from home... and my !@#$!@ verison dhcp may or may not backwards resolve... Might that be the reason? Dan (23 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) Hmm, no, the "new users start here" message only happens once the article is received and going through the auth stages. I think your newsreader must be submitting a faulty 'From:' header...I see a line like this (which is missing your name): (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) ah ha! thank you much, slrn will be reconfigured tonight :) but that doesn't explain why I couldn't cancle my own post with netscape, does it? my link posted to .trains, I tried to cancle it, but still got the "new uesrs" message... but I (...) (23 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
"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
|
|
(...) 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
|
|
"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
|
|
(...) 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)
|
