Subject:
|
Re: I can't access LUGNET through nntp today
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Thu, 15 Mar 2001 13:56:49 GMT
|
Viewed:
|
550 times
|
| |
|
|
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
|
|
Message has 2 Replies:
 | | 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 (24 years ago, 15-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 (...) (24 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
Message is in Reply To:
| | 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 (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
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
|
|
|
|
