WD Live TV - Gen 3 - Port forwarding - 80 or 443, neither work

I’m trying to remotely access the WD TV Live (gen 3) internal webpage via port forward on my Netgear router.  When inside my network I type the IP address into my browser and I get the login, can control remotely etc.  However, when outside my LAN with entry via my router, I can’t access the WD Live.  I called tech support who said ports 80 and 443 are the ones to try, but that has not been successful.  With other devices I can either configure the router with uPNP, or manually set it up, including telling the other devices (such as my QNAP NAS, or IP webcam) to use different ports. But here I can’t, from the WD internal page, see which port is says it is using, nor alter it.

Any ideas?

Thasnk,

David.

Hi,

l still Have to configure my new wd live…

I gesso PAT will be’ necessary… I.e I’m afraid We small reach out router on a different port, patted on the wd 80 tap port.

example if you pat internal wd iP addr 192.168.1.10:80 with port 1080 and your outer router ip addr is 10.9.78.210 you should browse http://10.9.78.210:1080 to reach your wd … give it a try!

s.

Why are you needing to access the WD Web via the internet?  There’s not much you can do with it…

External use:  so I can remotely control what my kids are watching.

As for the earlier comments - I didn’t follow how the WD live can be confiugured to use port 1080, as opposed to 80. 

DavidAB wrote:

External use:  so I can remotely control what my kids are watching.

How do you intend to do that?  Just using the web remote and pressing STOP all the time?

When you’re on your LAN and access the player with just IP (not specifying a port) that means it’s using port 80.  Your browser automatically makes connections on port 80 if you’re using standard http.  If you’re using https like https://192.168.1.20 then you’re connecting on port 443. 

To access the web interface from outside your LAN you would forward TCP ports 80 and/or 443 to the internal IP of your player on your router, then access the web page using your public IP instead of the private (LAN) IP.  To find your public IP go to a site like www.whatismyip.com from a browser inside your lan. 

For example, if your public IP is 173.45.6.22 you would access the player using http://173.45.6.22 if you forwarded port 80, or https://173.45.6.22 if you forwarded port 443.

If you can do port translation on your router you can pick an arbitrary port number to connect to externally and forward it to the standard port 80 or 443 internally.  For example, you could forward external connections to port 10000 to port 80 on the player’s LAN IP.  In this case using the public IP mentioned previously you would access the player using http://173.45.6.22:10000.  Specifying the port in the browser is only necessary if you’re using anything other than standard http (80) or https (443).  Not all routers are able to do port translation.

Hope this helps!

I tried it.  It appears that the WD web server policy doesn’t allow requests from off-network IP addresses.

Thanks - that is exactly the behaviour I am trying to overcome,having aleady tried port forwarding 80 and 443.  Why would WD put such restrictions in place?  Is that a common occurrance for other devices as well?

TonyPh12345 wrote:


DavidAB wrote:

External use:  so I can remotely control what my kids are watching.


How do you intend to do that?  Just using the web remote and pressing STOP all the time?

 

 

 

Rather put Parental password  …

TonyPh12345 wrote:

I tried it.  It appears that the WD web server policy doesn’t allow requests from off-network IP addresses.

There are a few options in this case - none of them very appealing unfortunately.

  1.  If you have an advanced router and know what you’re doing you could port forward and do some fancy things with NAT to make the incoming traffic look like it originates from the LAN.

  2. VPN - some VPN solutions assign the client an IP on the same LAN.

  3.  Remote desktop type access (RDP, VNC, TeamViewer, LogMeIn, etc) to a machine on the LAN from which you could launch the web interface.