Connecting to a NAS via restricted ports is challenging.
Connecting to a NAS via restricted ports is challenging.
Hello everyone. I'm an IT student handling a side project assigned by my teacher. He asked me to configure a NAS on a switch, which is linked to a router connected via Ethernet to the school's internet. The goal is for him to view the NAS contents using his computer in another room. His machine isn't connected to the switch or router directly—it's plugged into the school network over Ethernet. I'm trying to set up Web Access on the NAS so remote access works, but so far I've only managed basic file sharing through File Explorer with the command //TS1200DA29. That doesn't meet the expected functionality. After reviewing the settings, I attempted to enable Web Access and found an error indicating a connection refusal, possibly due to blocked ports. I checked various ports using online tools and found that port 443 was open, but when trying to access the site it didn’t work as intended. I also looked into DHCP and static IP configurations without success. The router and switch seem fine, but the issue might lie with the school's network setup itself. I'm considering FTP as an alternative method, possibly using FileZilla, though I'm unsure how that would resolve the port problem. I've noted several points for future reference: blocked ports, lack of proper configuration, and the possibility that the problem is on the school side rather than my end. I'm open to suggestions and ideas to try next time.
It looks like you're trying to connect to another desktop. You should be able to ping it now. Once connected, you can configure the network as usual using the system's local IP address.
It seems we should have been aware from the start since all connections ultimately go through the server room. The NAS settings include a feature to check devices, but it only responded to computers linked via the switch. My laptop was plugged directly into an Ethernet port in the wall, which connects to the server room; the NAS failed to reach it. I plan to test using CMD to see if I can ping a device connected to the switch from my laptop.
I mentioned that I don’t actually have access to it, especially since it’s far from my IT class. It was just something my teacher decided to include one day, but from what I see, I might have to give up halfway through.
I believe we should focus on the purpose behind this request. Is it meant to challenge your understanding or serve a practical need? If the router is already linked to the main school network, shouldn’t it be simpler to connect the NAS directly instead of using a router in the middle? The key issue appears to be enabling port forwarding on the router so that traffic from the school network reaches the NAS.
He seems to have chosen this task randomly, often when he feels the need. It probably tests my understanding. Regarding the NAS connection, I’m not entirely sure. He mentioned wanting to view files on his computer, which is in another room connected to the school network, while the NAS is linked to a switch or router. I was wondering what would happen if I connected the NAS directly to the wall using Ethernet instead of through the router/switch. I agree it might be related to a port issue, but the instructor doubts it. When I tried accessing the NAS via Web Access and displayed the page (using port 443 on the NAS settings), he just gave me a confused expression without offering any explanation.
It relies on the method you use to connect to the NAS. You may need to redirect ports on your router. The "shrug" might indicate you should handle this yourself.
I understand the distinction between wanting guidance independently and feeling dismissed when you ask for help. Thanks for sharing your thoughts. Tomorrow will bring another attempt.