NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New AC1900 (EX7000) can't get on the local network
I just bought a second EX7000 to use as an ethernet-connected WAP at one corner of my home, I have an existing EX7000 at the other end of the house which does the same job and works perfectly. My hom...
You might try updating the firmware to 1.0.0.66. I'd avoid 1.0.1.78 for now, there are a lot of people reporting issues with it.
The subnet mask should be 255.255.255.0.
Perhaps also try the smart setup path, as that might be needed for the system to determine that you are setting it up as an AP instead of as an extender.
What firmware are you running?
There are quite a few issues being reported with 1.0.1.78, so if you are running that you might try downgrading to 1.0.0.66.
Hi
This is out of the box
Hardware Version: EX7000
Firmware Version: V1.0.0.62_1.0.122My home network's router is 192.168.0.254 and my gateway is 192.168.0.1 (an ubuntu NUC running DHCP and DNS). The DHCP server serves up IP addresses in the range 192.168.0.129-250.
Here's what happens with the new (hopefully) WAP.
1. I connect an ethernet cable from the router. I know the port works.
2. I switch the EX7000 on. After about 30 secs it settles down with the LAN port and extender LED's green, all others off.
3. I can see NETGEAR_EXT in the list of wifi networks, so I connect to it with my phone and open a browser at mywifi.ext.
4. It says I am not connected to my extender's WIFI network.
5. I follow the link to log in directly to the EX7000 and login with my recovery username and password. (This is a new one, not the same as that used for the existing WAP).
6. It says I am not connected to my router, do I want to use the genie or connect manually.
7. I say I want to set it up myself. It goes into the smart setup page (which is where I see the firmware version I reported earlier), but I go instead to the device menu at the top left corner of the page.
8. I open the settings option, pick Wireless, scroll past the 2.4G and 5G wifi settings and open the IP Address section.
9. The device is set to pick up an address dynamically from the router but I can see that the address it has been given is 192.168.1.250. Nothing in my network would allocate this address.
10. I chage it to use a static IO and assign it 192.168.0.6, gateway as above, DNS server 8.8.8.8
11. Am I sure I do not want any security? Am I sure this address is in the correct subnet? I say OK to these (I'll change the network security later)
12. My browser page asks me to login again, so I do.
13. Go back to step 6.You might try updating the firmware to 1.0.0.66. I'd avoid 1.0.1.78 for now, there are a lot of people reporting issues with it.
The subnet mask should be 255.255.255.0.
Perhaps also try the smart setup path, as that might be needed for the system to determine that you are setting it up as an AP instead of as an extender.
That was good timing, I was just going to add an update to the previous.
Yes 255.255.255.0 is what I set for the subnet mask.
I found that when I set the static IP on the unit, it does retain an IP address of 192.168.0.6 and it shows up in my IP scanner. I've set up my DHCP server to identify the MAC address and assign that IP automatically (and remembered to reboot it), but when I tell the EX7000 to set the IP address dynamically it *always* gets 192.168.1.250. So it's static IP for now. (The other EX7000 is using DHCP and is getting the correct address.)
However, regardless of whether the device is getting 192.168.0.6 or 192.168.1.250, it consistently reports that there is no connection to the router.
The old EX7000 is running V1.0.0.50_1.0.102 firmware, and I didn't update because I had read that the latest firmware was suspect. If I can select which version to update to I'll put them both on 1.0.0.66. I hope they fix the issues with 78 because wireless mesh is *exactly* what I am trying to achieve.
Thank you
I updated the firmware to 1.0.0.66 and restarted the whole process. Allocating the correct IP address via DHCP is now happening, and smart setup is no longer complaining that the device is not connected to the router. The network is networking.
