Networking Forums

Networking Forums > Wireless Networking > Wireless Internet > Netgear WGR614 Router Configuration

Reply
Thread Tools Display Modes

Netgear WGR614 Router Configuration

 
 
ToxicMarlin
Guest
Posts: n/a

 
      12-14-2004, 03:36 PM
I'm having trouble with a Netgear WGR614 router. I installed it
yesterday and it's working fine for connecting to the Internet on a
wired connection and a wireless connection, but I can't connect to
the router to reconfigure the setup. I've performed a factory
setting reset twice, and each time I'm able to configure the router
initially, but when I save the settings and exit it, I am unable to
reconnect to the setup program to make configuration changes.

I didn't (at least not knowingly) change the default I.P. address for
the router.

I've tried to connect to it through I.E. using 192.168.0.1,
www.routerlogin.net/basicsetting.htm, or the Netgear support CD link
that came with the router. Every time, I get an error that the web
page cannot be located.

It's not practical to have to reset the router to the factory
settings every time I want to try a new configuration.

Any ideas?

Mike

 
Reply With Quote
 
 
 
 
dold@XReXXNetge.usenet.us.com
Guest
Posts: n/a

 
      12-14-2004, 04:04 PM
ToxicMarlin <(E-Mail Removed)> wrote:
> I've tried to connect to it through I.E. using 192.168.0.1,
> www.routerlogin.net/basicsetting.htm, or the Netgear support CD link
> that came with the router. Every time, I get an error that the web
> page cannot be located.


I think the www.routerlogin.net is only available while the router is at
factory defaults. It is handy that it is available as soon as you try to
connect to any web site, but there is a message on screen that it will go
away when configuration is performed.

I presume you are accepting DHCP from the router to your PC.
Have a look at the default gateway and DNS server settings to see what
address is set for the router.
Are you on the "Internet" side of the router, or the "LAN/Wireless" side of
the router?

From Windows CMD prompt, ipconfig /all will show both the default gateway
and the DNS server address, which should be the Netgear.
You should be able to open a web page to that address.

The only other thing I can think of is that you may some firewall or
filtering set on your PC. Have you tried a different PC?
When you successfully connect to the defaulted router, are you specifically
connecting to 192.168.0.1, or are you opening a browser and finding the
config page as the home page?


--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

 
Reply With Quote
 
Jeff Liebermann
Guest
Posts: n/a

 
      12-14-2004, 06:19 PM
On 14 Dec 2004 08:36:51 -0800, "ToxicMarlin" <(E-Mail Removed)>
wrote:

>I'm having trouble with a Netgear WGR614 router. I installed it
>yesterday and it's working fine for connecting to the Internet on a
>wired connection and a wireless connection, but I can't connect to
>the router to reconfigure the setup. I've performed a factory
>setting reset twice, and each time I'm able to configure the router
>initially, but when I save the settings and exit it, I am unable to
>reconnect to the setup program to make configuration changes.
>
>I didn't (at least not knowingly) change the default I.P. address for
>the router.
>
>I've tried to connect to it through I.E. using 192.168.0.1,
>www.routerlogin.net/basicsetting.htm, or the Netgear support CD link
>that came with the router. Every time, I get an error that the web
>page cannot be located.
>
>It's not practical to have to reset the router to the factory
>settings every time I want to try a new configuration.


Yes. For initial setup, use:
http://www.routerlogin.net
For everything after that, use:
http://www.routerlogin.com

http://kbserver.netgear.com/support_...asp?dnldID=739
Note the "known issues" item #1.

Opinion: This is actually a very good idea by Netgear. Too bad they
made the two URL's sufficiently similar that almost everybody
(including me) fails to notice the difference.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558
 
Reply With Quote
 
dold@XReXXNetge.usenet.us.com
Guest
Posts: n/a

 
      12-14-2004, 07:09 PM
Jeff Liebermann <(E-Mail Removed)> wrote:

> Yes. For initial setup, use:
> http://www.routerlogin.net
> For everything after that, use:
> http://www.routerlogin.com


> http://kbserver.netgear.com/support_...asp?dnldID=739
> Note the "known issues" item #1.


> Opinion: This is actually a very good idea by Netgear. Too bad they
> made the two URL's sufficiently similar that almost everybody
> (including me) fails to notice the difference.


I don't read that the same way that you do.
I read that the .net and .com are identical and interchangeable.

I think the initial redirection to this URL from any opening web browser is
a damn fine idea. Using some goofy name that is destined to be an industry
standard is not quite so good.

The original poster indicated that he had also tried 192.168.0.1, which
should have worked. It works for me, with a WGR614v4 Firmware Version
5.0_02. I didn't try the "name", .com or .net.

--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

 
Reply With Quote
 
Jeff Liebermann
Guest
Posts: n/a

 
      12-14-2004, 10:16 PM
On Tue, 14 Dec 2004 20:09:06 +0000 (UTC),
(E-Mail Removed) wrote:

>Jeff Liebermann <(E-Mail Removed)> wrote:
>
>> Yes. For initial setup, use:
>> http://www.routerlogin.net
>> For everything after that, use:
>> http://www.routerlogin.com

>
>> http://kbserver.netgear.com/support_...asp?dnldID=739
>> Note the "known issues" item #1.


>> Opinion: This is actually a very good idea by Netgear. Too bad they
>> made the two URL's sufficiently similar that almost everybody
>> (including me) fails to notice the difference.

>
>I don't read that the same way that you do.
>I read that the .net and .com are identical and interchangeable.
>
>I think the initial redirection to this URL from any opening web browser is
>a damn fine idea. Using some goofy name that is destined to be an industry
>standard is not quite so good.
>
>The original poster indicated that he had also tried 192.168.0.1, which
>should have worked. It works for me, with a WGR614v4 Firmware Version
>5.0_02. I didn't try the "name", .com or .net.


The setup instructions at:
ftp://downloads.netgear.com/files/wg...tall_guide.pdf
ftp://downloads.netgear.com/files/wgr614_ref_manual.pdf
both use http://192.168.0.1 instead of the routerlogin.whatever
stuff. I made a guess(tm) from my experience with the MR814, which
uses similar names. One name gets you to the initial setup wizard.
The other goes striaght to the config page. However, this might be a
bad guess(tm). In any case, 192.168.0.1 should work.

You may be right. Just ignore me.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice http://www.LearnByDestroying.com
# (E-Mail Removed)
# 831.421.6491 digital_pager (E-Mail Removed) AE6KS
 
Reply With Quote
 
TV Slug
Guest
Posts: n/a

 
      12-15-2004, 12:46 AM
ToxicMarlin wrote:
> I'm having trouble with a Netgear WGR614 router. I installed it
> yesterday and it's working fine for connecting to the Internet on a
> wired connection and a wireless connection, but I can't connect to
> the router to reconfigure the setup. I've performed a factory
> setting reset twice, and each time I'm able to configure the router
> initially, but when I save the settings and exit it, I am unable to
> reconnect to the setup program to make configuration changes.
>
> I didn't (at least not knowingly) change the default I.P. address for
> the router.
>
> I've tried to connect to it through I.E. using 192.168.0.1,
> www.routerlogin.net/basicsetting.htm, or the Netgear support CD link
> that came with the router. Every time, I get an error that the web
> page cannot be located.
>
> It's not practical to have to reset the router to the factory
> settings every time I want to try a new configuration.
>
> Any ideas?
>
> Mike


What exactly are you "configuring" when you save the changes and then can't
get back to the setup? There are options in there (other than the IP) that
will make the setup inaccessible. For instance, if you only go into the WAN
Setup and change the "Respond to Ping on the Internet Port" checkbox and
save that, can you no longer access the setup?


 
Reply With Quote
 
Jim Fox
Guest
Posts: n/a

 
      12-15-2004, 02:36 AM
Jeff Liebermann wrote:
>
> In any case, 192.168.0.1 should work.
>

It should work on the LAN side, assuming no configuration changes were made
that would prevent it from working. But on the WAN side, in addition to
entering whatever IP address it has, you have to add :8080 for port 8080.
For example, 111.222.333.444:8080. I have two routers, with the WAN port of
the WGR614 connected to a LAN port of my main router, and this allows me to
access the WGR614 from that LAN, which is on a different subnet.

But that raises the question: are two LANs involved? If the WGR614 is set
to automatically received a DHCP address from a router on a first subnet
(e.g., 192.168.0.1), then the WGR614 subnet might automatically be changed
to 192.168.1.1. I haven't tried this myself, since I set a static IP
address, but that is probably how it would work. (So in that case, he would
have to access the WGR614 on 192.168.1.1, or whatever).





 
Reply With Quote
 
Jeff Liebermann
Guest
Posts: n/a

 
      12-15-2004, 03:04 AM
On Tue, 14 Dec 2004 22:36:34 -0500, "Jim Fox" <(E-Mail Removed)>
wrote:

>Jeff Liebermann wrote:
>> In any case, 192.168.0.1 should work.


>It should work on the LAN side, assuming no configuration changes were made
>that would prevent it from working. But on the WAN side, in addition to
>entering whatever IP address it has, you have to add :8080 for port 8080.
>For example, 111.222.333.444:8080. I have two routers, with the WAN port of
>the WGR614 connected to a LAN port of my main router, and this allows me to
>access the WGR614 from that LAN, which is on a different subnet.
>
>But that raises the question: are two LANs involved? If the WGR614 is set
>to automatically received a DHCP address from a router on a first subnet
>(e.g., 192.168.0.1), then the WGR614 subnet might automatically be changed
>to 192.168.1.1. I haven't tried this myself, since I set a static IP
>address, but that is probably how it would work. (So in that case, he would
>have to access the WGR614 on 192.168.1.1, or whatever).


You have all the right buzzwords, but are apparently lacking in how
they are glued together to make a router. Let me try from the
beginning:

A router is a box that is designed to connect two dissimilar networks.
In this case, one network is the greater internet, also known as the
WAN (wide area network). The other network is your own network, known
as the LAN (local area network). Additional networks can also be
connected using static or dynamic routes, but we won't go there.

The basic requirement is that the WAN and LAN networks do not overlap.
Therefore, the LAN side of the router is usually assigned a Class C IP
address block of 255 addresses, such as 192.168.1.xxx. RFC-1918
allegedly insures that nobody on the greater internet uses
192.168.xxx.xxx for their internet connection.

On the WAN side of the router, you have a connection to the internet.
Your favorite ISP assigns you an IP address for the router, and a
gateway through which all packets *NOT* destined for 192.168.1.xxx get
to the ISP and then to the internet. This is called the routeing
table. The routers purpose in life is to connect devices on the LAN
side of the router to the WAN side using rules in this router table.
This is not a great time to explain how to decode a router table.

Connecting to the internet from any device on the LAN is fairly
simplistic. EVERYTHING goes through the ISP's default gateway IP
address and then to the internet. It doesn't matter what IP addresses
(except 192.168.1.xxx) or which IP port numbers 1-65535), they all go
to the internet via the default gateway. Computers and devices are
seperated using NAT (network address translation) and PAT (port
address translation as Cisco calls it) which seperate different
streams using port numbers.

However, coming in from the internet, we have a problem. Your router
has only one WAN IP address. However, there can be as many as 253
computahs on your LAN side. There's no easy way to connect to a
specific computah. For this we have "port redirection" which I don't
wanna burn time on right now.

Coming into the router configuration from the internet, one connects
to the WAN IP address of the router as assigned by the ISP. Coming
into the router configuration from the LAN, one uses the LAN side IP
address (usually 192.168.1.1). Both these addresses are the same
router, just different sides of the router.

From the LAN side, port 80 is usually used. That's not a problem
because the IP address used refers to exactly one device (the router).
However, coming in from the WAN presents a problem. If port
forwarding is enabled and configured, one has to specifically select a
port number that isn't already being used. Port 80 is highly likely
to be used if port forwarding is configured to point to a web server
on the LAN. This is how you run your own web server, by redirecting
the WAN side port 80 to a specific computah on the LAN. So, a
different port is necessary. It can be any port number but for some
odd reason, the cheapo router manufactories limit the choice to 1 or
three port numbers. Usually 8080 is on top of the list, so it gets
selected. Normally WAN side configuration access is disabled to
prevent hackers like me from taking over your router.




--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice http://www.LearnByDestroying.com
# (E-Mail Removed)
# 831.421.6491 digital_pager (E-Mail Removed) AE6KS
 
Reply With Quote
 
Jim Fox
Guest
Posts: n/a

 
      12-15-2004, 12:51 PM
Jeff Liebermann wrote:
>> You have all the right buzzwords, but are apparently lacking in how

> they are glued together to make a router. Let me try from the
> beginning:
>

I don't know what you think you added that is of relevance. But if it makes
you happy, OK.


 
Reply With Quote
 
Jeff Liebermann
Guest
Posts: n/a

 
      12-15-2004, 04:06 PM
On Wed, 15 Dec 2004 08:51:13 -0500, "Jim Fox" <(E-Mail Removed)>
wrote:

>Jeff Liebermann wrote:
>>> You have all the right buzzwords, but are apparently lacking in how

>> they are glued together to make a router. Let me try from the
>> beginning:


>I don't know what you think you added that is of relevance. But if it makes
>you happy, OK.


Sorry. I had a truely rotten day and was snarling at everyone and
everything. My appologies for being excessively offensive.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
wgr614 netgear router and VPN connection ... wbsurfver@yahoo.com Wireless Internet 2 12-07-2007 06:50 PM
Netgear WGR614 v5 configuration josesantos7@hotmail.com Wireless Internet 2 03-01-2005 11:49 PM
Manual configuration on Netgear WGR614? hofo Wireless Internet 4 12-14-2004 03:13 PM
Connecting WAP to Router (Netgear WGR614) Cliff Wireless Internet 12 10-15-2004 12:28 PM
Netgear RP614 Wired Router + Netgear WGR614 Wireless Router MH Wireless Internet 4 07-23-2003 12:58 PM



1 2 3 4 5 6 7 8 9 10 11