Resolution and Aliasing

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

Guest

Receiving "Logon Failure: The target account name is incorrect", and here's
the situation-
Took an old (W2K) host name and added it in DNS as an alias for an existing
W2K3 (cluster) server. NSLookup seems to resolve correctly, but attempting
to browse to the old host name from an XP or W2K3 system produces the error I
mentioned. The strange thing is that W2K clients can browse to the old host
name. There's an MS article related to the error message but it seems to
pertain to promoting domain controllers. I'm wondering if it does pertain to
something related to our Active Directory or DNS. The old host is still
online, but has been renamed.
 
In
dslinkard said:
Receiving "Logon Failure: The target account name is incorrect", and
here's the situation-
Took an old (W2K) host name and added it in DNS as an alias for an
existing W2K3 (cluster) server. NSLookup seems to resolve correctly,
but attempting to browse to the old host name from an XP or W2K3
system produces the error I mentioned. The strange thing is that W2K
clients can browse to the old host name. There's an MS article
related to the error message but it seems to pertain to promoting
domain controllers. I'm wondering if it does pertain to something
related to our Active Directory or DNS. The old host is still
online, but has been renamed.
Click to expand...

What article are you referring to? Is it this?
http://support.microsoft.com/default.aspx?scid=kb;en-us;296993


Did you point that alias as a name to the virtual IP or to an individual
node in the cluster?

When your clients 'browse' to the old name (thru Network Neighborhood?), is
it connecting to the cluster virtual IP or the node in the cluster? What IP
does is the name in WINS have? Is it the same as the IP in DNS?

Was the previous name you are using a previous DC name that was demoted
unsuccessfully ? (AD will retain the name unless properly demoted or a
Metadata cleanup is performed on the database to manually remove the name).

It can also be a simple SMB signing issue that is known to be an issue with
communication between W2k3 and XP to older clients. Read this (the title is
deceiving):

555038 - How to enable Windows 98-ME-NT clients to logon to Windows 2003
based Domains:
http://support.microsoft.com/?id=555038


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Is there keerberos erros in the Event logs? If so add the both "Host" SPN's
to the new server.....

Scott
"Ace Fekay [MVP]"
 
In
news.microsoft.com said:
Is there keerberos erros in the Event logs? If so add the both
"Host" SPN's to the new server.....

Scott
Click to expand...

Scott, if you are referring to 40961 errors (SPNEGO), then a reverse zone is
required to eliminate that error.

Ace
 
Back
Top