UNC access failure: Logon Failure: The target account name is incorrect

  • Thread starter Thread starter antonyliu2002
  • Start date Start date
A

antonyliu2002

Hi,

We can access the file server in our office through its ip address, but
we cannot access it through UNC like \\oakfileserver.

The error message says:

[snip]
Logon Failure: The target account name is incorrect

The system log shows:

<sys_log>
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11166
Date: 9/13/2005
Time: 11:18:03 AM
User: N/A
Computer: OAKFILESERVER
Description:
The system failed to register host (A) resource records (RRs) for
network adapter with settings:

Adapter Name : {22A28368-6B95-47F7-86C6-70AD401F9E5D}
Host Name : oakfileserver
Primary Domain Suffix : some.domain.name.com
DNS server list :
1.2.3.4, 1.2.3.5
Sent update to server : 1.2.3.6
IP Address(es) :
2.3.4.5

The reason the system could not register these RRs was because of a
security related problem. The cause of this could be (a) your computer
does not have permissions to register and update the specific DNS
domain name set for this adapter, or (b) there might have been a
problem negotiating valid credentials with the DNS server during the
processing of the update request.

You can manually retry DNS registration of the network adapter and its
settings by typing "ipconfig /registerdns" at the command prompt. If
problems still persist, contact your DNS server or network systems
administrator. For specific error code, see the record data displayed
below.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data: 0000: 38 23 00 00 8#..
</sys_log>

We have tried "ipconfig /registerdns", but it did not help.

Would any guru please kindly advise us? Thanks a lot!
 
Hi,

We can access the file server in our office through its ip address,
but we cannot access it through UNC like \\oakfileserver.

The error message says:

[snip]
Logon Failure: The target account name is incorrect

The system log shows:

<sys_log>
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11166
Date: 9/13/2005
Time: 11:18:03 AM
User: N/A
Computer: OAKFILESERVER
Description:
The system failed to register host (A) resource records (RRs) for
network adapter with settings:

Adapter Name : {22A28368-6B95-47F7-86C6-70AD401F9E5D}
Host Name : oakfileserver
Primary Domain Suffix : some.domain.name.com
DNS server list :
1.2.3.4, 1.2.3.5
Sent update to server : 1.2.3.6
IP Address(es) :
2.3.4.5
Click to expand...

I first need to understand the relationship of all these DNS servers. Is
Active Directory involved?
what are the two DNS servers 1.2.3.4 and 1.2.3.5 and what is the DNS server
1.2.3.6?

This error message would lead me to believe the 1.2.3.6 is the Primary
nameserver for some.domain.name.com, because that is where the update is
sent, and that DNS server does not or cannot accept dynamic updates from
this machine.
 
So how do force DNS to accept dynamic updates from this machine? I get the
same error. 1.2.3.6 is the server that is throwing this error. Active
Directory involved.

Kevin D. Goodknecht Sr. said:
Hi,

We can access the file server in our office through its ip address,
but we cannot access it through UNC like \\oakfileserver.

The error message says:

[snip]
Logon Failure: The target account name is incorrect

The system log shows:

<sys_log>
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11166
Date: 9/13/2005
Time: 11:18:03 AM
User: N/A
Computer: OAKFILESERVER
Description:
The system failed to register host (A) resource records (RRs) for
network adapter with settings:

Adapter Name : {22A28368-6B95-47F7-86C6-70AD401F9E5D}
Host Name : oakfileserver
Primary Domain Suffix : some.domain.name.com
DNS server list :
1.2.3.4, 1.2.3.5
Sent update to server : 1.2.3.6
IP Address(es) :
2.3.4.5
Click to expand...

I first need to understand the relationship of all these DNS servers. Is
Active Directory involved?
what are the two DNS servers 1.2.3.4 and 1.2.3.5 and what is the DNS server
1.2.3.6?

