Event ID 5788 & 5789, source Netlogon

[Kevin D. Goodknecht [MVP]]

In Scott Elgram <[email protected]> posted a question
Then Kevin replied below:
: Before deleting
: (same as parent folder) Host 192.168.0.0
: (same as parent folder) Name Server credentals.
: NsLookup gave me this;
:
: C:\>nslookup credentals
: *** Can't find server name for address 192.168.0.2: Non-existent
: domain
: *** Default servers are not available
: Server: UnKnown
: Address: 192.168.0.2
:
: *** UnKnown can't find credentals: Non-existent domain
:
: C:\>nslookup credentals.
: *** Can't find server name for address 192.168.0.2: Non-existent
: domain
: *** Default servers are not available
: Server: UnKnown
: Address: 192.168.0.2
:
: Name: credentals
: Addresses: 192.168.0.2, 192.168.0.0
:
: then I deleted
: (same as parent folder) Host 192.168.0.0
: (same as parent folder) Name Server credentals.
: and added a host Credentals with IP 192.168.0.2 and I got this;
:
: C:\>nslookup credentals
: *** Can't find server name for address 192.168.0.2: Non-existent
: domain
: *** Default servers are not available
: Server: UnKnown
: Address: 192.168.0.2
:
: Name: credentals.CREDENTALS
: Address: 192.168.0.2
:
:
: C:\>nslookup credentals.
: *** Can't find server name for address 192.168.0.2: Non-existent
: domain
: *** Default servers are not available
: Server: UnKnown
: Address: 192.168.0.2
:
: Name: credentals
:
: I haven't checked out the one workstation that was having the GPO
: issues but do you think this will fix that problem or is a migration
: really my only recourse at this point?
:

Can you ping credentals now?

Did you run ipconfig /flushdns?
Hmm, it still does not resolve the domain name.
A DCDIAG /v might tell us if this is going to do any good. Adding the
credentals host did give it the ability to resolve credentals the output is
kinda interesting It might work, never tested it though. It is not very
orthodox but it is worth a try.

You should still migrate but this _might_ hold things to gether until you
can do that.

 

[Ace Fekay [MVP]]

In

Before deleting
(same as parent folder) Host 192.168.0.0
(same as parent folder) Name Server credentals.
NsLookup gave me this;

C:\>nslookup credentals
*** Can't find server name for address 192.168.0.2: Non-existent
domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.2

*** UnKnown can't find credentals: Non-existent domain

C:\>nslookup credentals.
*** Can't find server name for address 192.168.0.2: Non-existent
domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.2

Name: credentals
Addresses: 192.168.0.2, 192.168.0.0

then I deleted
(same as parent folder) Host 192.168.0.0
(same as parent folder) Name Server credentals.
and added a host Credentals with IP 192.168.0.2 and I got this;

C:\>nslookup credentals
*** Can't find server name for address 192.168.0.2: Non-existent
domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.2

Name: credentals.CREDENTALS
Address: 192.168.0.2


C:\>nslookup credentals.
*** Can't find server name for address 192.168.0.2: Non-existent
domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.2

Name: credentals

I haven't checked out the one workstation that was having the GPO
issues but do you think this will fix that problem or is a migration
really my only recourse at this point?

In

There are 4 "(same as parent folder)' entries;
(same as parent folder) Host 192.168.0.0

<---This
is not a valid IP address is there another DC? Did someone add this
record? You should delete this record.

(same as parent folder) Host 192.168.0.2
(same as parent folder) Name Server credentals.
<---Delete (same as parent folder) Name Server
Mainserver.credentals. (same as parent folder) Start of
Authority [227], mainserver.credentals.,[email protected].

The "(same as parent folder) Name Server
credentals."
I just added to see if it would help. I don't know if it made a
differance though. I still get unknown host when i ping
credentals. However, if i ping mainserver (the name of the computer
on which the DC is running) or Mainserver.credentals i get a reply
192.168.0.2

I think the problem is the 192.168.0.0 record delete the record.
The only thing that might help and I cannot verify it is if you add
a Host named credentals with the IP 192.168.0.2, thinking about it
it would resolve to credentals.credentals with IP 192.168.0.2. That
way when the suffix "credentals" is appended to the host name
credentals it will resolve to the correct IP. I dunno, might help
shouldn't hurt.

Delete the NS record you created it is not a valid FQDN for a host NS
record.
try using nslookup to resolve the name credentals. (with a trailing
dot) and credentals with out the dot.

