This may be RPC related - see:
http://support.microsoft.com/kb/154596/
The number of ports you need to open on a local network connection to a DC,
even without DHCP, makes the use of this kind of firewall questionable:
http://support.microsoft.com/default...b;en-us;179442
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Jamie" <(E-Mail Removed)> wrote in message
news:3F60F895-6694-4756-A741-(E-Mail Removed)...
> Hello,
>
> We have a number of 2003 Domain Controllers deployed at various sites.
They
> are currently 2003 SP1. We have just patched one of them to test before
> attempting the others. These servers are all built identically with same
> configuration (except root DC's). They also had the SCF run after initial
> configuration and DCPROMO.
>
> DHCP has stopped working on this server since the patches were applied. If
> we turn off Windows Firewall then it works again. We have enabled ports
67,
> 68 and various others that have been recommended but still DHCP will not
work.
>
> We are reluctant to patch rest of the servers or expand the infrastructure
> before resolving this issue. Whilst the windows firewall is on the private
> side of the network the office 2 office comms are via VPN so we would like
to
> use Windows Firewall if possible for added protection. These are not
> "private, leased" circuits.
>
> If you can shed any light on this it would be appreciated. We have gone
> through the updates but none of the descriptions seem to have anything to
do
> with DHCP and without de-installing them 1 by 1 we have no way of telling.
At
> the end of the day we will need which ever patch to be applied in future
so
> we would think it better to resolve it via slackening the firewall off
> instead of removing the patch.
> --
> Thanks
>
> Jamie