J
J
Hi all,
I have an AD DC setup as Forest root and GC for our internal
non-registered domain "ACLABS".
About a week ago I had complaints from an admin that his DNS queries
were bot returning the correct IP. I checked the records for the
various hosts and the records were indeed incorrect. This is a
supernet containing over 500 MAC and Windows machines. These machines
were once setup to use DHCP and have recently been mostly configured
static. The DHCP server (CISCO Sup1a in 6006) was setup to NOT hand
out addresses overlapping with these static ranges. All hosts are
configure with the primary DNS 172.16.32.4 as the only DNS server and
all Win2K/XP clients are set to register dynamically. The GC/DNS
server, ACLABSW2KSRV1, has only one IP and is aimed at itself for DNS
at its' IP 172.16.32.4. Now, upon checking on these incorrect DNS
entries I noticed that they were all very old records, months old. I
set the forward and reverse zones to scavenge them every two days. The
machines are reset frequently and should re-register themselves
quickly. I made this scavenge setting on a Friday and upon checking
the next Monday there was little to no change but I had other things
to attend to so I left it alone for a few more days. When I checked
the DNS a few days later there were hardly any entries for hosts, one
subdomain forward zone was missing and all AD service records
(_tcp,_mdns, etc) were gone. The Event Viewer had records in the DNS
log that mentioned scavenging over 470 records, I'm assuming that many
of these had to be the records for my missing hosts although I'm sure
some could be cached entries from my forwarders. I have since checked
out the following:
Disjointed namespace? The domain is currently spelled exactly the
same, "ACLABS" without quotes, when viewed from IPCONFIG /ALL, AD
Users & Computers, and the forward lookup zone which i have since
deleted and recreated.
After re-creating the forward lookup zone "ACLABS" I made sure the
zone was set to accept dynamic updates and then restarted DNS. It's an
AD integrated zone.
After doing IPCONFIG /FLUSHDNS, IPCONFIG /REGISTERDNS, and NET STOP
NETLOGIN && NET START NETLOGON and also then a restart, still no AD
Service records in the DNS forward zones.
Netdiag /fix fails with DNS registration errors.
Here is the unedited output from the standard commands:
IPCONFIG /ALL
----------------------------------------------------------------
C:\Documents and Settings\Hope>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : aclabsw2ksrv1
Primary DNS Suffix . . . . . . . : ACLABS
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ACLABS
Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:
Connection-specific DNS Suffix . : ACLABS
Description . . . . . . . . . . . : Intel(R) PRO/100 Network
Connection
Physical Address. . . . . . . . . : 00-06-5B-04-A1-BC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.32.4
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 172.16.32.1
DNS Servers . . . . . . . . . . . : 172.16.32.4
NETDIAG /FIX
-----------------------------------------------------------------
C:\Documents and Settings\Hope>NETDIAG /FIX
......................................
Computer Name: ACLABSW2KSRV1
DNS Host Name: aclabsw2ksrv1.ACLABS
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 10, GenuineIntel
List of installed hotfixes :
KB329115
KB823182
KB823559
KB823980
KB824105
KB824141
KB824146
KB825119
KB826232
KB828028
KB828035
KB828741
KB828749
KB830352
KB835732
KB837001
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Intel Fast Ethernet LAN Controller - onboard
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : aclabsw2ksrv1.ACLABS
IP Address . . . . . . . . : 172.16.32.4
Subnet Mask. . . . . . . . : 255.255.252.0
Default Gateway. . . . . . : 172.16.32.1
Dns Servers. . . . . . . . : 172.16.32.4
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
No remote names have been found.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name
'aclabsw2ksrv1.ACLABS.'. [RCODE_SERVER_FAILURE]
The name 'aclabsw2ksrv1.ACLABS.' may not be registered in
DNS.
[FATAL] Failed to fix: DC DNS entry ACLABS. re-registeration on
DNS server '
172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.ACLABS.
re-registeration on D
NS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.ACLABS.
re-registe
ration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.ACLABS.
re-register
ation on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.79338a3d-e090-453c-8a2e-080ec
3053db4.domains._msdcs.ACLABS. re-registeration on DNS server
'172.16.32.4' fail
ed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.ACLABS.
re-registeration on DN
S server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
62a4f21f-1ab3-4ac5-a625-ec5a945f382b._ms
dcs.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.dc._msdcs.ACLABS. re-regi
steration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.ACLABS.
re-register
ation on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.ACLABS.
re-registeration
on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.ACLABS.
re-registeration on DNS
server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.ACLABS.
re-registeration
on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.ACLABS.
re-registeration o
n DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.ACLABS.
re-registeration o
n DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.gc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.Default-First-Site-Name._
sites.dc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.dc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.Default-First-Site-Name._
sites.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_gc._tcp.Default-First-Site-Name._sites.
ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS
entries for th
is DC on DNS server '172.16.32.4'.
[FATAL] No DNS servers have the DNS records for this DC
registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'aclabsW2ksrv2.ACLABS'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.
The command completed successfully
DCDIAG
-----------------------------------------------------------------------------
C:\Documents and Settings\Hope>dcdiag
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\ACLABSW2KSRV1
Starting test: Connectivity
ACLABSW2KSRV1'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
(62a4f21f-1ab3-4ac5-a625-ec5a945f382b._msdcs.ACLABS) couldn't
be
resolved, the server name (aclabsw2ksrv1.ACLABS) resolved to
the IP
address (172.16.32.4) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... ACLABSW2KSRV1 failed test
Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ACLABSW2KSRV1
Skipping all tests, because server ACLABSW2KSRV1 is
not responding to directory service requests
Running enterprise tests on : ACLABS
Starting test: Intersite
......................... ACLABS passed test Intersite
Starting test: FsmoCheck
......................... ACLABS passed test FsmoCheck
---------------------------------------------------------------------------------------
Thanks in advance for ANY help in solving this. You may have noticed
I've been to the usual fixes on this and it ain't working.
Maybe somebody will notice this see something wrong, or just have that
magic bullet I'm looking for.
I am trying to AVOID doing DCPROMO here, badly.
Thanks again,
Jason
I have an AD DC setup as Forest root and GC for our internal
non-registered domain "ACLABS".
About a week ago I had complaints from an admin that his DNS queries
were bot returning the correct IP. I checked the records for the
various hosts and the records were indeed incorrect. This is a
supernet containing over 500 MAC and Windows machines. These machines
were once setup to use DHCP and have recently been mostly configured
static. The DHCP server (CISCO Sup1a in 6006) was setup to NOT hand
out addresses overlapping with these static ranges. All hosts are
configure with the primary DNS 172.16.32.4 as the only DNS server and
all Win2K/XP clients are set to register dynamically. The GC/DNS
server, ACLABSW2KSRV1, has only one IP and is aimed at itself for DNS
at its' IP 172.16.32.4. Now, upon checking on these incorrect DNS
entries I noticed that they were all very old records, months old. I
set the forward and reverse zones to scavenge them every two days. The
machines are reset frequently and should re-register themselves
quickly. I made this scavenge setting on a Friday and upon checking
the next Monday there was little to no change but I had other things
to attend to so I left it alone for a few more days. When I checked
the DNS a few days later there were hardly any entries for hosts, one
subdomain forward zone was missing and all AD service records
(_tcp,_mdns, etc) were gone. The Event Viewer had records in the DNS
log that mentioned scavenging over 470 records, I'm assuming that many
of these had to be the records for my missing hosts although I'm sure
some could be cached entries from my forwarders. I have since checked
out the following:
Disjointed namespace? The domain is currently spelled exactly the
same, "ACLABS" without quotes, when viewed from IPCONFIG /ALL, AD
Users & Computers, and the forward lookup zone which i have since
deleted and recreated.
After re-creating the forward lookup zone "ACLABS" I made sure the
zone was set to accept dynamic updates and then restarted DNS. It's an
AD integrated zone.
After doing IPCONFIG /FLUSHDNS, IPCONFIG /REGISTERDNS, and NET STOP
NETLOGIN && NET START NETLOGON and also then a restart, still no AD
Service records in the DNS forward zones.
Netdiag /fix fails with DNS registration errors.
Here is the unedited output from the standard commands:
IPCONFIG /ALL
----------------------------------------------------------------
C:\Documents and Settings\Hope>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : aclabsw2ksrv1
Primary DNS Suffix . . . . . . . : ACLABS
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ACLABS
Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:
Connection-specific DNS Suffix . : ACLABS
Description . . . . . . . . . . . : Intel(R) PRO/100 Network
Connection
Physical Address. . . . . . . . . : 00-06-5B-04-A1-BC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.32.4
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 172.16.32.1
DNS Servers . . . . . . . . . . . : 172.16.32.4
NETDIAG /FIX
-----------------------------------------------------------------
C:\Documents and Settings\Hope>NETDIAG /FIX
......................................
Computer Name: ACLABSW2KSRV1
DNS Host Name: aclabsw2ksrv1.ACLABS
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 10, GenuineIntel
List of installed hotfixes :
KB329115
KB823182
KB823559
KB823980
KB824105
KB824141
KB824146
KB825119
KB826232
KB828028
KB828035
KB828741
KB828749
KB830352
KB835732
KB837001
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Intel Fast Ethernet LAN Controller - onboard
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : aclabsw2ksrv1.ACLABS
IP Address . . . . . . . . : 172.16.32.4
Subnet Mask. . . . . . . . : 255.255.252.0
Default Gateway. . . . . . : 172.16.32.1
Dns Servers. . . . . . . . : 172.16.32.4
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
No remote names have been found.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name
'aclabsw2ksrv1.ACLABS.'. [RCODE_SERVER_FAILURE]
The name 'aclabsw2ksrv1.ACLABS.' may not be registered in
DNS.
[FATAL] Failed to fix: DC DNS entry ACLABS. re-registeration on
DNS server '
172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.ACLABS.
re-registeration on D
NS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.ACLABS.
re-registe
ration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.ACLABS.
re-register
ation on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.79338a3d-e090-453c-8a2e-080ec
3053db4.domains._msdcs.ACLABS. re-registeration on DNS server
'172.16.32.4' fail
ed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.ACLABS.
re-registeration on DN
S server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
62a4f21f-1ab3-4ac5-a625-ec5a945f382b._ms
dcs.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.dc._msdcs.ACLABS. re-regi
steration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.ACLABS.
re-register
ation on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.ACLABS.
re-registeration
on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.ACLABS.
re-registeration on DNS
server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.ACLABS.
re-registeration
on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.ACLABS.
re-registeration o
n DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.ACLABS.
re-registeration o
n DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.gc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.Default-First-Site-Name._
sites.dc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._site
s.dc._msdcs.ACLABS. re-registeration on DNS server '172.16.32.4'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.Default-First-Site-Name._
sites.ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_gc._tcp.Default-First-Site-Name._sites.
ACLABS. re-registeration on DNS server '172.16.32.4' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS
entries for th
is DC on DNS server '172.16.32.4'.
[FATAL] No DNS servers have the DNS records for this DC
registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{2AFBB961-9820-4F10-A82F-203258828557}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'aclabsW2ksrv2.ACLABS'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.
The command completed successfully
DCDIAG
-----------------------------------------------------------------------------
C:\Documents and Settings\Hope>dcdiag
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\ACLABSW2KSRV1
Starting test: Connectivity
ACLABSW2KSRV1'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
(62a4f21f-1ab3-4ac5-a625-ec5a945f382b._msdcs.ACLABS) couldn't
be
resolved, the server name (aclabsw2ksrv1.ACLABS) resolved to
the IP
address (172.16.32.4) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... ACLABSW2KSRV1 failed test
Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ACLABSW2KSRV1
Skipping all tests, because server ACLABSW2KSRV1 is
not responding to directory service requests
Running enterprise tests on : ACLABS
Starting test: Intersite
......................... ACLABS passed test Intersite
Starting test: FsmoCheck
......................... ACLABS passed test FsmoCheck
---------------------------------------------------------------------------------------
Thanks in advance for ANY help in solving this. You may have noticed
I've been to the usual fixes on this and it ain't working.
Maybe somebody will notice this see something wrong, or just have that
magic bullet I'm looking for.
I am trying to AVOID doing DCPROMO here, badly.
Thanks again,
Jason