locked
Logon Unsuccessful: The user name you typed is the same as the user name you logged in with RRS feed

  • Question

  • 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.com
    Friday, April 30, 2010 1:34 PM

Answers

All replies

  • Check whether you have any entries in the Stored User Names and Passwords (Control Panel\User Acconts\Advanced) - if so, remove them and try again...

    hth
    Marcin

    • Marked as answer by Bruce-Liu Friday, May 21, 2010 5:37 AM
    Friday, April 30, 2010 1:40 PM
  • 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.com
    Friday, April 30, 2010 2:58 PM
  • Any DNS issues in the Domain?
    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, April 30, 2010 7:14 PM
  • 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.
    Monday, May 3, 2010 8:46 AM
  • no, DNS is working well
    http://ITDualism.wordpress.com
    Monday, May 3, 2010 2:01 PM
  • I experienced the same problem.

    It occured when the same username was logged on at two different computer at the same time, and I tried to log on at a third one.


    A Fabis Abstinentes -Pythagoras of Samos
    Tuesday, May 11, 2010 11:18 AM
  • Consider using the Account Lockout and Troubleshooting tools.

    http://www.microsoft.com/downloads/details.aspx?FamilyID=7af2e69c-91f3-4e63-8629-b999adde0b9e&displaylang=en

    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.com

    Please no e-mails, any questions should be posted in the NewsGroup This
    posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Bruce-Liu Friday, May 21, 2010 5:37 AM
    Tuesday, May 11, 2010 12:24 PM
  • Check whether you have any entries in the Stored User Names and Passwords (Control Panel\User Acconts\Advanced) - if so, remove them and try again...

    I can't find and "Advanced"button on the User Accounts page.
    Friday, April 3, 2020 7:24 AM
  • Consider using the Account Lockout and Troubleshooting tools.

    "404 - File or directory not found."
    Friday, April 3, 2020 7:27 AM
  • 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".

    Friday, April 3, 2020 7:37 AM