General discussion

Locked

Login Failure: target name is incorrect

By Hawkeye_11105 ·
I have two Win2K domain controllers. The first one was upgraded from a Win NT 4 domain. The second was added to the domain later.
When I try to access the first server from any client or from the second server by using the machine name (i.e. \\firstserver) I get the error message "Login Failure: target name is incorrect".

If I try to map drives by IP or by FQDN (\\firstserver.mycompany.org) I am successful.
I have no problem with accessing the second server from either the client or fromthe first server.

One thing that I noticed that was not done correctly: when we upgraded the first server we never changed the domain name connected to the NIC. So the machine name was firstserver.mycompany-ny.org. I followed the registry hackin Microsoft Article #: Q257623 but I still am unable to access the firstserver correctly.
This was the first server in the domain. I tried running DC Promo to demote the server to a standalone and fix the problem but I am unable to succesfully run DC Promo.

Thanks

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Login Failure: target name is incorrect

by m_pact In reply to Login Failure: target nam ...

Have you tried to use the dcdiag.exe that comes with the windows 200 resource kit. that at least pointed me in the right direction with my dc's.

Collapse -

Login Failure: target name is incorrect

by Hawkeye_11105 In reply to Login Failure: target nam ...

Poster rated this answer

Collapse -

Login Failure: target name is incorrect

by Hawkeye_11105 In reply to Login Failure: target nam ...

I noticed that if I go into the Domain Controllers section of the Active Directory Groups & Users snap-in on both machines that the DNS name for FirstServer is different.
On FirstServer, the DNS name is FirstServer.MyCompany.Org.
On SecondServer,the DNS name is listed as FirstServer.MyCompany-NY.org
This, obviously, would seem to be the source of my problem but I have no way to change the DNS name and I still cannot demote the server so I can re-promote it.
I'm trying to move files off ofFirstServer but I'm afraid to just take it out of the system (to rebuild if needed) because it still has the FSMO roles

Collapse -

Login Failure: target name is incorrect

by timwalsh In reply to Login Failure: target nam ...

Run dcdiag (as suggested in answer one) from both DCs and see how the results match. Win2K will not let you run dcpromo on a computer that still has FSMO roles assigned. You will need to transfer FSMO roles to the second DC (assuming it is otherwise healthy).

You can transfer roles in one of two ways: graceful transfer (using the AD computers and users snap-in from the secondary DC), or through seizure (by removingthe first DC from the network and then using ntdsutil in Directory ServicesRestore mode on the secondary DC). If you can successfully use the graceful method, you should then be able to run dcpromo to get things straight again. If you have to use the seizure method, it will be a waste of time trying to run dcpromo (in fact it still won't work because the DC will still think it has the FSMO roles assigned). Just wipe the drive and install from scratch (it hopefully goes without saying to back up any important data on BOTH DCs before you attempt any of this).

Hopethis helps.

Collapse -

Login Failure: target name is incorrect

by Hawkeye_11105 In reply to Login Failure: target nam ...

Well I ended off having to use the seizure method and re-installing the C: partition.
I was hoping to avoid that but I guess if we would have taken some more time and installed it right the first time then I woulnd't have had the problem.

Thanks

Collapse -

Login Failure: target name is incorrect

by Hawkeye_11105 In reply to Login Failure: target nam ...

This question was closed by the author

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums