NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Jerome_Labla
Jan 29, 2023Aspirant
ORBI RBR350 (router) and Orbi Satellite ethernet ports not functional
My main setup : - Netgear modem D6200 - Netgear Orbi RBR350 + 1 Satellite - Netgear powerline 1200 - PC windows 10 - NAS Synology Hi everyone, I bought an Orbi pack more than one year ago i...
Jerome_Labla
Jan 29, 2023Aspirant
Thanks for your quick answer.
The D6200 is connected through an Ethernet cable, not phone splitter.
I wonder if there can be any consequences on the fact that the Hikvision camera is not functional when connected to the ethernet port of the Orbi Satellite (though the mapping on the orbi mob app shows it) ?
Another information : the camera has a fixed IP 192.168.0.30. But in the mapping of the orbi mobile app, it shows 192.168.0.64.
Jérôme
CrimpOn
Jan 29, 2023Guru - Experienced User
Jerome_Labla wrote:
The D6200 is connected through an Ethernet cable, not phone splitter.
In this case, the D6200 can be removed, leaving a single router (the Orbi), with every device connected to it.
Static IP address is a bit ambiguous.
- The traditional meaning is that the user has configured this IP address on the physical device itself. In this case, the device will accept only communications directed to that specific IP address. And, the IP subnet and gateway IPs have to be set correctly for the device to know how to communicate with other devices.
- What most Orbi users do is define a Reserved Address using the LAN Setup table in the router web interface. That way, when the device is powered on and uses the DHCP process to request an IP address, we can be confident that it will always get the same address from the router. There are some nuances in this process. Reserved Addresses should be separate from the "pool" of IP addresses used for other device. Also, Orbi's have a quirky DHCP mechanism and sometimes devices stubbornly keep using the same IP address until the router itself is turned off and on again. (A chore that I hate to do.)
I would try setting the camera to use DHCP to get an IP address like everything else does.
- Jerome_LablaJan 29, 2023Aspirant
Thanks again.
Duly noted regarding the camera connexion. I guess this is the issue I am facing.
I did change the IP adress to a fixed one, because first I used the camera connected through a powerline plug (+wire connexion). And I used the synology interface to monitor it. It was recommanded to do so.
Your explanation is very logical, and I will try to do so. Would you recommend any literrature/document I could read in this respect ?
Regarding the using of the ORBI instead of the D6200, this is what I intended to do, disconnecting completely the D6200 from my setup. But as explained in my first message, the internet connexion became unstable (sometimes working sometimes not), and all the other devices connected to the ethernet ports were visible from the orbi mobile app/orbi intereface within a PC browser. BUT connexion were not functional (couldn't print or access the NAS).
The NAS has also a fixed IP address, as well as the ethernet Hub. It has never been an issue when connected through the D6200.
regards
Jérôme
- CrimpOnJan 29, 2023Guru - Experienced User
Moving devices with Static IPs from one network to another can create unexpected problems. For example:
- It appears that the D6200 was using 192.168.0.x as the IP subnet.
- Orbi routers typically define the LAN subnet as 192.168.1.x.
- Thus, if a NAS with a Static IP of 192.168.0.XX is placed on an Orbi LAN that is defined as 192.168.1.x, devices told to connect to 192.168.0.XX will think, "that cannot be on the same subnet as I am, so I'll have to ask the Gateway to forward packets to that device." And, the NAS will say, "hmm. 192.168.1.something cannot be on the same subnet as I am, so I'll have to ask the Gateway to forward packets to wherever that is."
Probably would be good idea to verify that every device on the network is in the same IP subnet.
- Jerome_LablaJan 29, 2023Aspirant
Again thanks a lot. Pretty much sure you are all wright about this subnet issue. And I do remember that I fixed all the main IPs of my devices because I had conflicts issues with the DHCP.
I will try that. Pretty much sure it will solve everything.
I will let you know.
Regards
Jérôme