Yes, LTT can resolve issues more quickly than Asus customer support.
Yes, LTT can resolve issues more quickly than Asus customer support.
When configuring AiMesh on Asus wireless routers, options include wired backhaul, wireless backhaul, or automatic negotiation between them. Refer to Asus' guidance on setting up a wired connection while preserving mesh functionality. I recommend retaining the wired link for stronger reliability compared to wireless, particularly in complex multi-level setups like yours. Keeping the wired path ensures consistent performance and simplifies management. Additionally, maintaining AiMesh avoids the need to generate new SSIDs, preventing clients from creating conflicting profiles that could disrupt file sharing across operating systems. However, you may need to address some setup steps beyond these recommendations. It seems migrating from Nest devices to Asus might have triggered network changes for your clients. On Windows systems, ensure all devices join the same Workgroup and that Network Discovery and File & Printer Sharing are correctly configured for Private, Guest, or Public profiles.
The sharing options are irrelevant when connecting remotely via desktop.
It’s configured for wired backhaul. The main concern was using the Ethernet cable on the 1G WAN/LAN port instead of a LAN port. Despite thinking it wouldn’t matter, the documentation advises using a yellow LAN port over a blue WAN port. Network Discovery is active with Private profiles enabled. When checking the Workgroup, a Synology setting suggested testing the router network, which led to a link about two or more routers being detected. It seems I might need to enable port forwarding manually. I’m planning to try setting it up automatically, though I’m not fully sure. This is something I should learn how to handle.
I usually avoid discussing issues in threads and prefer sharing solutions instead. It turns out I accidentally added an entry in my hosts file for my NAS, which made the DNS name point to the IP assigned by the old router. This was simple to fix once a friend suggested checking the DNS name rather than the IP address. Thanks for your input, everyone. Now, if you’ll pardon me, I need to eat a humble pie.