WHS2011 & IIS

Associate
Joined
16 Mar 2004
Posts
1,931
Location
Oxford
I've got my WHS2011 site setup to access files and created a directory on from this to show information on the backup, etc. This all forwards to port 80 on the router, so can be accessed by going to http://XXXXXXX.ddns.net.

I've also got a CCTV server setup that the router is port forwarding to 82, so has to be accessed by going to http://XXXXXXX.ddns.net:82. That works fine most of the time, however I've found the Wi-Fi where I work (staff have full permission to use this for personal use) blocks a lot of ports. Is it possible to get the server using ISS to point to the CCTV server at 192.168.1.237, so it can be accessed by just going to http://XXXXXXX.ddns.net/cctv.

WHS is running IIS 6.1. Any help greatly appreciated.
 
Chances are the wifi is blocking all "non essential" ports. What about changing the CCTV server port to something a little more standard such as the https 443 port?
 
The problem is the Wi-Fi blocks a lot of non-essential ports. I'll look into different ports with it, sadly port 443 is another one WHS uses. I might have to do a bit of trial and error from work when I'm next in by connecting to the home router via VPN via 3G and changing ports until something works. Ideally IIS would just forward a port eg; 82 to http://sitename.com/cctv/.

I've since read up a bit on it and it would appear IIS 6 won't allow HTTP redirect in this way, but is a feature in 7.5.
 
Frustratingly they've just completely blocked VPN access on the free Wi-Fi, hence this post. I'm actually in talks with someone from our IT dept over changing some of the frankly stupid restrictions. It's not even like it's a shared connection, the in house IT uses a 5Mb/sec connection, and the free Wi-Fi has its own 80Mb/sec FTTC connection!
 
This, or use a VPN.

Is the authentication information being sent in the clear?

Frustratingly they've just completely blocked VPN access on the free Wi-Fi, hence this post. I'm actually in talks with someone from our IT dept over changing some of the frankly stupid restrictions. It's not even like it's a shared connection, the in house IT uses a 5Mb/sec connection, and the free Wi-Fi has its own 80Mb/sec FTTC connection!

Port 25, 465, 993, 587, 53?

Port 443 was just an example. You could use literally any "standard" port providing the WHS IIS isn't using it already. Port 53 is probably a bad idea but its an example.
 
Back
Top Bottom