Setup Windows Firewall on a Domain Controller

If you would like to enable Windows Firewall on a domain controller, you will want to consider the following exceptions to the firewall before going live. These exceptions are necessary if you want domain authentication and file and print sharing. I would also recommend enabling these ports so only the local network is the exception. Allowing “outside” access may be hazardous to your server’s health.

Enable program exceptions for lsass.exe and ntfrs.exe.exe which are found under %windir%\system32.

Enable port exceptions for ports 53 (TCP and UDP), 88 (TCP and UDP), 123 (UDP), 135 (TCP), 137 (TCP), 389 (UDP), 464 (TCP and UDP) and 636 (TCP).

Did this help, leave a comment…

IIS Won’t Start - The format of the network name is invalid.

The format of the network name is invalid.
If you see this error, make sure your server is actively listening on a bound ip address.

In a command prompt type the following:
httpcfg query iplisten
This will show you the IP addresses listening on port 80.

Note: If you receive an error that says, ‘httpcfg’ is not recognized as an internal or external command, operable program or batch file., then you will need to download the library. You can do so from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en

If your query comes up blank, simply type the following command:
httpcfg set iplisten -i ipaddress
Where the IP address is the one you want to listen on.
(You may need to reboot before these changes take effect.)

Finally you can start up IIS again with the following command:
iisreset

Enjoy!