NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SYNOLOGY NAS unable to connect to internet through Orbi 960 Satellite when connected directly to it
Orbi Mesh WiFi 6E System - AXE11000 - 3 pack - Black (RBKE963B) Firmware: V6.3.7.10_3.3.3 I have been using Orbis for several years now and recently migrated from a Orbi 5 to a Orbi 6E system w...
As I stated, the NAS cannot connect to the Internet. I am not trying to connect to it FROM the internet.
Nothing on the NAS can connect to Synology services... ie My Synology, Package Center, syncing time, etc.
When I follow the directions on this post (https://www.synoforum.com/threads/nas-connected-to-local-network-but-no-internet.6109/) and SSH into the NAS, it cannot even ping the router.
I feel like the Orbi is absolutely blocking the traffic, but I cannot find where in the Orbi interface to free it up.
All settings that drive the NAS are the same as all other items on my network, ie DHCP enabled, gateways are assigned by the router, etc.
Additionally, been using these steps as well to troubleshoot it: https://kb.synology.com/en-us/DSM/tutorial/Why_cant_I_connect_to_Package_Center
I have a feeling this isn't a Synology issue, but an Orbi issue.
It would be useful to eliminate the TRENDnet switch from the environment (temporarily)
With these items connected directly to the Orbi satellite:
- PC
- NAS
Does the NAS appear on the Orbi Attached Devices display with the correct IP address that is assigned to the MAC address?
After connecting to the NAS from the PC (SSH), is it now able to ping anything on the home network? (the Orbi router, for example?) On the internet? (I like ford.com)
Thank you for your reply.
I am not certain what putting the PC directly on the satellite will do for the NAS, as they can communicate regardless, and the PC isn't part of the NAS's DNS resolution. However, I have connected both PC and NAS directly to the Orbi Satellite as you requested.
The NAS does not show up in blocked, or connected devices. I even added it to the Approved devices list... each NIC was added to it.
In the Orbi's log, the only reference to the NAS is this:
[DHCP IP: (192.168.1.212)] to MAC address REDACTED_MAC_ADDRESS, Sunday, May 21,2023 07:22:01
There is no other reference to the mac address of the NAS in the log file (I just rebooted the Orbi, so it started the log file anew).
SSHing into the NAS still results in being unable to ping ford.com, or google.com.
Interestingly enough, when I ping, it resolves the IP address for the domain to the router. That does seem peculiar.. I have update the DNS setting of the NIC on the NAS to 8.8.8.8.
Nslookup ford.com returns:
ash-4.4# nslookup
> ford.com
Server: 8.8.8.8
Address: 8.8.8.8#53Non-authoritative answer:
Name: ford.com
Address: 192.168.1.1
;; Got bad packet: unexpected end of input
38 bytes
8a 6a 81 80 00 01 00 01 00 00 00 00 04 66 6f 72 .j...........for
64 03 63 6f 6d 00 00 1c 00 01 c0 0c 00 1c 00 01 d.com...........
00 00 00 00 00 00 ......Pinging the routers address returns nothing. It fails. It feels so much like the traffic is being black holed from the NAS when the router is receiving it...
And no, I don't have a pihole or anything like that on my network... 🙂
On a lark, I put NIC_2 of the NAS on the DENIED list. That doesn't stop me from accessing the NAS.
Remember, we put attached the PC and the NAS directly to the satellite. I am really having a hard time understanding out the Orbi's networking works...
In the Orbis log, there is nothing related to denying anything for NIC_2, just giving it its IP address (which, yes, it still does even though its on the denied list).
With the DNS set to 8.8.8.8, I did the NSLOOKUP again:
ash-4.4# nslookup ford.com
Server: 8.8.8.8
Address: 8.8.8.8#53Non-authoritative answer:
Name: ford.com
Address: 192.168.1.1
;; Got bad packet: unexpected end of input
38 bytes
71 77 81 80 00 01 00 01 00 00 00 00 04 66 6f 72 qw...........for
64 03 63 6f 6d 00 00 1c 00 01 c0 0c 00 1c 00 01 d.com...........
00 00 00 00 00 00 ......(not confident that my suggestions have been very helpful so far.....)
I notice in the Synology Installation manual for the 1522+, they show one Ethernet cable connected to port 1 of the NAS. (The product accepts up to five Ethernet connections, so there seems to be no reason why port 1 would be significant. Maybe multiple ports are not active until after the operating system is fully configured?)
What I would expect is that when port 1 of the NAS is connected to any of the LAN ports on the RBSE960 satellite, that within a few minutes the router Attached Devices display should show the MAC address of that port as "Connected" (to the satellite) and assigned the IP address that was defined in the LAN setup table. (Orbi status does not update instantly.)
The satellite's web page should also show the NAS MAC interface as connected with the correct IP. (If you have defined a "name" for the NAS interface, the satellite may show that as "unknown", but that's a different issue.)
My reason for turning off Access Control and removing that sophisticated switch is to reduce the number of potential variables.
Once the NAS appears in Attached Devices, then a computer that is not connected to that satellite should be able to ping the NAS.
Definitely think there is some weirdness.
As I have had the 1522+ for about 6 weeks now... you can imagine I have tried a lot of different things.
There is some oddball combination I havent quite figured out that allows ONE port to be active on the NAS, and only one.
At one point, I had NIC-1 on the NAS working, and was gleeful... even had it sending emails for like 2 weeks. But, that one NIC was all I could get working. For a NIC with 4 built-in NICs, not to be able to use any of them BUT one defeats the purpose of having them.
I thought I would try something different today. I put NIC-2 on the block list. Made sure there was only one NIC attached to the switch... and the ORBI showed it as blocked. I unblocked it, and now I can have NIC-1 and NIC-2 both active (I havent tried both at the same time, but thats for a different experiment).
I cannot get the 10G card to work to save my life.
It lights up, showing its at 2.5G on the switch... even gets an IP. But never gets internet access.
I did find some stuff in the Orbi "Armor" app that may be promising... I may need to spend some time there to see if perhaps that has been the issue. And that is only on my phone. I do really despise the mobile Orbi app.
I will let you know if I make more progress. Thanks for the assistance.