To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.nntpOpen lugnet.admin.nntp in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / NNTP / 396
395  |  397
Subject: 
Re: I can't access LUGNET through nntp today
Newsgroups: 
lugnet.admin.nntp
Date: 
Thu, 15 Mar 2001 13:46:39 GMT
Viewed: 
574 times
  
Todd Lehman wrote:

In lugnet.admin.nntp, Thomas Main writes:

I am connecting through port 199 (yesterday I tried 1119, 8000, and 8080


199?  You mean 119, ya?


as a test...same results).  I am using Netscape Communicator 4.7's
built-in newsreader my ip address is 152.10.28.104


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 reverse-DNS
lookup issue?

Can other people traceroute to or nslookup Thomas's IP address (above)?

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
[146.188.161.70]
   4    10 ms    10 ms    10 ms  194.ATM10-0-0.GW3.RDU1.ALTER.NET
[146.188.162.69]
   5    10 ms    20 ms    11 ms  ncren-3-gw.customer.ALTER.NET
[157.130.76.58]
   6    10 ms    20 ms    10 ms  rtp2-gw.ncren.net [128.109.211.5]
   7    10 ms    20 ms    10 ms  rtp8-gw.ncren.net [128.109.199.4]
   8    20 ms    20 ms    20 ms  asu-gw.ncren.net [128.109.216.2]
   9    21 ms    20 ms    30 ms  152.10.254.253
  10   541 ms    20 ms    20 ms  152.10.28.104

defenitly doesn't backwards resolve, but that shouldn't be an issue,
should it?

Dan



Message has 1 Reply:
  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 (24 years ago, 15-Mar-01, to lugnet.admin.nntp)

Message is in Reply To:
  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 (...) (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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR