NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Pstreicher
Jan 09, 2020Luminary
IP changed when I moved the cable, how do I get back to original IP?
I have been using this WNDR4000 Wi-Fi router for several years now with no problems whatsoever, until yesterday. Here's what I did. I wanted to move this router to a different location in the house....
- Jan 13, 2020
antinode wrote:> >> You say this is important but the problem is [...]
I understand that you want the G-1100 separated from the WNDR4000,
and that's fine with me, but if you want both those devices to provide
wireless access, then configuring the G-1100 in bridge mode (modem-only)
would be a bad idea, because that would disable its wireless access
capability. Hence my primary suggestion was to configure the WNDR4000
as a WAP (which would leave both wireless access points active).> [...] do not want to have to spend the coin if we don't have to.
Understood, but as that step-by-step procedure to configure any
router as a WAP should make clear, configuring a WNDR4000 as a WAP is
not especially simple.>> It was not hard to do. Basically I just gave the WNDR4000 a different name
for the SSID and turned both radio frequencies on. The FIOS G-1100 uses it's DHCP
to assign any wireless connections through the WNDR4000/N750.
The WNDR4000 shows no internect connection which used to confuse me until
I understood that the FIOS G-1100 was not configured in bridge mode and I had
only extended the network from the LAN port of the FIOS G-1100 to one of the
WNDR4000's LAN ports.
I think it's really a great piece of engineering that one router can serve IP addressing
through to another router in this fashion.
Pstreicher
Jan 10, 2020Luminary
Thanks for your reply. After reading through the manual and various other posts here in the forum, I was able to get the Nas up and running again and am able to connect to it to see the shares/files, etc.
What I did was shut down the Nas then plug in the two ethernet cables (Yes, it has two ethernet ports) to my D-Link eight port switch and then power up.
On to the WNDR4000/N750 router.....
Reading through 'how to reset' I then performed a reset. After waiting for the lights to settle I connected one end of an ethernet cable to the 'Internet' port of the router.and the other to my ethernet port on my laptop. I then typed in the browser, 192.168.1.2. After a few seconds or so I get a screen that informs me to check the cable and connections, so on and so forth. Sorry, I did not take a screengrab to give here or to type in the details. I tried the sequence once more and get the same results. I'm sure the first thing I needed to do was to check this cable to make sure it was a good working cable. I did test it by connecting it from the desktop computer in the office on one end and connecting the other end to the FIOS router and it proved it was good. I could browse the internet and log into the FIOS router, browse the net.
So, at this point I am at a loss as to what to do next.
Pstreicher
Jan 10, 2020Luminary
Update: Moments after posting the above I decided to try again. I don't know if leaving the router powered down overnight did the trick or what, but now after connecting the laptop to one of the router's ethernet ports and browsing to 192.168.1.1 I got the screen that gives me three options (if I remember correctly) to set up the router. I selected the option to allow me to do the setup. I could then see the menu selections on the side of the login splash screen as normal.
I then selected to restore from a backup configuration file that I had saved back on December 30, 2019. The router successfully restored the file, the lights flashed indicating to me that it is all back to where I started from before moving cables around. I checked for the SSID with my phone and do see the correct SSID's for 2.4 and 5G signals. I will next plug in the router to the D-Link switch after placing this router at the front of my house as I had originally started off to do before I got into trouble. This has been quite the learning experience and I have to thank the original, one and only replier to my post for pointing me in the right direction. Hopefully after moving and plugging this router into my switch everything will be good to go and we can close this discussion.
- antinodeJan 10, 2020Guru
> [...] I was able to get the Nas up and running again [...]
Did you find its actual model number, so that the rest of us might be
able to read along?> [...] (Yes, it has two ethernet ports) [...]
I can believe that, but why using both would be helpful in your case
is not immediately obvious. But that's not the immediate concern.> [...] I connected one end of an ethernet cable to the 'Internet' port
> of the router.and the other to my ethernet port on my laptop. [...]I would not expect that to work. The router _LAN_ Ethernet ports are
where you should connect a client device like your (unspecified) "my
laptop" (or your (unspecified) NAS).
> [...] I then typed in the browser, 192.168.1.2. [...]I would not expect that to be the (LAN) IP address of the router.
More likely, that would be the address of your (unspecified) "my
laptop".> [...] the FIOS router [...]
Still not a very detailed description of that device, but it seems
likely to be more accurate than "modem".
> [...] connecting the laptop to one of the router's ethernet ports and
> browsing to 192.168.1.1 [...]That would have a much better chance or doing something useful.
> [...] I will next plug in the router to the D-Link switch after
> placing this router at the front of my house as I had originally started
> off to do before I got into trouble. [...]You seem to have gotten the WNDR4000 back to its original condition,
which is good.> [...] Hopefully after moving and plugging this router into my switch
> everything will be good to go and we can close this discussion.Optimists are so cute.
I assume that your (unspecified) "the FIOS router" provides your
Internet connection, and that you've connected one of its LAN ports to
one of the ports on your "my D-Link eight port switch", and that you
have some computers and/or other gizmos connected to "the FIOS router"
directly and/or to the switch. Which should all be harmless.
The next problem will arise when you add the WNDR4000 to this
arrangement. If you simply connect the WAN/Internet port of the
WNDR4000 to one of the ports on your switch (or directly to a LAN port
on the main router -- they're practically equivalent), then, by default,
the WNDR4000 will create its own little subnet, and you can expect
trouble with communication between devices which are connected to the
LAN side of the WNDR4000-as-router, and devices which are connected to
the LAN of main router. If you try it, then I'd expect you to see a
whole different set of IP addresses on the WNDR4000 LAN ("10.0.0.*", not
"192.168.1.*").If you want all your devices to talk to each other on one
big/extended LAN, then you'll need to configure the WNDR4000 as a
wireless access point. Sadly, as I read the WNDR4000 User Manual, it
doesn't have a convenient one-step option to let you do that. That
doesn't make it impossible, but it does make it rather complicated.
(And you thought that what you'd already done was educational.) There's
a step-by-step for this here:
https://community.netgear.com/t5/x/x/m-p/1463500That's written for a C6300-as-WAP, but the steps are about the same for
any other router (any make/model) which lacks a one-step WAP option. It
does require you to do a little work on the main router, too.Many newer Netgear (and other) routers have more convenient WAP
configuration options, so you might have less trouble with something
other than a WNDR4000 in this role. In the User Manual for a Netgear
router, look for a section title like, "Set up the router as a WiFi [or
'wireless'] access point". For more helpful pictures, fetch the R7000
User Manual, and look there.I'll bet that this sounded easy when you started out.
- PstreicherJan 11, 2020Luminary
antinode wrote:> [...] I was able to get the Nas up and running again [...]
Did you find its actual model number, so that the rest of us might be
able to read along?>> I did and it is an RN104/ReadyNas 100 Series 4-Bay model.
> [...] (Yes, it has two ethernet ports) [...]
I can believe that, but why using both would be helpful in your case
is not immediately obvious. But that's not the immediate concern.>> I had intentions of bonding the two together to get faster transfer
speed but upon reading forum posts years ago when setting this up,
I was apprehensive to try it due to an actual slowing of speed, for
what reason that may happen I never found an answer. And, it was
also stated that it was hard to undue the bonding. One day I may
look into this again.
> [...] I connected one end of an ethernet cable to the 'Internet' port
> of the router.and the other to my ethernet port on my laptop. [...]I would not expect that to work. The router _LAN_ Ethernet ports are
where you should connect a client device like your (unspecified) "my
laptop" (or your (unspecified) NAS).>> Yeah, I think that is what originally had me spinning my wheels
and I was getting nowhere. After several attempts I remembered
that was not the correct port to connect to.
> [...] I then typed in the browser, 192.168.1.2. [...]I would not expect that to be the (LAN) IP address of the router.
More likely, that would be the address of your (unspecified) "my
laptop".>> The laptop I am using is an HP Envy model, Intel i7,
8gb ram, 64bit, Windows 8.1, Touch screen, 1TB SSD.
For however I set all this up in my network years ago
with this FIOS Actiontec router at the time, the Netgear
WNDR4000/N750 Wireless Dual Band Gigabit Router
was getting an IP of 192.168.1.2 and has stayed this way.
> [...] the FIOS router [...]
Still not a very detailed description of that device, but it seems
likely to be more accurate than "modem".>> It was an Actiontec model before it was upgraded to the
newer FIOS-G1100 Quantum model.
> [...] connecting the laptop to one of the router's ethernet ports and
> browsing to 192.168.1.1 [...]That would have a much better chance or doing something useful.
>> This provided the magic to make things happen finally after
getting the connections right. I could not locate any docs
to show or tell me how to do this. Maybe it is on the Netgear
site but where.
> [...] I will next plug in the router to the D-Link switch after
> placing this router at the front of my house as I had originally started
> off to do before I got into trouble. [...]You seem to have gotten the WNDR4000 back to its original condition,
which is good.>> Yes and I mounted it up high on a wall in the garage near the
center of my house where I will next switch the new Genie garage
door opener, a Wi-Fi model, of which you can see in notifications
if your door is open or closed, and some other features.
I also will switch the Yale Nest lock on the front door to this router
if it begins going offline like it had been doing a couple of weeks ago,
for which I went through many days of hell trying to figure that problem
out. I left it alone for two days and after optimizing my router SSID channels
to not interfere with the neighbors or vice versa, it came back online and
has stayed online. Keeping my fingers crossed on that. I digress though.
Forgive me.
> [...] Hopefully after moving and plugging this router into my switch
> everything will be good to go and we can close this discussion.Optimists are so cute.
I assume that your (unspecified) "the FIOS router" provides your
Internet connection, and that you've connected one of its LAN ports to
one of the ports on your "my D-Link eight port switch", and that you
have some computers and/or other gizmos connected to "the FIOS router"
directly and/or to the switch. Which should all be harmless.>> You assume correctly
The next problem will arise when you add the WNDR4000 to this
arrangement. If you simply connect the WAN/Internet port of the
WNDR4000 to one of the ports on your switch (or directly to a LAN port
on the main router -- they're practically equivalent), then, by default,
the WNDR4000 will create its own little subnet, and you can expect
trouble with communication between devices which are connected to the
LAN side of the WNDR4000-as-router, and devices which are connected to
the LAN of main router. If you try it, then I'd expect you to see a
whole different set of IP addresses on the WNDR4000 LAN ("10.0.0.*", not
"192.168.1.*").>> I do understand what you are saying but, I am have only connected
one of the LAN ports to the switch and am only going to use the
WNDR4000 as another wireless access point with a different SSID
as I had been doing in the past. That is, other than I did have the two
ethernet ports of the NAS connected to that router due to not having
any switch at the time when I set up the NAS some years back.
I did move those two NAS cables to the switch and when I booted the
NAS it came back up as before using the same IP's it originally was
using. I breathed a sigh of relief when I saw that yesterday morning.
If you want all your devices to talk to each other on one
big/extended LAN, then you'll need to configure the WNDR4000 as a
wireless access point. Sadly, as I read the WNDR4000 User Manual, it
doesn't have a convenient one-step option to let you do that. That
doesn't make it impossible, but it does make it rather complicated.
(And you thought that what you'd already done was educational.) There's
a step-by-step for this here:>> That is a good point and I want to do that someday.
Thanks for that link below. I will read though it and see
what I can.
https://community.netgear.com/t5/x/x/m-p/1463500
That's written for a C6300-as-WAP, but the steps are about the same for
any other router (any make/model) which lacks a one-step WAP option. It
does require you to do a little work on the main router, too.>> I believe I have to change the option in the FIOS G-1100 to
'Bridge' mode. Not sure at the moment but I think I read that
recently somewhere.
Many newer Netgear (and other) routers have more convenient WAP
configuration options, so you might have less trouble with something
other than a WNDR4000 in this role. In the User Manual for a Netgear
router, look for a section title like, "Set up the router as a WiFi [or
'wireless'] access point". For more helpful pictures, fetch the R7000
User Manual, and look there.I'll bet that this sounded easy when you started out
>> Of course. It always does doesn't it. :) Good day, sir and
we can close this case I think.
- antinodeJan 11, 2020Guru
> >> I do understand what you are saying but, I am have only connected
> one of the LAN ports to the switch and am only going to use the
> WNDR4000 as another wireless access point with a different SSID
> as I had been doing in the past.You lost me. "one of the LAN ports" on what?
> >> I believe I have to change the option in the FIOS G-1100 to
> 'Bridge' mode. Not sure at the moment but I think I read that
> recently somewhere.Might be possible. I haven't investigated that device.
The important thing is to have one router, not two. That means that
you can disable the router functions of the G-1100, by putting it into a
"bridge" mode, or else you can disable the router functions of the
WNDR4000 by configuring it as a WAP. If you put the G-1100 into
"bridge" mode, then the only thing which you can connect to it would be
the WNDR4000-as-router -- all the client devices would need to be
connected to the WNDR4000-as-router. With the G-1100-as-router and the
WNDR4000-as-WAP, you could connect client devices to either of them.