NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
pc_m
Jan 03, 2019Aspirant
Wired connections not able to connect to internet
I have a similar problem to the one in post https://community.netgear.com/t5/Orbi/Orbir-will-not-connect-to-a-wired-connection/m-p/1262055#M6071
I had an Asus wi-fi router with 4 ethernet ports...
pc_m
Jan 06, 2019Aspirant
Tough day today. On the fourth powerup and login of my iMac, I did not have wired access to internet. It worked for 4 days (previously worked for 5). Fortunately, the Netgear GS308 ethernet switch arrived today. Connected all up, in place of the Linksys, and... same thing. No access for wired devices and they were not showing up in the Orbi admin scrteen.
Next, I connected only my iMac to the ethernet switch and the switch to the Orbi router, with no other devices connected to the router and power cycled the Orbi and new ethernet switch. The Mac had a self assigned IP and did not connect to the internet. This is the same thing I had with the Linkaya switch,
Called Netgear support. I connected the Mac (only) to the Orbi and it worked. Then, connected the iMac to the ethernet switch and the switch to the Orbi, and it now works (same kind of thing). I conneted the other 4 devices to the switch and they worked as well. Support told me to call them if I had problems again.
After hanging up, I connected the QNAP NAS box I have, and custom LInux box. Within a few minutes, I had lost wired device connections. I unplugged the LInux box and then wired connections came back up.
I checked the LInux box and it was stuck trying to boot up. I reset it, booted. Connected to the ORbi (directly), and all is working again.
So, seems like maybe the Linux box (Ubuntu 18.04) is affecting the Orbi. This box is configured with two static IP addresses (using a sub-interface), one interface is used for local-network and one is used for VPN (pport-forwarding) from the outside, using DDNS. I use this box as a file server, VPN server, SQL server, SSH server,...
I haven't conteacted Netgear yet. I want to see if it works for a week. The questions are...
- Why would it fail after several days?
- Why would the failure/issue affect all wired devices?
- What is the issue actually?
Some devices don't get a DHCP address, all devices have link up, and the static IP devices don't have access, even though they have link up some connected through switch, some through diect connect. And yes, all static IP devices are outside of the DHCP pool being used .2 -.100.
FURRYe38
Jan 06, 2019Guru - Experienced User
Interesting. Sounds like this NAS was the actual culprit. I wouldn't think it would be.
What Static IPs were you using on the NAS?
Sounds like something on the NAS wasn't not either configured right maybe causing some conflic on the main network or there was some forum of collison. Possible IP address bad state on the NAS as well. This would effect any wired connections with the switch and Orbi. Does this NAS support IGMP procols by chance or have any form of using them? Just curious.
If all is working after you took the NAS off line and when you put it back online before you reset it. Something in the NAS configuration as amiss, after you reset it and set up up again, seems to work however keep an eye on it.
You might do a search for your MFr and model# NAS to see if there are any known issues with it or any configurations that could cause Wired problems.
if your using 192.168.1.static IP address above .100 for your NAS, should be good.
Let us know how it goes...
- pc_mJan 07, 2019Aspirant
It's not the NAS box, it is a custom built Linux computer running Ubuntu 18.04 64bit desktop OS. This box is my VPN server, file server, SSH server, Samba server, database server, etc. and has been working fine for several years (OS updated to 18.04 from 16.04 a few months ago and always kept up to date). The NAS box I have is currently just being used for RAID backup of other systems.
The linux box in question is not running any special protocols. It is using a static IP (ending in .230) on a class A network, that is outside of the DHCP pool (.2-.100). No other static IP devices conflict with this system - remember this is a working network that I've had up for years.
It does have two IP addresses on the network. One on a main interface and one on a sub-interface (instead of having two physical interfaces). IIRC, this was set up for VPN with one IP being port forwarded to from the WAN IP using DDNS. The other is used for local traffic.
I'm concerned about the fact that this runs for 4-5 days before failing, which doesn't make sense if there is a configuration issue. Also, the Orbi doesn't seem to recover, once in a failed state.
I will keep monitoring this setup closely and see if/when it fails again.
- FURRYe38Jan 07, 2019Guru - Experienced User
Very odd for sure. Let us know how it goes.
Possible something happening between the two adapters or the configuration there of. Something to maybe contact the support community of Ubuntu about.