On Fri, 28 Sep 2007 00:15:23 -0400, Patriot5
<Patriot5.2xls8v@no-mx.wirelessforums.org> wrote:
>I replaced my older "b" wireless Netgear router with a new WGR614 when
>it began to become very slow when connected wirelessly. After numerous
>hours attempting to get the new router working I need help!
>I have
>followed the Netgear directions and suggestions from different posts
>here without luck.
Which suggestions did you try and which ones did not work. I really
don't like repeating the suggestions over and over.
>I have a Comcast cable/phone modem that the router
>connects to.
Does it have a manufacturer and model number?
>I know about resetting the Comcast modem etc. I am able to
>ping the router when it is not connected to Comcast fine. It definitely
>is a problem with the connection from the WGR614 and the Comcast. The PC
>works fine when connected directly to Comcast. The older Netgear was up
>and running in 10 minutes on installation so I don't know what could be
>wrong unless the WGR614 is DOA. Any suggestions? Should I use a static
>IP?
I've had problems with some of the 6 different hardware versions of
the WGR614 (check your serial number tag). In most cases, the
solution was to update the router firmware. Start here:
<http://kbserver.netgear.com/products/wgr614.asp>
and make absolutely sure you install the firmware that matches your
unspecified hardware version.
You didn't mention what happened when you plugged your unspecified
model PC directly into the router via a CAT5 cable (i.e. no wireless).
Did it work? Did it work fast?
It's also possible there's something odd about your wireless client.
Ping isn't really good enough for testing.
If your unspecified model Comcast cable modem happens to be the VoIP
Arris version, it has a few nasty habits, one of which is to save the
MAC address of the connecting device even though you stomped on the
reset button. If you have an Arris cable modem, remove the bottom
cover, unplug the battery for about 15 seconds, replace battery,
replace cover, wait until it reboots, and try again.
It's also possible that you have a bad CAT5 cable between the Netgear
and the cable modem. The cables supplied by Comcast appeared to me a
bit marginal, but I've had no failures. Still, it would useful to
replace the cable.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
jeffl@comix.santa-cruz.ca.us
#
http://802.11junk.com jeffl@cruzio.com
#
http://www.LearnByDestroying.com AE6KS