(Msg. 1) Posted: Wed Oct 01, 2008 4:42 am
Post subject: NETDIAG problem - SPN queries Archived from groups: microsoft>public>win2000>dns (more info?)
Using NETDIAG I found 3 errors on my Windows 2000 Domain Controller:
The first:
Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'RAS Async Adapter' may not be working
because it has not received any packets.
I'm expecting this is related to the running RRAS services on there.
They're not used anymore, so I'm seriously contemplating taking those
off anyway. Can't find the device in the device list, and of what I
could find on the net it's not really a problematic notice.
The second:
AutoConfiguration results. . . . . . : Failed
[WARNING] AutoConfiguration is in use. DHCP not available.
and a bit further down in the log:
Autonet address test . . . . . . . : Failed
[FATAL] All adapters are autoconfigured.
The DHCP servers are unreachable. Please check cables, hubs, and
taps.
The DHCP server is a hardware box on our network. I know it works, and
I know the server can reach it. The reason however for it to try for
DHCP is unknown, since it has a fixed IP adres set. I'm considering
this error to be ignorable. There is only one LAN card, and as stated:
it's not running DHCP.
Then we get the third (and possibly most annoying) problem:
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'SERVER1.DOMAIN.INTERNAL'.
[WARNING] Failed to query SPN registration on DC
'SERVER2.DOMAIN.INTERNAL'.
I found quite a few people running into this problem through a search
engine, but no real follow-ups or solutions on it... Except one page
that mentioned a Microsoft utility called SETSPN.EXE
Now with that utility the SPN (ServicePrincipalNames) can be verified
or even reset if needed.
Now when I try to reset this to the required settings through the
command SETSPN -R SERVER1, the following error appears:
Failed to crack name DOMIN\SERVER1 into the FQDN, (0) 1 0x2
When I try to ping the machine using it's name (SERVER1), it's FQDN
(SERVER1.DOMAIN.INTERNAL) or even it's full FQDN
(SERVER1.DOMAIN.INTERNAL.) it works normally. The IP is resolved and
no real issues are present. Using the FQDN to run the command (SETSPN -
R SERVER1.DOMAIN.INTERNAL) tells me it couldn't find the account
SERVER1.DOMAIN.INTERNAL.
Anyone have any idea if the SPN's listed are correct or not, or what
specifically might be the cause of my root problem (the warnings), or
even how to get SETSPN.EXE to run properly with the re-create switch?
(Msg. 2) Posted: Wed Oct 01, 2008 11:52 am
Post subject: Re: NETDIAG problem - SPN queries [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Hello Neko-,
How many DC's do you have in total? Please post an unedited ipconfig /all
from all. Did you run netdiag also on the other ones? Please post the complete
output from netdiag /v
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> Using NETDIAG I found 3 errors on my Windows 2000 Domain Controller:
>
> The first:
>
> Netcard queries test . . . . . . . : Passed
> [WARNING] The net card 'RAS Async Adapter' may not be working
> because it has not received any packets.
> I'm expecting this is related to the running RRAS services on there.
> They're not used anymore, so I'm seriously contemplating taking those
> off anyway. Can't find the device in the device list, and of what I
> could find on the net it's not really a problematic notice.
>
> The second:
>
> AutoConfiguration results. . . . . . : Failed
> [WARNING] AutoConfiguration is in use. DHCP not available.
> and a bit further down in the log:
>
> Autonet address test . . . . . . . : Failed
> [FATAL] All adapters are autoconfigured.
> The DHCP servers are unreachable. Please check cables, hubs, and
> taps.
> The DHCP server is a hardware box on our network. I know it works, and
> I know the server can reach it. The reason however for it to try for
> DHCP is unknown, since it has a fixed IP adres set. I'm considering
> this error to be ignorable. There is only one LAN card, and as stated:
> it's not running DHCP.
>
> Then we get the third (and possibly most annoying) problem:
>
> LDAP test. . . . . . . . . . . . . : Passed
> [WARNING] Failed to query SPN registration on DC
> 'SERVER1.DOMAIN.INTERNAL'.
> [WARNING] Failed to query SPN registration on DC
> 'SERVER2.DOMAIN.INTERNAL'.
> I found quite a few people running into this problem through a search
> engine, but no real follow-ups or solutions on it... Except one page
> that mentioned a Microsoft utility called SETSPN.EXE
>
> Now with that utility the SPN (ServicePrincipalNames) can be verified
> or even reset if needed.
>
> First off: a list of the SPN's on the machine:
>
> Registered ServicePrincipalNames for CN=SERVER1,OU=Domain
> Controllers,DC=DOMAIN,DC=INTERNALAL:
> MSSQLSvc/SERVER1.DOMAIN.INTERNAL:1433
> SMTPSVC/SERVER1
> SMTPSVC/SERVER1.DOMAIN.INTERNAL
> NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/SERVER1.DOMAIN.INTERNAL
> GC/SERVER1.DOMAIN.INTERNAL/DOMAIN.INTERNAL
> HOST/SERVER1.DOMAIN.INTERNAL/DOMIN
> HOST/SERVER1
> HOST/SERVER1.DOMAIN.INTERNAL
> HOST/SERVER1.DOMAIN.INTERNAL/DOMAIN.INTERNAL
> E3514235-4B06-11D1-AB04-00C04FC2DCD2/7b0b58c0-8a12-4906-
> b856-5771f3505e43/DOMAIN.INTERNAL
> LDAP/7b0b58c0-8a12-4906-b856-5771f3505e43._msdcs.DOMAIN.INTERNAL
> LDAP/SERVER1.DOMAIN.INTERNAL/DOMIN
> LDAP/SERVER1
> LDAP/SERVER1.DOMAIN.INTERNAL
> LDAP/SERVER1.DOMAIN.INTERNAL/DOMAIN.INTERNAL
> DNS/SERVER1.DOMAIN.INTERNAL
> Now when I try to reset this to the required settings through the
> command SETSPN -R SERVER1, the following error appears:
>
> Failed to crack name DOMIN\SERVER1 into the FQDN, (0) 1 0x2
>
> When I try to ping the machine using it's name (SERVER1), it's FQDN
> (SERVER1.DOMAIN.INTERNAL) or even it's full FQDN
> (SERVER1.DOMAIN.INTERNAL.) it works normally. The IP is resolved and
> no real issues are present. Using the FQDN to run the command (SETSPN
> -
> R SERVER1.DOMAIN.INTERNAL) tells me it couldn't find the account
> SERVER1.DOMAIN.INTERNAL.
> Anyone have any idea if the SPN's listed are correct or not, or what
> specifically might be the cause of my root problem (the warnings), or
> even how to get SETSPN.EXE to run properly with the re-create switch?
>
(Msg. 3) Posted: Thu Oct 02, 2008 3:32 am
Post subject: Re: NETDIAG problem - SPN queries [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
I got two DC's. One Windows 2000, and the other Windows 2003. Due to a
minor issue on the Windows 2003 (dubbed SERVER2) I was referred to the
command repadmin /syncall <replication partner>. Did that on both
servers to resolve a minor KCC warning in the DCDIAG of the Windows
2003 machine. That got resolved.
Then did the NETDIAG on the Windows 2000 (the problem SERVER1) machine
to see if the error was still there... The SPN issue seems to have
vanished. The DHCP things are still in there tho
To accomodate your request tho... (and I am aware this machine is
pretty busy):
IPCONFIG from the 2000 machine (SERVER1 which has the issue):
Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Failed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Connection
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this
adapter.
Gathering Winsock information.
Testing DNS
The DNS registration for SERVER1.DOMAIN.INTERNAL is correct
on all DNS servers
PASS - All the DNS entries for DC are registered on DNS server
'192.168.1.3' and other DCs also have some of the names registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for a Windows 2000 DC
Gathering the list of Domain Controllers for domain 'DOMIN'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain DOMIN ...
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information
WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this
adapter.
There are no WINS servers configured for this interface.
IPX test : IPX is not installed on this machine.
Global results:
IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{C7C96FB4-5166-4EE6-9288-6408A8A26AF2}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Failed
[FATAL] All adapters are autoconfigured.
The DHCP servers are unreachable. Please check cables, hubs, and
taps.
IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.
Default gateway test . . . . . . . : Passed
PASS - you have at least one reachable gateway.
NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
PASS - The NetBT is properly configured.
There is at least one interface where the <00> 'WorkStation
Service',
<03> 'Messenger Service', <20> 'WINS' names are defined and they
are
not in conflict.
Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 14
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :4
Description: RSVP TCP Service Provider
Provider Version :4
Max message size : Stream Oriented
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{C7C96FB4-5166-4EE6-9288-6408A8A26AF2}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{C7C96FB4-5166-4EE6-9288-6408A8A26AF2}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{78275DF3-919B-4CA1-9E6F-1BF9E109A866}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{78275DF3-919B-4CA1-9E6F-1BF9E109A866}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{D772C0FC-8E51-45AC-940B-3A5C8A5E5145}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{D772C0FC-8E51-45AC-940B-3A5C8A5E5145}] DATAGRAM 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{FEE28DC8-
FB9B-4376-B8CD-15DE46376708}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{FEE28DC8-
FB9B-4376-B8CD-15DE46376708}] DATAGRAM 3
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{56556F62-2F07-4A6B-B83D-9290F79E4863}] SEQPACKET 4
Provider Version :2
Description: MSAFD NetBIOS [\Device
\NetBT_Tcpip_{56556F62-2F07-4A6B-B83D-9290F79E4863}] DATAGRAM 4
Provider Version :2
Max UDP size : 65507 bytes
DNS test . . . . . . . . . . . . . : Passed
Interface {C7C96FB4-5166-4EE6-9288-6408A8A26AF2}
DNS Domain: DOMAIN.INTERNAL
DNS Servers: 192.168.1.3
IP Address: 192.168.1.3
Expected registration with PDN (primary DNS domain name):
Hostname: SERVER1.DOMAIN.INTERNAL.
Authoritative zone: DOMAIN.INTERNAL.
Primary DNS server: SERVER1.DOMAIN.INTERNAL 192.168.1.3
Authoritative NS:192.168.1.2 192.168.1.3
Verify DNS registration:
Name: SERVER1.DOMAIN.INTERNAL
Expected IP: 192.168.1.3
Server 192.168.1.2: NO_ERROR
Server 192.168.1.3: NO_ERROR
The DNS registration for SERVER1.DOMAIN.INTERNAL is correct on all
DNS servers
Check the DNS registration for DCs entries on DNS server '192.168.1.3'
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 389 SERVER2.DOMAIN.INTERNAL
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 389 SERVER2.DOMAIN.INTERNAL
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is correct on DNS server '192.168.1.3'.
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.gc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 3268 SERVER2.DOMAIN.INTERNAL
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.gc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.gc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL
SRV 0 100 3268 SERVER2.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kerberos._tcp.dc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 88 SERVER2.DOMAIN.INTERNAL
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.dc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.dc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 88 SERVER2.DOMAIN.INTERNAL
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.dc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 389 SERVER2.DOMAIN.INTERNAL
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.dc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.dc._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL
SRV 0 100 389 SERVER2.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kerberos._tcp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 88 SERVER2.DOMAIN.INTERNAL
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 88 SERVER2.DOMAIN.INTERNAL
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _gc._tcp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 3268 SERVER2.DOMAIN.INTERNAL
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.Default-First-Site-Name._sites.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _gc._tcp.Default-First-Site-Name._sites.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 3268 SERVER1.DOMAIN.INTERNAL
SRV 0 100 3268 SERVER2.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kerberos._udp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 88 SERVER2.DOMAIN.INTERNAL
SRV 0 100 88 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 464 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kpasswd._tcp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 464 SERVER2.DOMAIN.INTERNAL
SRV 0 100 464 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 464 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _kpasswd._udp.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 464 SERVER2.DOMAIN.INTERNAL
SRV 0 100 464 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.d7859f82-62b2-4f2d-9ab8-
f7cff86417d9.domains._msdcs.DOMAIN.INTERNAL.
DNS DATA =
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL.
The record on DNS server 192.168.1.3 is:
DNS NAME = _ldap._tcp.d7859f82-62b2-4f2d-9ab8-
f7cff86417d9.domains._msdcs.DOMAIN.INTERNAL
DNS DATA =
SRV 0 100 389 SERVER2.DOMAIN.INTERNAL
SRV 0 100 389 SERVER1.DOMAIN.INTERNAL
+------------------------------------------------------+
The Record is correct on DNS server '192.168.1.3'.
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = DOMAIN.INTERNAL.
DNS DATA =
A 192.168.1.3
The record on DNS server 192.168.1.3 is:
DNS NAME = DOMAIN.INTERNAL
DNS DATA =
A 192.168.1.2
A 192.168.1.3
+------------------------------------------------------+
The Record is different on DNS server '192.168.1.3'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.3', no need to
re-register.
+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.DOMAIN.INTERNAL.
DNS DATA =
A 192.168.1.3
The record on DNS server 192.168.1.3 is:
DNS NAME = gc._msdcs.DOMAIN.INTERNAL
DNS DATA =
A 192.168.1.2
A 192.168.1.3
+------------------------------------------------------+
PASS - All the DNS entries for DC are registered on DNS server
'192.168.1.3' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{C7C96FB4-5166-4EE6-9288-6408A8A26AF2}
The redir is bound to 1 NetBt transport.
List of transports currently bound to the browser
NetBT_Tcpip_{C7C96FB4-5166-4EE6-9288-6408A8A26AF2}
The browser is bound to 1 NetBt transport.
Mailslot test for DOMIN* passed.
DC discovery test. . . . . . . . . : Passed
Find DC in domain 'DOMIN':
Found this DC in domain 'DOMIN':
DC. . . . . . . . . . . : \\SERVER1.DOMAIN.INTERNAL
Address . . . . . . . . : \\192.168.1.3
Domain Guid . . . . . . : {D7859F82-62B2-4F2D-9AB8-
F7CFF86417D9}
Domain Name . . . . . . : DOMAIN.INTERNAL
Forest Name . . . . . . : DOMAIN.INTERNAL
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV
WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum
Home
Forums
Home
FAQ
Profile
Private Messages
Log in
Windows Other