Draytek Vigor Router Port Forwarding
KB ID 0000425 Problem This procedure was carried out on a Draytek Vigor 2800 Router, for this I needed to forward RDP (That’s on TCP Port 3389). Warning: If you need to forward any of the following ports 23 (Telnet), 80 (HTTP) , 443 HTTPS/SSL), 21 (FTP), or 22 (SSH). The Draytek has these reserved for remote management. You will need to change the port number (system Maintenance > Management > Management Port Setup)....
IIS – ‘This Web site cannot be started. Another Web site may be using the same port’.
KB ID 0000660 Problem After being unable to access my Exchange Management console, it turns out the default website had stopped. When I attempted to start it I was greeted with this error. Solution 1. Nothing was using the usual web ports (80 and 443) which I found out by running the following two commands; netstat -aon | find “:80″</p> <p>netstat -aon | find “:443” Note: If you do have a process...
Exchange – Redirect OWA (HTTP to HTTPS)
KB ID 0000697 Problem Out of the box, Exchange (quite rightly) secures Outlook Web Access so that you have to access it via https. The problem is some of your users are used to accessing websites via http, (or simply typing a URL in their browser, without typing any prefix, so it defaults to http). If you try and access OWA via http://server.domain.com/owa.. There are a number of ways to get round this, the simplest is to redirect...
Redirect AnyConnect Browser Connections From HTTP to HTTPS
KB ID 0000707 Problem AnyConnect, is great for users, but most of them are not used to typing full URL’s into their browsers. Modern browsers will prefix your URL with ‘http://’ for you. That’s brilliant most of the time, but AnyConnect and SSL VPN need to go to ‘https://’. Wouldn’t it be good if your users typed vpn.petenetlive.com into their browsers, and instead of the browser...
CentOS – Setup the iptables Firewall
KB ID 0000938 Problem I was a little perturbed to find out the firewall on my CentOS web server was wide open today. My server setup notes yielded no clues, so it was time to put my ‘Linux Head’ on and fix it. Solution 1. Connect to the server via console or SSH. As I’m going to change the iptables config file lets back it up (always assume you are going to smash something!) cp /etc/sysconfig/iptables iptables.bak 2....