- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Forgive me if this has been covered before. I tried doing a search, but I couldn't find out exactly what I needed and I'm pulling my hair out.
I have a Netgear ReadyNAS that I use as a media file server for my PS3. A torrent client, Transmission, is also running on the NAS. It's hard-wired to my Verizon router (MI424WR) and I am able to access the admin settings and Transmission within my LAN, but I can't get it to work via the internet. I'm pretty sure I have this set up correctly as a static IP. The dynamic DHCP range is 192.168.1.5 - 192.168.1.254 and the IP for the ReadyNAS is 192.168.1.3 with the lease type set to static.
I access the admin settings on the LAN using https://192.168.1.3/admin and logging in with my user name and password. I access Transmission using http://192.168.1.3:8181/transmission/web and again logging in, and Transmission is uploading/downloading correctly. However, I can't access either of these outside the LAN using my public IP (72.84.xxx.xxx). I've tried messing with the port forwarding settings, but no luck so far.
Under Remote Administration, I have all four of these checked:
- Using Primary HTTP Port (80)
- Using Secondary HTTP Port (8080)
- Using Primary HTTPS Port (443)
- Using Secondary HTTPS Port (8443)
Under Port Forwarding, these entries are automatically generated:
Networked Computer
Device Network Address Public IP Address Remote Host IP Address Protocols WAN Connection Type Status Action Networked Computer: localhost
Network Address: localhost
Public IP: (blank)
Remote IP: (blank)
Protocols: Verizon FiOS Service – TCP Any -> 4567
WAN Connection Type: All Broadband Devices
Networked Computer: 192.168.1.100
Network Address: 192.168.1.100:63145
Public IP: Verizon FiOS Service
Remote IP: Verizon FiOS Service
Protocols: Application - UDP Any -> 63145
WAN Connection Type: Broadband Connection (Coax)
Networked Computer: 192.168.1.3
Network Address: 192.168.1.3:51413
Public IP: (blank)
Remote IP: (blank)
Protocols: Transmission at 51413 - TCP Any -> 51413
WAN Connection Type: Any
Any idea what I'm missing?? Thanks.
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You stated that you have your NAS set to listen on the following ports:
- Using Primary HTTP Port (80)
- Using Secondary HTTP Port (8080)
- Using Primary HTTPS Port (443)
- Using Secondary HTTPS Port (8443)
However you have not set up any port forwarding to forward those ports to you NAS server. You should also have the following forward to your NAS IP:
TCP Any -> 80 (this one may not work as Verizon still blocks this port in some areas)
TCP Any -> 8080
TCP Any -> 443
TCP Any -> 8443
You link looked like it was using port 8181 so you would need to forward that as well.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You stated that you have your NAS set to listen on the following ports:
- Using Primary HTTP Port (80)
- Using Secondary HTTP Port (8080)
- Using Primary HTTPS Port (443)
- Using Secondary HTTPS Port (8443)
However you have not set up any port forwarding to forward those ports to you NAS server. You should also have the following forward to your NAS IP:
TCP Any -> 80 (this one may not work as Verizon still blocks this port in some areas)
TCP Any -> 8080
TCP Any -> 443
TCP Any -> 8443
You link looked like it was using port 8181 so you would need to forward that as well.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I have those four options checked under Remote Administration on the Verizon router, but I'm not sure that's correct. I'm pretty sure ReadyNAS uses port 443 for its UI, and I know Transmission uses 8181. But I'll try forwarding all of those ports when I get home this evening. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Those checkboxes are not for you NAS box. What those do is allow you to access your router's administration from outside your network which you probably don't want. You will want to uncheck those as you are wanting to use many of those ports to go to your NAS box.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, that makes sense. I was thinking those settings had to do with opening ports to all the devices on my LAN (including the NAS). Maybe that's why I can't get port forwarding to work. I'll give it a try tonight.
I wish I could bypass the Verizon router and go back to the D-Link router I was using when I had Comcrap...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Desperado wrote:I wish I could bypass the Verizon router and go back to the D-Link router I was using when I had Comcrap...
You can. Although it is a little more involved if you have Fios TV + internet. If you want to not use the Actiontec, you have to call Verizon and have them switch your ONT from MoCa to ethernet. Then you can pull the Actiontec and plug your router in to the ONT via ethernet. Here is a link to the different network configurations availible for Fios and the benefits/drawbacks of each.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. I do have both TV and internet, so I don't want to get into anything complicated that might interfere with either. It looks like switching from MoCa would prevent program guide data from getting to my STB. I definitely don't want that. Hopefully I can get port forwarding to work.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, I'm making progress! I am able to access Transmission over the internet, but when I try to connect to the NAS, I get a "404 Not Found" error.
I unchecked the four boxes under Remote Administration and added an entry under Port Forwarding:
TCP Any -> 443
TCP Any -> 80
TCP Any -> 8080
TCP Any -> 8181
TCP Any -> 8443
The NAS uses https for the UI, so I'm pretty sure it's using port 443. Am I missing something?
Thanks again for all the help!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Desperado wrote:OK, I'm making progress! I am able to access Transmission over the internet, but when I try to connect to the NAS, I get a "404 Not Found" error.
I unchecked the four boxes under Remote Administration and added an entry under Port Forwarding:
TCP Any -> 443
TCP Any -> 80
TCP Any -> 8080
TCP Any -> 8181
TCP Any -> 8443The NAS uses https for the UI, so I'm pretty sure it's using port 443. Am I missing something?
Thanks again for all the help!
Try using
https://youripaddress:443
where youripaddress is the WAN IP of the router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No dice. That takes me to a broken page I set up when I was messing around with php and mysql. I need to get rid of that, but I should be able to enter https://myipaddress/admin to get to the NAS. At least that's the way it worked with my D-Link router.