Connecting to a NAS via restricted ports is challenging.
Connecting to a NAS via restricted ports is challenging.
After finishing school today, I still couldn’t get the NAS configured for remote access. It looks like it’s going to be a challenge. I checked various ports, but no matter what I used, the outcome stayed consistent—I kept redirected back to the school’s Cisco site. To double-check, I enabled the router’s Remote Management feature; it opened its web interface and provided helpful information. When I tried logging in from my laptop connected via Ethernet, I managed to reach the router settings using the device’s IP address. However, accessing from outside the local network seemed blocked. My friend also tried logging in from home, and I used my phone’s LTE signal. It seems web access, FTP, or similar functions are out of reach. Even attempting port forwarding or ensuring UPnP was active didn’t help much.
I also noticed that regardless of the port, everything led back to the school’s login page. This suggests either web access or network configuration is blocked. I tried plugging the NAS directly into the wall using Ethernet, but the results were inconsistent—Navigator displayed the old gateway (192.168.0.1) instead of the school’s internet gateway (10.188.16.1). It looks like changing settings won’t work.
I came home still without a solution. The instructor mentioned I might have overlooked something simple, but they refused to explain further. I have two ideas: either connect the switch directly to the wall instead of the router, or try plugging the router into the switch while it’s connected to the wall. Either way, I’m unsure what will work.
The second idea about the workgroup name seemed less likely—my school computers still use “WORKGROUP,” and changing it to “memes” didn’t help. I’m not sure what’s causing this issue, but it’s frustrating. This situation is annoying, though it’s giving me some insight. Still, I’ll keep trying until I figure it out.
From outside the school LAN, yes, it would be impossible. You’d need to forward ports from their router just like you did with yours. There might be a hacky solution using a VPN for the NAS and port forwarding online, but it would only make sense if you really needed it to justify the effort and expense.
Sure, I’ll just check again tomorrow and see if there’s another way to approach it. Thanks for sharing your thoughts.
He should be able to reach it from his school network via your routers' WAN IP address, provided port forwarding is correctly configured. The main challenge lies on the Internet side. A key consideration is whether the school LAN uses client isolation, which might separate his PC and router into different VLANs.
I finally understood everything was in place. It had been set up without me realizing it, but I kept overanalyzing things—using web access, FTP, and other tools. The key came when I realized the connection wasn’t obvious because of a dongle and a hidden SSID. When I unplugged the router, it clicked into place. The teacher needed the Wi-Fi password, which helped confirm he was connected via Wi-Fi. Once the network was active, I checked File Explorer and found everything accessible. After organizing the files, I used FileZilla to move the 480GB data to a single folder on the NAS, which took a full day. I shared my experience hoping it might help others, even though it didn’t add much value. Thanks for all the suggestions!