Active Directory Synch, DNS lookup failure

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I’m having problems with DNS. I found some similar problems in this discussion group but I’m not able to apply any of their solutions to my situation

In summary, it appears that we are having problems with active directory communications/synchronization because of a problem with DNS.

I’ve tried uninstalling and reinstalling DNS a number of times and followed all the troubleshooting tips I could find in Technet. I am postive that I have the site type defined as Active Directory integrated and enabled for dynamic updates

I have included background information and output from various utilities below

Any help would be greatly appreciated

BACKGROUND
… Working with 2000 Active directory, upgraded from 4.0 domain. Two servers in question: “ntsrv_1†and “max-dynamicsâ€
… Ntsrv_1 is not the system that the Active directory upgrade was performed on. That system has since been retired
… Domain is called “wicâ€. Which I realize now is not a good thing. I’d like to change it to “wic.whq†but it may be too late since AD has already been up for a long time and there are a lot of user accounts defined
… Symptom 1: Applications “may†be having problems with Sql server connectivity on the server “max-dynamicsâ€. This symptom is what started the reseach
… Symptom 2: Encountering errors in the event log related to Active Directory Synchronization and DNS (see below

OUTPUT FROM VARIOUS UTILITIES
The Directory Service folder is loaded with the message belo
Start of EVENT VIEWER output ---------------------
Source: NTDS KC
Category: Knowledge Consistenc
Event ID: 126

The attempt to establish a replication link with parameter

Partition: CN=Configuration,DC=WI
Source DSA DN: CN=NTDS Settings,CN=MAX-DYNAMICS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WI
Source DSA Address: 843b794e-155d-42f2-bad1-caa217f7a9e8._msdcs.WI
Inter-site Transport (if any):

failed with the following status

The DSA operation is unable to proceed because of a DNS lookup failure

The record data is the status code. This operation will be retried
End of Event Viewer output --------------------------

Start of output from IPCONFIG /ALL --------------------------------------
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ntsrv_
Primary DNS Suffix . . . . . . . : WI
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : WI

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter (10/100
Physical Address. . . . . . . . . : 00-B0-D0-79-F8-71
DHCP Enabled. . . . . . . . . . . : N
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.
End of output from IPconfig /all -----------------------------------------

Start of Output from NETDIAG /FIX -----------------------------------
Computer Name: NTSRV_
DNS Host Name: ntsrv_1.WI
System info : Windows 2000 Server (Build 2195
Processor : x86 Family 6 Model 8 Stepping 6, GenuineInte
List of installed hotfixes :
KB81969
KB82318
KB82355
KB82398
KB82410
KB82414
KB82414
KB82511
KB82623
KB82803
Q14722
Q81609

Netcard queries test . . . . . . . : Passe
Per interface results

Adapter : Local Area Connectio

Netcard queries test . . . : Passe

Host Name. . . . . . . . . : ntsrv_
IP Address . . . . . . . . : 192.168.1.
Subnet Mask. . . . . . . . : 255.255.255.
Default Gateway. . . . . . : 192.168.1.
Dns Servers. . . . . . . . : 192.168.1.

AutoConfiguration results. . . . . . : Passe

Default gateway test . . . : Passe

NetBT name test. . . . . . : Passe
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_{302CD726-E5BE-4ED0-995C-D65F7621996A}
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] The DNS host name 'ntsrv_1.WIC' valid only on Windows 2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME]
[WARNING] Cannot find a primary authoritative DNS server for the name
'ntsrv_1.WIC.'. [RCODE_SERVER_FAILURE]
The name 'ntsrv_1.WIC.' may not be registered in DNS.
[FATAL] Failed to fix: DC DNS entry WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.2e3f8d91-4ab6-4914-9a90-727161c0d74d.domains._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.WIC. re-registeration on DNS server '192.168.1.5' 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.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry 3333f326-3e15-4768-b2e8-1fa5694f44b9._msdcs.WIC. re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '192.168.1.5'.
[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_{302CD726-E5BE-4ED0-995C-D65F7621996A}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{302CD726-E5BE-4ED0-995C-D65F7621996A}
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 'MAX-Dynamics.WIC'.

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
End of output from NETDIAG /FIX ------------------------------------------------------
 
I'm pretty sure I fixed it. I noticed the posting about single level domain names and applied the registry fixes. It seemed to fix the problem.
 
In
Jody said:
I'm having problems with DNS. I found some similar problems in this
discussion group but I'm not able to apply any of their solutions to
my situation.

In summary, it appears that we are having problems with active
directory communications/synchronization because of a problem with
DNS.

I've tried uninstalling and reinstalling DNS a number of times and
followed all the troubleshooting tips I could find in Technet. I am
postive that I have the site type defined as Active Directory
integrated and enabled for dynamic updates.

I have included background information and output from various
utilities below.

Any help would be greatly appreciated.

BACKGROUND:
. Working with 2000 Active directory, upgraded from 4.0 domain. Two
servers in question: "ntsrv_1" and "max-dynamics".
. Ntsrv_1 is not the system that the Active directory upgrade was
performed on. That system has since been retired.
. Domain is called "wic". Which I realize now is not a good thing.
I'd like to change it to "wic.whq" but it may be too late since AD
has already been up for a long time and there are a lot of user
accounts defined.
. Symptom 1: Applications "may" be having problems with Sql server
connectivity on the server "max-dynamics". This symptom is what
started the reseach.
. Symptom 2: Encountering errors in the event log related to Active
Directory Synchronization and DNS (see below)

OUTPUT FROM VARIOUS UTILITIES:
The Directory Service folder is loaded with the message below
Start of EVENT VIEWER output ----------------------
Source: NTDS KCC
Category: Knowledge Consistency
Event ID: 1265

The attempt to establish a replication link with parameters

Partition: CN=Configuration,DC=WIC
Source DSA DN: CN=NTDS
Settings,CN=MAX-DYNAMICS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=C
onfiguration,DC=WIC
Source DSA Address: 843b794e-155d-42f2-bad1-caa217f7a9e8._msdcs.WIC
Inter-site Transport (if any):

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup
failure.

The record data is the status code. This operation will be retried.
End of Event Viewer output ---------------------------

Start of output from IPCONFIG /ALL
---------------------------------------
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ntsrv_1
Primary DNS Suffix . . . . . . . : WIC
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : WIC

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-B0-D0-79-F8-71
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.5
End of output from IPconfig /all
------------------------------------------

Start of Output from NETDIAG /FIX ------------------------------------
Computer Name: NTSRV_1
DNS Host Name: ntsrv_1.WIC
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel
List of installed hotfixes :
KB819696
KB823182
KB823559
KB823980
KB824105
KB824141
KB824146
KB825119
KB826232
KB828035
Q147222
Q816093


Netcard queries test . . . . . . . : Passed
Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : ntsrv_1
IP Address . . . . . . . . : 192.168.1.5
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.5

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_{302CD726-E5BE-4ED0-995C-D65F7621996A}
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] The DNS host name 'ntsrv_1.WIC' valid only on Windows
2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME] [WARNING] Cannot
find a primary authoritative DNS server for the name
'ntsrv_1.WIC.'. [RCODE_SERVER_FAILURE] The name
'ntsrv_1.WIC.' may not be registered in DNS. [FATAL] Failed to
fix: DC DNS entry WIC. re-registeration on DNS server '192.168.1.5'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.2e3f8d91-4ab6-4914-9a90-727161c0d74d.domains._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._sites.WIC. re-registeration on
DNS server '192.168.1.5' 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.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.Default-First-Site-Name._sites.WIC. re-registeration
on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.WIC.
re-registeration on DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
_gc._tcp.Default-First-Site-Name._sites.WIC. re-registeration on DNS
server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
3333f326-3e15-4768-b2e8-1fa5694f44b9._msdcs.WIC. re-registeration on
DNS server '192.168.1.5' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS
entries for this DC on DNS server '192.168.1.5'. [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_{302CD726-E5BE-4ED0-995C-D65F7621996A}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{302CD726-E5BE-4ED0-995C-D65F7621996A}
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
'MAX-Dynamics.WIC'.

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
End of output from NETDIAG /FIX
------------------------------------------------------
Click to expand...

Thanks for posting all this info. Sometimes we have to pull teeth to get
this sort of stuff!

All these errors point to SRV data doesn't exist or is not getting updated
and you probably have SP4 installed. SP4 stopped DNS registration of single
label names since the DNS server doesn't know what to do with them (DNS is
hierarchal based, single labe names have not hierarchy), so therefore it
excessively quieries the ISC Root servers on the Internet. So you can see
why it was stopped.

