NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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....
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.
> [...] the two cables [...]
Why "two cables"?
> [...] serving a Netgear RN410 Nas.
What is its _real_ model number? Look at the product label.
> [...] I then plugged in the two Nas cables into the switch that is
> served by the host modem. [...]
What is your "the switch"? What is your "the host modem"?
> [...] This router was only used for Nas access and for wireless
> devices.
Was it configured as a router or as a wireless access point?
> [...] Now the trouble became apparent.
So far, the only thing which is apparent to me is that, other than
the WNDR4000, I have no idea what any of your equipment is, nor how any
of it is connected to the rest of it, nor what any of the relevant IP
addresses might be, nor what any LED indicators might be indicating, nor
anything else which might qualify as useful information.
A cable has two ends. Where do your cables go? (Hint: If a device
has different types of Ethernet ports, then "connected to device" is not
enough detail.)
> [...] I also could no longer log into the WNDR4000 router.
When you did what, exactly? "could no longer" is not a useful
problem description. It does not say what you did. It does not say
what happened when you did it. As usual, showing actual actions
(commands) with their actual results (error messages, LED indicators,
...) can be more helpful than vague descriptions or interpretations.
Starting from some computer or other, which was connected somehow or
other to something or other, using some web browser or other, and some
URL or other, you got some kind of error or other?
> Does anyone know how to get back the original IP for the Netgear
> router and more importantly, the Nas ips with ports 4 and 7?
Who knows what that "the original IP [address]" was? If you expect a
device to keep the same IP address, then you might look for "Address
Reservation" in the WNDR4000 User Manual. (Visit
http://netgear.com/support , put in your router model number, and look
for Documentation. Get the User Manual. You might also try that for
the NAS gizmo, whatever it might be.)
> [...] I am panicking at this point.
Apparently, and it's not helpful. A clear, accurate, concise
description of what your equipment is, and how it's all connected, would
be a better way to invest your time. (And waste less of everyone
else's.)
> I say ports, meaning the 4th or end number of the IP number.
"ports" means something different to everyone else. Inventing your
own technical terms (especially when they conflict with existing ones)
is not the best way to communicate. And, with multiple routers
involved, the rest of any IP address might be significant, too.
Also, there are forums for NAS devices:
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.
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.
> [...] 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.