🚀 go-pugleaf

Parcxman wrote:
> TKR <spamthis@attbi.com> wrote in
> news:v4%L9.388362$WL3.115857@rwcrnsc54: 
> 
> 
>>Parcxman wrote:
>>
>>>My Netgear RT314 router has been working fine until tonight.  I've
>>>got attbi cable, and four machines behind the router.
>>>
>>>Now, if I put any of my machines behind the router, they won't
>>>connect to the internet.  If I hook them directly to the cable modem,
>>>I can connect ok just fine.
>>>
>>>Here's what I see.  The RT314 front panel lights are normal; the
>>>power light is on, the test light is off, the local ports are on, and
>>>the internet light blinks.
>>>
>>>I've released all/renewed all on any machine behind the router.  I've
>>>shut all hardware down, inclding the router, for 20 minutes, but no
>>>go.  I've used the router's Wizard to access the Maintenance/Erase
>>>panel and erased the settings to set them back to factory default
>>>(per the manual). I then re-entered the Wizard and re-configured just
>>>as I did when I first set the router up...actually, there was nothing
>>>to do to set it up initially, it plugged and played with all factory
>>>defaults. 
>>>
>>>The System Status screen shows:
>>>WAN PORT
>>>         IP Address: 12.210.236.25 (this is what attbi hands out)
>>>         IP Subnet Mask: 255.255.254.0
>>>         DHCP: Client
>>>LAN PORT
>>>         IP Address: 192.168.0.1
>>>         IP Subnet Mask: 255.255.255.0
>>>         DHCP: Server
>>>
>>>Firmware Version: v3.24 (CA.0), 2/8/2001
>>>
>>>The winipcfg (Win98) panel shows:
>>>DNS Server: 192.168.0.1
>>>IP: 192.168.0.2
>>>Subnet Mask: 255.255.255.0
>>>Default Gateway: 192.168.0.1
>>>DHCP Server: 192.168.0.1
>>>
>>>Same settings show on an XP machine when connected to the router.
>>>
>>>At this point, I've got no idea what's wrong.  I wonder if the
>>>firmware has gone south.  If so, should I see if there is an
>>>update/upgrade? 
>>>
>>>If it's time for a new router, can you suggest a 4 or 6 port wired
>>>router with firewall?  Wired is fine, as I've got the house cabled
>>>for ethernet, and all machines are desktops.
>>>
>>>TIA,
>>>Bruce
>>
>>First, you should determine if you have no Internet access or if you
>>are simply unable to resolve domain names.
>>
>>Telnet into the router. Go to Menu 24.8 . At the command prompt, issue
>>this command:
>>ip dhcp enif1 status
>>
>>Look through the resulting output and check that everything looks OK.
>>Then, using the Default gateway address listed in the output, use ping
>>to ping the gateway address (at your OS' command prompt, type ping
>>nnn.nnn.nnn.nnn where nnn is the Gateway address listed in the output
>>from above).
>>
>>If you can ping your ISP's gateway, then try pinging yahoo.com. If
>>this fails, then you have a DNS issue. Suggest that you configure your
>>4 PCs to use the 2 DNS server addresses from the output above rather
>>than 192.168.0.1 .
>>
>>If pinging your ISP's gateway failed, then the router isn't passing
>>traffic properly. First suggestion would be to upgrade to 3.25
>>firmware. Then restest.
>>
> 
> 
> I put two machines on the router side, and each can ping each other 
> (192.168.0.2/3), and browse each other (netbeui is installed on machines).  
> All machines can ping the router's LAN port 192.168.0.1.
> 
> No machines can ping yahoo's IP 66.218.71.87/84.
> 
> Telnetting to the router's menu 24.8 gives:
> 
> ip dhcp enif1 status
> DHCP on iface enif1 is client
>      Hostname : family.attbi.com.attbi.com
>      Domain Name : attbi.com
>      Server IP address: 12.242.17.34
>      Client IP address: 12.210.236.25/23
>      DNS server : 216.148.227.68, 204.127.202.4
>      Default gateway: 12.210.236.1
>      Lease time  : 345595 seconds
>      Renewal time: 172793 seconds
>      Rebind time : 302391 seconds
> 
> Pinging the Default Gateway 12.210.236.1 with the OS command prompt, times 
> out. 
> 
> NOTE:
> If I ping it from a machine that is connected directly to the cable modem, 
> I get 
> C:\>ping 12.210.236.1
> 
> Pinging 12.210.236.1 with 32 bytes of data:
> 
> Reply from 12.244.98.129: TTL expired in transit.
> Reply from 12.244.98.129: TTL expired in transit.
> Reply from 12.244.98.129: TTL expired in transit.
> Reply from 12.244.98.129: TTL expired in transit.
> 
> Ping statistics for 12.210.236.1:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 0ms, Maximum =  0ms, Average =  0ms
> 
> C:\>
> (I don't know what the above indicates.)
> 
> Back to the router...
> All I can do now, I guess, is to reinstall firmware v3.24 or v3.25.  The 
> Netgear site says that v3.25 is not needed if 3.24 is working, as 3.25 only  
> adds a language (French, I believe) and has one minor fix.
> 
> Comments?
> 
> Thanks,
> Bruce

The results from pinging ATT's gateway are unusual. Time To Live timeout
indicates that the number of hops to the gateway are greater than the
TTL value configured in the PC's TCP/IP stack. Since the TTL value is
around 25, I think, and the gateway should be the 1st hop, you should
not be getting a TTL timeout. The only thing that comes to mind is the
possibility that the route tables in the PC (and / or the router) are
screwed up (hacked?). The only other thing that came to mind was arp
poisoning, but the default gateway IP address looks to be valid.

At this point, I suggest that you focus on resolving the PC's ping
issue. After solving the "ping to gateway" problem is resolved,
perhaps you will find that the router doesn't really have an issue.

btw - firmware 3.25 is a good upgrade, in that 3.25 is stealth upon
installation and doesn't require any filters. Just be sure to load
the ROM file (config file) when you upgrade.