When I run netdiag om my dc (the only one in the domain) I get this error:
DNS test . . . . . . . . . . . . . : Failed
[FATAL] File \config\netlogon.dns contains invalid DNS
] No DNS servers have the DNS records for this DC registered.

When I run dcdiag it get this:
Testing server: Default-First-Site-Name\PRIMARY
Starting test: Connectivity
PRIMARY's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(89c7dd51-3c74-4366-8fb4-79c6a109e256._msdcs.NAGICO.com) couldn't be
resolved, the server name (primary.NAGICO.COM) resolved to the IP
address (192.168.0.25) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... PRIMARY failed test Connectivity

When I go in the DNS everything seems fine... how can I fix this error?
Thanks

Vincent

Do you have applied the win2000 sp4?

If you do, I posted in this news on Jul 19 2003 11:45AM a
problem with the netlogon service, that I think in some
way related with this.

Manually enter in your DNS zone an alias record
named "89c7dd51-3c74-4366-8fb4-79c6a109e256"
in "_msdcs.NAGICO.com" path pointing
to "primary.NAGICO.COM".

If this corrects this particularly error, stop and restart
the netlogon service, check in the system event for a
warning in the netlogon with event id 5781. If it is
there, my dear fellow, the DNS is not being updated with
the contents of "MIcrosoftDNS" object from the AD. This
only happens after applying the SP4 for win2000.

I think for now that we can survive if we manually enter
in the DNS zone the contents of the "netlogon.dns",
managed by the netlogon service.

Sorry but I do not have other solution.

Jose Vieira




>-----Original Message-----
>When I run netdiag om my dc (the only one in the domain)
I get this error:
>DNS test . . . . . . . . . . . . . : Failed
> [FATAL] File \config\netlogon.dns contains invalid
DNS
>] No DNS servers have the DNS records for this DC
registered.
>
>When I run dcdiag it get this:
>Testing server: Default-First-Site-Name\PRIMARY
> Starting test: Connectivity
> PRIMARY's server GUID DNS name could not be
resolved to an
> IP address. Check the DNS server, DHCP, server
name, etc
> Although the Guid DNS name
> (89c7dd51-3c74-4366-8fb4-
79c6a109e256._msdcs.NAGICO.com) couldn't be
> resolved, the server name (primary.NAGICO.COM)
resolved to the IP
> address (192.168.0.25) and was pingable. Check
that the IP address is
> registered correctly with the DNS server.
> ......................... PRIMARY failed test
Connectivity
>
>When I go in the DNS everything seems fine... how can I
fix this error?
>Thanks
>
>Vincent
>
>
>.
>

thanks a lot..that erro got fixed.
I deleted my nagico.com zone already. After I recreated it, it did not
create the other folders....
Is there a fix for that too?

Vincent

"Jose Vieira" <(E-Mail Removed)> wrote in message
news:052701c34e58$20af6500$(E-Mail Removed)...
> Do you have applied the win2000 sp4?
>
> If you do, I posted in this news on Jul 19 2003 11:45AM a
> problem with the netlogon service, that I think in some
> way related with this.
>
> Manually enter in your DNS zone an alias record
> named "89c7dd51-3c74-4366-8fb4-79c6a109e256"
> in "_msdcs.NAGICO.com" path pointing
> to "primary.NAGICO.COM".
>
> If this corrects this particularly error, stop and restart
> the netlogon service, check in the system event for a
> warning in the netlogon with event id 5781. If it is
> there, my dear fellow, the DNS is not being updated with
> the contents of "MIcrosoftDNS" object from the AD. This
> only happens after applying the SP4 for win2000.
>
> I think for now that we can survive if we manually enter
> in the DNS zone the contents of the "netlogon.dns",
> managed by the netlogon service.
>
> Sorry but I do not have other solution.
>
> Jose Vieira
>
>
>
>
> >-----Original Message-----
> >When I run netdiag om my dc (the only one in the domain)
> I get this error:
> >DNS test . . . . . . . . . . . . . : Failed
> > [FATAL] File \config\netlogon.dns contains invalid
> DNS
> >] No DNS servers have the DNS records for this DC
> registered.
> >
> >When I run dcdiag it get this:
> >Testing server: Default-First-Site-Name\PRIMARY
> > Starting test: Connectivity
> > PRIMARY's server GUID DNS name could not be
> resolved to an
> > IP address. Check the DNS server, DHCP, server
> name, etc
> > Although the Guid DNS name
> > (89c7dd51-3c74-4366-8fb4-
> 79c6a109e256._msdcs.NAGICO.com) couldn't be
> > resolved, the server name (primary.NAGICO.COM)
> resolved to the IP
> > address (192.168.0.25) and was pingable. Check
> that the IP address is
> > registered correctly with the DNS server.
> > ......................... PRIMARY failed test
> Connectivity
> >
> >When I go in the DNS everything seems fine... how can I
> fix this error?
> >Thanks
> >
> >Vincent
> >
> >
> >.
> >

In news:#(E-Mail Removed),
Vincent Haakmat [393242] <(E-Mail Removed)> posted his concerns then I
replied down below:
> thanks a lot..that erro got fixed.
> I deleted my nagico.com zone already. After I recreated it, it did not
> create the other folders....
> Is there a fix for that too?
>
> Vincent
>
You mean when you deleted and recreated the zone, the SRV folders (the ones
with the underscores) didn't show up?

Have you tried this to force them:

cmd prompt
ipconfig /registerdns
net stop netlogon
net start netlogon

If they still don't show up, check:

