Re: UNC access failure: Logon Failure: The target account name is
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Thu, 22 Sep 2005 22:47:56 -0400
In news:F0B8FFAE-6F4D-4A0E-A57D-6327E9100204@xxxxxxxxxxxxx,
japson <japson@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
commented about below:
> 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
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
.
- Follow-Ups:
- References:
- UNC access failure: Logon Failure: The target account name is incorrect
- From: antonyliu2002
- Re: UNC access failure: Logon Failure: The target account name is incorrect
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: UNC access failure: Logon Failure: The target account name is
- From: japson
- Re: UNC access failure: Logon Failure: The target account name is
- From: Ace Fekay [MVP]
- Re: UNC access failure: Logon Failure: The target account name is
- From: japson
- UNC access failure: Logon Failure: The target account name is incorrect
- Prev by Date: Re: UNC access failure: Logon Failure: The target account name is
- Next by Date: Re: UNC access failure: Logon Failure: The target account name is
- Previous by thread: Re: UNC access failure: Logon Failure: The target account name is
- Next by thread: Re: UNC access failure: Logon Failure: The target account name is
- Index(es):
Relevant Pages
|