Security for a day

We were splitting two web sites to two new servers from the existing one. The sites all worked and resolved internally, so created a new web publishing rules on the ISA for the relocated sites and their host header names.

When attempting to access the web site number two the web page displayed:

Bad Request (Invalid Hostname) – 400 Error

The web sites still worked internally and the ISA could resolve the server host headers and browse the sites. The rule looked good, pointed to the right location had the right ports open.

Turned on logging and watched for access to the site. No hits. Muck around checking event logs, restarting the firewall services and tweaking the rule. No joy.

Got a pencil and paper out and went through my deployment notes, ticking off each step. Got the web listener for site two and immediately found the problem. I had done a copy and paste of the rule and web listener and hadn’t changed the IP address of the second web listener to it new address. It was still using the first listener IP.

Added the correct IP address and everything worked as expected.

Meep