As for keeping with the current name, see this article about single label
domain names and forcing it to work (but it's actually recommended to change
the name):
http://support.microsoft.com/?id=300684

As for your domain name, yes, "WIC" is in the wrong format. To get it
changed to "wic.whq" depends on your current Domain Mode.
1. If still in Mixed Mode, you can install an NT4 BDC into the domain, then
pull out the W2k DC from the network just leaving the NT4 BDC. Then you can
either demote the W2k machine or reinstall it as a fresh installation. If
Exchange is installed on this W2k box, then I would suggest to demote it
properly so as to not harm the Echange installation.Then promote the NT4 BDC
to a PDC, then run the upgrade on it this time choosing the correct
"wic.whq" AD DNS domain name. You can still keep WIC as the NetBIOS legacy
name. Then promote the W2k box as an additional DC in the domain. This will
insure you don't lose your user or domain accounts.

More info here...
292541 - How to Rename the DNS name of a Windows 2000 Domain [As long as the
domain is in mixed mode]:
http://support.microsoft.com/?id=292541


2. If in Native mode, this becomes a bit more complicated. In this case,
it's suggested to install another fresh pristine AD domain with the correct
name of "wic.whq". Then you can use the ADMT tool to migrate the users,
groups and computer accounts. You can also keep the users current profiles
as well with this tool. If Exchange is running, then you would need to go a
step further and use the Exmerge utility to migrate the mailboxes over.

Download details Active Directory Migration Tool v.2.0:
http://microsoft.com/downloads/deta...b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

260871 - HOW TO Set Up ADMT for Windows NT 4.0 to Windows 2000 Migration:
http://support.microsoft.com/?id=260871

Domain Migration Cookbook - Index and Cover:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.mspx

328871 - HOW TO Use the Exchange Migration Wizard to Migrate Mailboxes From
an Exchange Organization:
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871




--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jody said:
I'm pretty sure I fixed it. I noticed the posting about single level
domain names and applied the registry fixes. It seemed to fix the
problem.
Click to expand...

In addition, I can across this article in a search last night, MSDNS canot
resolve single label names.
What this means is that group policies cannot be applied because group
policies are found in the domain DFS share under the domain name in your
scenario-> \\WIC\SYSVOL\WIC\policies If you cannot connect to this share
using the domain name could you try this reg entry in the article below to
see if this resolves the issue? (This is a known issue to which we don't
have a verified fix yet)
251384 - Delays in Name Resolution Using Microsoft DNS Server Forwarder
Option
http://support.microsoft.com/default.aspx?scid=kb;en-us;251384
 
Back
Top