 | | Re: I can't access LUGNET through nntp today —Todd Lehman
|
| | | (...) Thomas, Are you using a proxy or anything like that? Behind a firewall? Any recent network configuration changes on your machine or on your LAN or your ISP? How long is the hang before it times out and gives you the error? Anyone else seeing (...) (24 years ago, 13-Mar-01, to lugnet.admin.nntp)
|
| | | |
| | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | | (...) using netscape 6's newsreader, no problem at all... it wouldn't cancle my article though :/ Dan (24 years ago, 13-Mar-01, to lugnet.admin.nntp)
|
| | | | | |
| | | | | Re: I can't access LUGNET through nntp today —Thomas Main
|
| | | | (...) using (...) end? (...) I (...) Todd, Nope, no proxy. It took forever to finally timeout yesterday when I tried to connect. Today, I just connected (took unusually long) and read one message, then when going to the next message, it is just (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Thomas Main
|
| | | | In lugnet.admin.nntp, Thomas Main writes: <snip> (...) Just an update, moving between messsages is a lot faster now...moving between messages in groups is also moving at a decent, although lesser speed. -- Thomas Main main@appstate.edu (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Thomas Main
|
| | | | (...) Hmmm...it seems that my initial connect is what is terribly slow, and then another long wait until the first message comes up. I just reconnected to the news server and it seems to take about 3 mins. to connect, then another 3 min. to display (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Todd Lehman
|
| | | | | (...) Which port are you connecting with? The default (119)? What groups are in your subscription list? What software client are you using? Can you email me your IP address and I'll try doing a traceroute. --Todd (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | | |
| | | | | | | Re: I can't access LUGNET through nntp today —Thomas Main
|
| | | | | | (...) the (...) min. (...) I am connecting through port 199 (yesterday I tried 1119, 8000, and 8080 as a test...same results). I am using Netscape Communicator 4.7's built-in newsreader my ip address is 152.10.28.104 Thanks for your help. -- Thomas (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | | | |
| | | | | | | | Re: I can't access LUGNET through nntp today —Todd Lehman
|
| | | | | | (...) 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 (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| | | | | | |
| | | | | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | | | (...) 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)
|
| | | | | | |
| | | | | | | | Re: I can't access LUGNET through nntp today —Todd Lehman
|
| | | | | | (...) That could be it. IIRC, the HTTP server doesn't do reverse lookups but the NNTP server does. --Todd (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| | | | | | |
| | | | | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | | | | (...) 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
|
| | | | | | | | (...) 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): (...) (24 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | | | | | |
| | | | | | | | | | Re: I can't access LUGNET through nntp today —Dan Boger
|
| | | | | | | | (...) 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 (...) (24 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | | | | | |
| | | | | | | | 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 (...) (24 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 (...) (24 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 (...) (24 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 (...) (24 years ago, 16-Mar-01, to lugnet.admin.nntp)
|
| | | | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Kenneth A. Drumm, Ph.D.
|
| | | | | I've noticed that if you use IE and Netzero as an ISP getting messages is_very_ _VERY_ long. Is this the case? -- Kenneth A. Drumm Ph.D. "Thomas Main" <main@appstate.edu> wrote in message news:GA74so.1M0@lugnet.com... (...) tried to (...) message, (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | | |
| | | | | | Re: I can't access LUGNET through nntp today —Kenneth A. Drumm, Ph.D.
|
| | | | I've noticed that if you use IE and Netzero as an ISP getting messages is_very_ _VERY_ long. Is this the case? -- Kenneth A. Drumm Ph.D. "Thomas Main" <main@appstate.edu> wrote in message news:GA74so.1M0@lugnet.com... (...) tried to (...) message, (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| | | | |
