Ssl – WD Sentinel DX 4000 Remote Web Access requires port blocked by ISP. Is it possible to change the default ports

httpiissslstoragewindows-server-2008-r2

WD Sentinel DX 4000 Remote Web Access requires port blocked by ISP. Is it possible to change the default ports?

The ports required are 80 for HTTP, and 443 for HTTPS.

I can RDP into the server behind Western Digital's front end (itself apparently just an IIS web page presented through RDP), but wouldn't know where to begin to look to modify the default ports. I've been told it's possible, but even that, I'm not certain of.

I'm not, as I'm sure you can tell, any kind of professional admin. I'm just the guy that isn't scared of computers in my office, so I get these things tasked to me.

Best Answer

Ports 80 and 443 are blocked by your ISP? Time to get a new ISP. It doesn't appear you can change the ports used on this WSS device that I can see.

How do you know they are being blocked at the ISP level? It's more likely that there's a firewall at your location (possibly inside the WAN router or cable modem, or whatever is at your SMB) that you need to setup to allow 80 and 443 port forwarding through your WAN firewall into the WD Sentinel.

Do you have a firewall in between the DX4000 and the ISP? You could setup the rules there using PAT (port address translation) to do something like external_IP:88 redirects to DX4000_internalIP:80. However, it may get tricky if it doesn't also allow for external_IP:444 redirects to DX4000_internalIP:443 or requires both http and https during the connections. You might only need the SSL (2nd PAT) one if your users can go straight to that link.

Short of that, the only option I can think of is setting up a separate VPN than the built-in remote web access one on the DX4000 (either through the WAN firewall router or on a separate VPN server) that would get the users remote access into the network where they can directly access the DX4000.

Related Solutions

Ssl – Multiple Sites with SSL on IIS6

You can't use virtual hosts with SSL, so to host two sites both using SSL you have to have 2 ip addresses, each one with a specific host and ssl cert bound to it.

In short you need 2 ip addresses on your server, one bound to domain1.com, and one bound to domain2.com, and 2 IIS sites one for domain1.com, and one for domain2.com. They can both serve up the same content, but will need to be separate sites.

Apache supports something called SNI (see here) which allows you to do vhosts with SSL but this isn't support by IIS currently.

Trying to route outgoing http requests through VPN on Ubuntu Server 12.04

What you need is source policy routing to route responses to incoming connections out the EC2 gateway instead of the VPN. Assuming that your instance's internal IP is 1.0.0.20 with default gateway at 1.0.0.1, and VPN IP is 10.8.0.20:

Create named routing tables (only needs to be done once)

echo 10 ec2 >> /etc/iproute2/rt_tables
echo 11 vpn >> /etc/iproute2/rt_tables

Configure the new routing tables with a default route over their respective gateways

ip route add 1.0.0.0/24 dev eth0 table ec2
ip route add default via 1.0.0.1 table ec2
ip route add 10.8.0.0/24 dev tun0 table vpn
ip route add default via 1.0.0.1 table vpn

Add routing rules to select the correct routing table based on the source address
```
ip rule add from 1.0.0.20 lookup ec2
ip rule add from 10.8.0.20 lookup vpn
```

This should allow you to set the default gateway to be the VPN and still have incoming connections work.

What you could do instead however, is configure your application to explicitly bind to the VPN IP (10.8.0.20) when creating outgoing connections, which will cause all connections from that application to go over the VPN, but all other outgoing connections go out directly. If you can't configure your application to bind to the VPN IP, you could add an HTTP proxy server to do this part.

Best Answer

Related Solutions

Ssl – Multiple Sites with SSL on IIS6

Trying to route outgoing http requests through VPN on Ubuntu Server 12.04

Related Topic