"Leighton Earl" <leighton.e***@gmail.com> wrote in message
news:da90d4f3.0504040844.61876686@posting.google.com...
>I have installed SP1 on one of our Windows 2003 domain controllers.
> Unfortunately the Windows firewall is applying the non domain policy
> which blocks everything. I think this is because this registry key has
> a null value:
> NKLM\software\microsoft\windows\currentversion\group
> policy\history\networkname
>
> sourced from:
> http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
>
> Other servers have correctly assigned network names, it seems only our
> domain controllers suffer from this.
>
> Why do only the domain controllers have null network names?

"Derek" <dseaman@nospam.nospam> wrote in message
news:elChcUUOFHA.2704@TK2MSFTNGP15.phx.gbl...
> I have the same problem. So for my DCs I used the 'standard' Firewall
> settings instead of 'domain'.
>
> "Leighton Earl" <leighton.e***@gmail.com> wrote in message
> news:da90d4f3.0504040844.61876686@posting.google.com...
> >I have installed SP1 on one of our Windows 2003 domain controllers.
> > Unfortunately the Windows firewall is applying the non domain policy
> > which blocks everything. I think this is because this registry key has
> > a null value:
> > NKLM\software\microsoft\windows\currentversion\group
> > policy\history\networkname
> >
> > sourced from:
> > http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
> >
> > Other servers have correctly assigned network names, it seems only our
> > domain controllers suffer from this.
> >
> > Why do only the domain controllers have null network names?
>
>

"jerry cantrell" wrote:

> I've seen this too, Null values on our DC's.
>
> jerry.
>
> "Derek" <dseaman@nospam.nospam> wrote in message
> news:elChcUUOFHA.2704@TK2MSFTNGP15.phx.gbl...
> > I have the same problem. So for my DCs I used the 'standard' Firewall
> > settings instead of 'domain'.
> >
> > "Leighton Earl" <leighton.e***@gmail.com> wrote in message
> > news:da90d4f3.0504040844.61876686@posting.google.com...
> > >I have installed SP1 on one of our Windows 2003 domain controllers.
> > > Unfortunately the Windows firewall is applying the non domain policy
> > > which blocks everything. I think this is because this registry key has
> > > a null value:
> > > NKLM\software\microsoft\windows\currentversion\group
> > > policy\history\networkname
> > >
> > > sourced from:
> > > http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
> > >
> > > Other servers have correctly assigned network names, it seems only our
> > > domain controllers suffer from this.
> > >
> > > Why do only the domain controllers have null network names?
> >
> >
>
>
>

"Leon2005" wrote:

> I have seen at least 2 customers of ours that have the same problem.
> Fortunately, they use our patch managment tool, Service Pack Manager...no you
> do not need to patch anything...but part of our tool is a Windows Firewall
> Manager, that is, without use of ActiveDirectory of GroupPolicies, so you can
> easily scan all your machines on the network and see what exactly is going
> on. You can correct you problem almost instantly - our tool is not dealing
> with StandardProfiles only with DomainProfiles and thus it rights 'empty'
> standard profile and whatever you configure for DomainProfile and then resets
> the firewall (no reboot needed). There are some screenshots available at:
> www.securitybastion.com/SPM-WF-Screenshots.doc
>
>
> "jerry cantrell" wrote:
>
> > I've seen this too, Null values on our DC's.
> >
> > jerry.
> >
> > "Derek" <dseaman@nospam.nospam> wrote in message
> > news:elChcUUOFHA.2704@TK2MSFTNGP15.phx.gbl...
> > > I have the same problem. So for my DCs I used the 'standard' Firewall
> > > settings instead of 'domain'.
> > >
> > > "Leighton Earl" <leighton.e***@gmail.com> wrote in message
> > > news:da90d4f3.0504040844.61876686@posting.google.com...
> > > >I have installed SP1 on one of our Windows 2003 domain controllers.
> > > > Unfortunately the Windows firewall is applying the non domain policy
> > > > which blocks everything. I think this is because this registry key has
> > > > a null value:
> > > > NKLM\software\microsoft\windows\currentversion\group
> > > > policy\history\networkname
> > > >
> > > > sourced from:
> > > > http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
> > > >
> > > > Other servers have correctly assigned network names, it seems only our
> > > > domain controllers suffer from this.
> > > >
> > > > Why do only the domain controllers have null network names?
> > >
> > >
> >
> >
> >

"Leon2005" wrote:

> I have seen at least 2 customers of ours that have the same problem.
> Fortunately, they use our patch managment tool, Service Pack Manager...no you
> do not need to patch anything...but part of our tool is a Windows Firewall
> Manager, that is, without use of ActiveDirectory of GroupPolicies, so you can
> easily scan all your machines on the network and see what exactly is going
> on. You can correct you problem almost instantly - our tool is not dealing
> with StandardProfiles only with DomainProfiles and thus it rights 'empty'
> standard profile and whatever you configure for DomainProfile and then resets
> the firewall (no reboot needed). There are some screenshots available at:
> www.securitybastion.com/SPM-WF-Screenshots.doc
>
>
> "jerry cantrell" wrote:
>
> > I've seen this too, Null values on our DC's.
> >
> > jerry.
> >
> > "Derek" <dseaman@nospam.nospam> wrote in message
> > news:elChcUUOFHA.2704@TK2MSFTNGP15.phx.gbl...
> > > I have the same problem. So for my DCs I used the 'standard' Firewall
> > > settings instead of 'domain'.
> > >
> > > "Leighton Earl" <leighton.e***@gmail.com> wrote in message
> > > news:da90d4f3.0504040844.61876686@posting.google.com...
> > > >I have installed SP1 on one of our Windows 2003 domain controllers.
> > > > Unfortunately the Windows firewall is applying the non domain policy
> > > > which blocks everything. I think this is because this registry key has
> > > > a null value:
> > > > NKLM\software\microsoft\windows\currentversion\group
> > > > policy\history\networkname
> > > >
> > > > sourced from:
> > > > http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
> > > >
> > > > Other servers have correctly assigned network names, it seems only our
> > > > domain controllers suffer from this.
> > > >
> > > > Why do only the domain controllers have null network names?
> > >
> > >
> >
> >
> >