1. Primary DNS Suffix of the DC is set to NAGICO.COM (found in My Computer
Properties, Network ID tab, Properties, More).
2. NAGICO.COM zone has updates set to YES.
3. NAGICO.COM is spelled the same as the Primary DNS Suffix
4. Your machines are *only* pointing to this DNS server and no others, such
as your ISP's DNS or some other external DNS that does not host the AD zone
NAGICO.COM. This is very important.

Hope that helps. Curious about this SP4 issue in regards to the 5781 errors.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Yes I have tried all stuff you posted, also any
recommendations found on MS knowledge database regarding
5781 errors. None of them solved this issue.

I have distributed windows 2000 AD along 3 sites with 3 DC
in each on an privet LAN (9 DC's at total), working fine
in more than 1,5 years. After applied SP4 in all DC's the
netlogon service issue this error in all DC's.

I do not believe that is something wrong with this
network, because it is working for a long time and do not
have made changes in their structure or in their DC's.
Something is wrong with SP4. I'm shore.

Were can I report this problem to Microsoft?


Jose Vieira



>-----Original Message-----
>In news:#(E-Mail Removed),
>Vincent Haakmat [393242] <(E-Mail Removed)> posted his
concerns then I
>replied down below:
>> thanks a lot..that erro got fixed.
>> I deleted my nagico.com zone already. After I recreated
it, it did not
>> create the other folders....
>> Is there a fix for that too?
>>
>> Vincent
>>
>You mean when you deleted and recreated the zone, the SRV
folders (the ones
>with the underscores) didn't show up?
>
>Have you tried this to force them:
>
>cmd prompt
>ipconfig /registerdns
>net stop netlogon
>net start netlogon
>
>If they still don't show up, check:
>
>1. Primary DNS Suffix of the DC is set to NAGICO.COM
(found in My Computer
>Properties, Network ID tab, Properties, More).
>2. NAGICO.COM zone has updates set to YES.
>3. NAGICO.COM is spelled the same as the Primary DNS
Suffix
>4. Your machines are *only* pointing to this DNS server
and no others, such
>as your ISP's DNS or some other external DNS that does
not host the AD zone
>NAGICO.COM. This is very important.
>
>Hope that helps. Curious about this SP4 issue in regards
to the 5781 errors.
>
>--
>Regards,
>Ace
>
>Please direct all replies to the newsgroup so all can
benefit.
>
>Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
>Microsoft Windows MVP - Active Directory
>--
>=================================
>
>
>.
>

I did not add any other DNS entry except the one from the DC. I
Also, have SP3 installed. but I use SUS to update our computers and SUS
Admin gives these packages a SP4 tail.. so I assume these are Qxxx fixes
included in SP4.

Thanks
Vincent

"Ace Fekay [MVP]" <PleaseSubstituteMyFirstName&(E-Mail Removed)>
wrote in message news:(E-Mail Removed)...
> In news:#(E-Mail Removed),
> Vincent Haakmat [393242] <(E-Mail Removed)> posted his concerns then I
> replied down below:
> > thanks a lot..that erro got fixed.
> > I deleted my nagico.com zone already. After I recreated it, it did not
> > create the other folders....
> > Is there a fix for that too?
> >
> > Vincent
> >
>
> Vincent, I jsut want to confirm that you are only using your internal DNS
> server in the machine's IP Properties and there are no others listed (such
> as your ISP's)? This should be true for all internal machines in an AD
> environment.
>
>
> --
> Regards,
> Ace
>
> Please direct all replies to the newsgroup so all can benefit.
>
> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
> Microsoft Windows MVP - Active Directory
> --
> =================================
>
>

In news:#O$(E-Mail Removed),
Vincent Haakmat [393242] <(E-Mail Removed)> posted his concerns then I
replied down below:
> I did not add any other DNS entry except the one from the DC. I
> Also, have SP3 installed. but I use SUS to update our computers and
> SUS Admin gives these packages a SP4 tail.. so I assume these are
> Qxxx fixes included in SP4.
>
> Thanks
> Vincent
>
> "Ace Fekay [MVP]"
> <PleaseSubstituteMyFirstName&(E-Mail Removed)> wrote in
> message news:(E-Mail Removed)...
>> In news:#(E-Mail Removed),
>> Vincent Haakmat [393242] <(E-Mail Removed)> posted his concerns
>> then I replied down below:
>>> thanks a lot..that erro got fixed.
>>> I deleted my nagico.com zone already. After I recreated it, it did
>>> not create the other folders....
>>> Is there a fix for that too?
>>>
>>> Vincent
>>>
>>
>> Vincent, I jsut want to confirm that you are only using your
>> internal DNS server in the machine's IP Properties and there are no
>> others listed (such as your ISP's)? This should be true for all
>> internal machines in an AD environment.
>>
>>
>> --
>> Regards,
>> Ace
>>
>> Please direct all replies to the newsgroup so all can benefit.
>>
>> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
>> Microsoft Windows MVP - Active Directory
>> --
>> =================================

Ok, just wanted to confirm that part. I haven't heard anything back from the
newsgroup so not sure what's happening. I may send it to my lead.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

We also had a very similar problem occur after installing
SP4 on our DNS Server. We are currently paying for MS
support to look at the problem. I will post the solution
if we find one. So far we have had no luck.

Notes:
- Some registry entries for DNS are missing

- The _msdcs, _tcp, etc folders are not regenerating
after DNS reinstall.

- The only non-SP4 machine we have left on the network is
STILL ABLE TO REGISTER WITH THE DNS SERVER. (It's records
update as they should, which leads me to believe that
something is wrong with the DNS client service as well.)

- We are recieving 5781 errors in our event log.

- It does not appear to be related to permissions.

Good luck to everyone.

~ Michelle