🚀 go-pugleaf

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.