This error message would lead me to believe the 1.2.3.6 is the Primary
nameserver for some.domain.name.com, because that is where the update is
sent, and that DNS server does not or cannot accept dynamic updates from
this machine.
Click to expand...
 
In
japson said:
So how do force DNS to accept dynamic updates from this machine? I
get the same error. 1.2.3.6 is the server that is throwing this
error. Active Directory involved.
Click to expand...

I believe what Kevin is asking is if 1.2.3.6 is one of your DNS servers or
is it an outside (ISP) server or is it the server hosting a Primary zone for
some.domain.name.com and the others are secondaries, etc.

If it is one of your own DNS servers, is it a domain controller?

Are all the servers you listed, 1.2.3.4 and 1.2.3.5 also domain
controllers/DNS servers? If so, is the zone AD Integrated or are you using
Primary/Secondary zones?

Normally this error pops up if using an ISP's DNS in a machine's (DC
included) IP configuration. It can be simply based on not allowing updates
on the zone properties if it is one of your servers.

There are a number of other factors that dictate dynamic registration on a
DC and client as well, simply such as:

1. The Primary DNS Suffix must match the AD DNS domain name, i
2. I can't be a single label name,
3. The DNS servers listed in the IP config must be authorative for the zone
or has a way to get to it (such as the MNAME in a secondary zone)
4. Updates are allowed in the Primary or the AD Integrated zone properties.

It would be highly helpful to know more about your specific configuration
and topology to better and accurately assist you.


As far as the other issue, the UNC issue, (not related to DNS), UNC access
based on \\computername is NetBIOS based, unless the record is in DNS and it
is devolving to that record. The UNC error you described is common when
NetBios is resolution is misconfigured or not propery supported. If there
are multiple entries for the same NeBIOS name, that can cause it as well. If
you have multiple subnets, WINS is the answer for NetBIOS name resolution
support.

To resolve whether NetBIOS registration (nothing to dowith DNS registration)
is functioning, open a CMD prompt, and type in from both machines (the
server you're trying to access, and the machine you're doing this from):
nbtstat -n

You should see the NetBIOS name of each machine, and the NetBIOS name of the
domain it is part of. If you don't see at least the machine name, and the
netbios domainname, (not the AD DNS domain name), there is a NetBIOS issues.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Microsot Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
1.2.3.6 is not a DNS server, it just happens to be a server on my local
network. 1.2.3.4 is primary DC\DNS and 1.2.3.5 is secondary DC\DNS.

What brought this on:
I added a new server to my domain and assigned a static IP to replace an old
server. But first, I removed the old references in DNS and AD to the old
server before adding the new server to my domain. Then these DNSApi errors
started. I could not ping the computer name but I could ping the new static
IP. I had to go into DNS and add the computer name so I could connect and
ping the computer name.

Everything appears to work fine, I would just like to stop this error. Thanks
 
In
japson said:
1.2.3.6 is not a DNS server, it just happens to be a server on my
local network. 1.2.3.4 is primary DC\DNS and 1.2.3.5 is secondary
DC\DNS.

What brought this on:
I added a new server to my domain and assigned a static IP to replace
an old server. But first, I removed the old references in DNS and AD
to the old server before adding the new server to my domain. Then
these DNSApi errors started. I could not ping the computer name but I
could ping the new static IP. I had to go into DNS and add the
computer name so I could connect and ping the computer name.

Everything appears to work fine, I would just like to stop this
error. Thanks
Click to expand...

We'll try to help stop it, but at this point we're now guessing without
specifics about your infrastructure and just offering possibilities.

Are you using WINS? If so, did you check in WINS if the older IP is in
there? As I mentioned, NetBIOS errors can cause this as well, which point
back to WINS, if using it.

Are all machines only using the internal DNS (no ISP DNS server) in their IP
properties?

If you have to *manually* enter the static IP in DNS, then that tells me
there's an obvious DNS misconfiguration somewhere that is preventing
registration. Once again, here are the pre-requisites to ensure DNS dynamic
registration. Check each point and post back if you have any questions about
them. I adjusted #3. .

