최고의 답변자
Logon Unsuccessful: The user name you typed is the same as the user name you logged in with

질문
-
Windows 2003 domain. I get the following message when using a user with domain admin permissions:
"Logon Unsuccessful: The user name you typed is the same as the user name you logged in with. That user name has already been tried. A domain controller cannot be found to verify that user name."
other domain admin level users have no issues (yet?)
when I try to connect to the same services from same PCs or servers using a different administrator, it is working - I take it as something faulty with the user, not with network connectivity or local PCs
this is coming and going without any noticeable reason
http://ITDualism.wordpress.com2010년 4월 30일 금요일 오후 1:34
답변
-
Consider using the Account Lockout and Troubleshooting tools.
I have info on troubleshooting lockouts, which may be related at:
http://www.pbbergs.com/windows/articles/UserAccountLockoutTroubleshooting.html
--
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.comPlease no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.- 답변으로 표시됨 Bruce-Liu 2010년 5월 21일 금요일 오전 5:37
2010년 5월 11일 화요일 오후 12:24
모든 응답
-
this happen on any domain machine, PCs and servers. it is also a problem on out of domain machines trying to access domain resources using this username's credentials.
is there a limit to the number of concurrent uses of a single username? (I do work like this for years and never had a problem but worth checking)
I repeat one main behavioral issue: this is working\not working randomly for X period of time. I'm doing nothing and it is working then after whatever time it stops. that is why I think it might have some limit issues that idle times solve
http://ITDualism.wordpress.com2010년 4월 30일 금요일 오후 2:58 -
Hello,
if Marcins suggestion, also described here http://support.microsoft.com/kb/306992/en-us, doesn't help, please post an unedited ipconfig /all from the problem workstation and your DC/DNS server so we can exclude DNS as a problem.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.2010년 5월 3일 월요일 오전 8:46 -
Consider using the Account Lockout and Troubleshooting tools.
I have info on troubleshooting lockouts, which may be related at:
http://www.pbbergs.com/windows/articles/UserAccountLockoutTroubleshooting.html
--
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.comPlease no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.- 답변으로 표시됨 Bruce-Liu 2010년 5월 21일 금요일 오전 5:37
2010년 5월 11일 화요일 오후 12:24 -
10 year later and the problem still persist. Current workaround is to try to log in with a user on a different but valid domain. Which will fail as users from the 2nd domain don't have access. But if I then try again with correct domain it works.
Which leads me to believe that remembering that the last login attempt failed is just wrong on a fundamental design level. Just because something failed before doesn't mean it will fail again.
This error message should not exist or there should be at least "retry anyway option".
2020년 4월 3일 금요일 오전 7:37