That is just a message (not an error) saying you do;'t have a reverse zone
created when nslookup upon initialization attempts to find the name of your
machine from your reverse zone for your subnet. No problem, either ignore it
and subsequenst commands will work, or create a reverse zone and make sure
there's a PTR for your DNS server's IP.

Note: This has NOTHING to do with your current issues.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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

 

[Ace Fekay [MVP]]

In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted their thoughts, then I offered mine

Hmm, nevermind about my post. I see you have a reverse.

As Kevin said, this will probably bandaid the current issue, but you may
still have problems with GPOs unitl (if you can) migrate.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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

 

[Scott Elgram]

Yes, I can ping credentals now. I get;
C:\>ping credentals

Pinging credentals.CREDENTALS [192.168.0.2] with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

so it's really only pinging the host 'credentals' which i inputed earlier.
I got a chance to check out the workstation too.....still no luck with the
GPO. I get the same errors as before. :-(

I did the DCDiag (although for some reason i got an error - "The procedure
entry point DsIsMangledDnW could not be located in the dynamic link library
NTDSAPI.dll." when i tried the one off Microsofts site. I found a working
one on http://www.versiontracker.com/dyn/moreinfo/win/18830 though. The
result was as fallows;

C:\>dcdiag /v

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine MAINSERVER, is a DC.
* Connecting to directory service on server MAINSERVER.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MAINSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... MAINSERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MAINSERVER
Starting test: Replications
* Replications Check
......................... MAINSERVER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=CREDENTALS
* Security Permissions Check for
CN=Configuration,DC=CREDENTALS
* Security Permissions Check for
DC=CREDENTALS
......................... MAINSERVER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... MAINSERVER passed test NetLogons
Starting test: Advertising
The DC MAINSERVER is advertising itself as a DC and having a DS.
The DC MAINSERVER is advertising as an LDAP server
The DC MAINSERVER is advertising as having a writeable directory
The DC MAINSERVER is advertising as a Key Distribution Center
The DC MAINSERVER is advertising as a time server
The DS MAINSERVER is advertising as a GC.
......................... MAINSERVER passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS
Role Domain Owner = CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS
Role PDC Owner = CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS
Role Rid Owner = CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS
......................... MAINSERVER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1605 to 1073741823
* MAINSERVER.CREDENTALS is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1105 to 1604
* rIDNextRID: 1279
* rIDPreviousAllocationPool is 1105 to 1604
......................... MAINSERVER passed test RidManager
Starting test: MachineAccount
* MAINSERVER is not trusted for account delegation
* SPN found :LDAP/MAINSERVER.CREDENTALS/CREDENTALS
* SPN found :LDAP/MAINSERVER.CREDENTALS
* SPN found :LDAP/MAINSERVER
* SPN found :LDAP/MAINSERVER.CREDENTALS/CREDENTALS
* SPN found
:LDAP/b7641fb7-1c27-48a8-9079-e42ef8f7dd54._msdcs.CREDENTALS
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/b7641fb7-1c27-48a8-9079-e42ef8f7dd54/C
REDENTALS
* SPN found :HOST/MAINSERVER.CREDENTALS/CREDENTALS
* SPN found :HOST/MAINSERVER.CREDENTALS
* SPN found :HOST/MAINSERVER
* SPN found :HOST/MAINSERVER.CREDENTALS/CREDENTALS
* SPN found :GC/MAINSERVER.CREDENTALS/CREDENTALS
......................... MAINSERVER failed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... MAINSERVER passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
MAINSERVER is in domain DC=CREDENTALS
Checking for CN=MAINSERVER,OU=Domain Controllers,DC=CREDENTALS in
domain DC=CREDENTALS on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=MAINSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Con
figuration,DC=CREDENTALS in domain CN=Configuration,DC =CREDENTALS on 1
servers
Object is up-to-date on all servers.
......................... MAINSERVER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
......................... MAINSERVER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... MAINSERVER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... MAINSERVER passed test systemlog

Running enterprise tests on : CREDENTALS
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope
provided by the command line arguments provided.
......................... CREDENTALS passed test Intersite
Starting test: FsmoCheck
GC Name: \\MAINSERVER.CREDENTALS
Locator Flags: 0xe00001fd
PDC Name: \\MAINSERVER.CREDENTALS
Locator Flags: 0xe00001fd
Time Server Name: \\MAINSERVER.CREDENTALS
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\MAINSERVER.CREDENTALS
Locator Flags: 0xe00001fd
KDC Name: \\MAINSERVER.CREDENTALS
Locator Flags: 0xe00001fd
......................... CREDENTALS passed test FsmoCheck