1. The Primary DNS Suffix must match the AD DNS domain name, ipconfig /all
will show you that.

2. It can't be a single label name

3. The DNS servers listed in the IP config must be authorative for the zone.
This means that all AD machines (DCs, clients and member servers), must ONLY
use the internal DNS server(s) that host the AD DNS domain zone or your DNS
server has a way to send the query to it (thru Secondaries, delegation,
stubs, etc)

or has a way to get to it (such as the MNAME in a secondary zone)

4. Updates are allowed in the Primary or the AD Integrated zone properties.

If you like, what would really help us to get closer to a diagnosis is if we
can see an ipconfig /all of one of your DCs and of the machine in question.


Ace
 
Not using WINS. No ISP DNS servers.

With ipconfig /all, no Connection-specific DNS Suffix is given. So I had to
manually add the DNS suffix. It was set to Append primary and connection
specific DNS suffixes and Append parent suffixes of the primary DNS suffixes
as are all my servers.

But when running ipconfig /registerdns, I still get the same error.

Thanks
 
In
japson said:
Not using WINS. No ISP DNS servers.

With ipconfig /all, no Connection-specific DNS Suffix is given. So I
had to manually add the DNS suffix. It was set to Append primary and
connection specific DNS suffixes and Append parent suffixes of the
primary DNS suffixes as are all my servers.

But when running ipconfig /registerdns, I still get the same error.

Thanks
Click to expand...

That doesn't make sense if AD is involved. Once you join a machine to the
domain, it automatically (unless the checkbox is unchecked) takes on the
domain's Primary DNS Suffix which will also be your Connection Suffix and
Search Suffix.

Go into Network ID in System Properties and check the box if this machine is
already joined. If not joined, and you don't want it to, then of course
manually enter it.

Ace
 
When this first happened, I updated the NIC drivers, swapped ports to which
the ethernet cable was connected, deleted any references in DNS and AD and
swapped between being in a Workgroup and joining my domain 3 times.

I've since added other machines to my network without any problems.
 
In
japson said:
When this first happened, I updated the NIC drivers, swapped ports to
which the ethernet cable was connected, deleted any references in DNS
and AD and swapped between being in a Workgroup and joining my domain
3 times.

I've since added other machines to my network without any problems.
Click to expand...

I see. Has rejoining rectified the problem and automatically configured the
suffix?

Ace
 
japson said:
When this first happened, I updated the NIC drivers, swapped ports to
which the ethernet cable was connected, deleted any references in DNS
and AD and swapped between being in a Workgroup and joining my domain
3 times.

I've since added other machines to my network without any problems.
Click to expand...

A netdiag /v should tell us why it is sending updates to the wrong server.
 
In
Kevin D. Goodknecht Sr. said:
A netdiag /v should tell us why it is sending updates to the wrong
server.
Click to expand...

That and the ipconfig /all. But japson hasn't provided one when I asked. I
don't think we'll get the netdiag.

Ace
 
Windows IP Configuration

Host Name . . . . . . . . . . . . : IBMx335-1
Primary Dns Suffix . . . . . . . : domain.mycompany.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.mycompany.com
mycompany.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.mycompany.com
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0D-60-1C-87-B6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 1.2.3.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 1.2.3.1
DNS Servers . . . . . . . . . . . : 1.2.3.4
1.2.3.5

Everything appears correct with the IP config. But as I stated before,
nothing was in Connection-specific DNS Suffix: until I added it locally in
the IP settings.

I'll look for netdiag.exe soon.
 
In
japson said:
The netdiag log is pretty large, should I post it here or email it to
you?

Thanks
Click to expand...

Email it if you like, and keep it *unedited* please. You can email both
Kevin and I if you like. My email is as it is stated,
(e-mail address removed). I don't want to write it out here due to
webbots grabbing emails for spammers.

Ac
 
Back
Top