Enabling Windows Firewall on Windows 2003 Active Directory Domain Controller

Some time ago I discovered that my (two) Active Directory controllers weren’t actually talking to each other too well. After some debugging I found that the local Windows Firewall was enabled on one of the AD controllers and it was basically blocking everything that had to do with AD. So I disabled it and all was well. All servers are located behind a firewall anyway, so the risk was minimal.
Now I thought it was about time to enable the firewall on my AD controllers again. And it turns out that, as usual, Microsoft lets the ports flow wild. There are three services that don’t have a fixed port: NTDS, NTFrs and NetLogon. Without a fixed port it is difficult to enable firewall for them. The local firewall can enable based on process, but my external can’t.
The good news is that you can set fixed ports for these services. This is described in the knowledge base article http://support.microsoft.com/kb/555381.
But who wants to read all that?
Here is the short version:

1. Change registry to set fixed ports either by follow the knowledge base article or simply by running this .reg-file.
   Note: As always when downloading .reg-files have a look at it first to see what it actually does.
   Download, unzip, execute .reg-file, answer yes to question about importing it:
   Win2003 AD DC Lock Ports NTDS-NTFrs-NetLogon.zip
2.  Reboot the AD-controller.
3.  Note that if all servers are on same subnet you can increase security a lot by setting Scope to “My network (subnet) only”.

Enable Windows Firewall and set the following rules: