Article View: comp.dcom.modems.cable
Article #28Re: Netgear RT314 Now Working
From: TKR
Date: Fri, 20 Dec 2002 14:43
Date: Fri, 20 Dec 2002 14:43
38 lines
2855 bytes
2855 bytes
> > > I have no idea why, but just before I was about to connect the router to > another IP (I have 4 paid IPs from attbi), I decided to ping the default > gateway that attbi was handing out to the router, 12.210.236.1, and which > was last night receiving TTL expired status, but with no packet loss (see > above). I pinged this ip from a machine connected directly to the cable > modem. Here's the results: > > C:\>ping 12.210.236.1 > > Pinging 12.210.236.1 with 32 bytes of data: > > Reply from 12.210.236.1: bytes=32 time=10ms TTL=255 > Reply from 12.210.236.1: bytes=32 time=10ms TTL=255 > Reply from 12.210.236.1: bytes=32 time=53ms TTL=255 > Reply from 12.210.236.1: bytes=32 time=12ms TTL=255 > > Ping statistics for 12.210.236.1: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 10ms, Maximum = 53ms, Average = 21ms > > C:\> > > Hmmm...I then connected the router to the cat5 cable, and connected 2 > machines behind the router. Both machines are now browsing the internet. > > Why was this line out for two days and then came back up, I have no idea. > If anyone does, please write. I will monitor this for a while and write > back if this reoccurs. > > Thanks to TKR for scratching his head with me. > > Bruce No additional thoughts here, either. Just glad you're back up and running.
Technical Details
Message-ID:
<Z%FM9.408080$P31.147583@rwcrnsc53>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mailReferences:
<Xns92E7D210CA5DDparcxmannetscapenet@204.127.202.16> <v4%L9.388362$WL3.115857@rwcrnsc54> <Xns92E8F28086E6Fparcxmannetscapenet@63.240.76.16> <lxkM9.32975$qF3.2166@sccrnsc04> <Xns92E9E6FD3B139parcxmannetscapenet@63.240.76.16>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fa874,a726fd0dfdecd17d X-Google-Attributes: gidfa874,public X-Google-Thread: 113850,a726fd0dfdecd17d X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2002-12-20 06:42:59 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mail From: TKR <spamthis@attbi.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.dcom.modems.cable,ba.internet Subject: Re: Netgear RT314 Now Working References: <Xns92E7D210CA5DDparcxmannetscapenet@204.127.202.16> <v4%L9.388362$WL3.115857@rwcrnsc54> <Xns92E8F28086E6Fparcxmannetscapenet@63.240.76.16> <lxkM9.32975$qF3.2166@sccrnsc04> <Xns92E9E6FD3B139parcxmannetscapenet@63.240.76.16> In-Reply-To: <Xns92E9E6FD3B139parcxmannetscapenet@63.240.76.16> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lines: 39 Message-ID: <Z%FM9.408080$P31.147583@rwcrnsc53> NNTP-Posting-Host: 66.177.119.61 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc53 1040395385 66.177.119.61 (Fri, 20 Dec 2002 14:43:05 GMT) NNTP-Posting-Date: Fri, 20 Dec 2002 14:43:05 GMT Organization: AT&T Broadband Date: Fri, 20 Dec 2002 14:43:05 GMT