Highlights

Monday, October 8, 2012

SOLVED! - System Error 2221 has occurred

For some reason, a user suddenly cannot use the "NET USE" command to map network drives. Windows logon is working, but accessing network shares become very strange, with "System Error 2221 has occurred" message. This probably is a stored credential problem.

SOLUTION: Press your Windows' Start / Launch, in "Search programs and files" field type "Credential Manager" and you should see it shows up on the list. Run it.

Check the stored credentials and remove related credentials, by click on the "Remove from vault". Now, try your NET USE command to map drives again.

33 comments:

  1. I was getting the same problem, drive mappings were not working.
    I deleted the entry in Credential Manager and rebooted, worked like a dream

    ReplyDelete
  2. just found this answer through various searches, and you have just solved a problem i have had for 2 days. Thank You so much

    ReplyDelete
  3. Good work Jack.
    My situation is that all the people having this issue at my work are only getting it through the VPN. We have confirmed that a person would have to log off the VPN then clear the credentials required (and choose correctly from the myriad of listed items) then log back onto the VPN and clear the session credentials and go back through the VPN log off/on process again. We've confirmed it all a half a dozen times but still searching for that elusive permanent fix that removes the need for the laborious work-around of credential-clearing-log-on-off-on etc.
    Keep up the good work.
    Cheers,
    Grumpy Old IT Guy.

    ReplyDelete
  4. Helped me today. Thanks. Trevor.

    ReplyDelete
  5. Hello Jack. I work at a multinacional company, on Brazil's subsidiary. This post have just helped me a lot with an issue in Chile. Thanks! Gustavo, from Brazil.

    ReplyDelete
  6. THAT'S THE FACT JACK! Thank you sir! This helped me too.

    ReplyDelete
  7. Thanks man, that did the trick

    ReplyDelete
  8. Thanks a lot, that helps a lot on VPN / credential issues

    ReplyDelete
  9. Excellent! Thank you! This solved a Windows Server 2012 Essentials based domain for accessing a windows 8.1 drive. Excellent!

    ReplyDelete
  10. Amazing! Saved me hours of aggravation. Thanks

    ReplyDelete
  11. thx, saved my ass with that one :)

    ReplyDelete
  12. worked perfect thank you

    ReplyDelete
  13. Works!! Hot damn...Thank you!

    ReplyDelete
  14. thanks for the tip!! Appreciate it

    ReplyDelete
  15. Nice one....Thanks

    ReplyDelete
  16. Worked again, thanks!

    ReplyDelete
  17. Had an SVP encounter this issue today. People freaked out.. Thank you for allowing me to calmly save the day.. The solution expressed here works like a charm.

    May also correct an error showing in the GUI of "An extended error has occured".

    ReplyDelete
  18. I love you! This just saved me from a massive headache I was having for 2 days. Come to Jamaica and feel alright! DJ Archie.

    ReplyDelete
  19. Nice work! I'll try to remember credential manager next time. Very handy!

    ReplyDelete
  20. I encountered this today - a user logged onto her PC with a local account (which she was not supposed to do) and tried to run an application that connected to an application server which munged the credential for that member server. Following these instructions on her PC fixed it and I learned something new at the same time! (I've also removed the local profile. Bad user, Bad!)

    ReplyDelete
  21. Worked for me. A connection to our fileserver was using an incorrect username. I could only map the drive by IP address and not with FQDN

    ReplyDelete
  22. I've been trying to figure out a strange file share access issue for an hour now. Finally caught this error after testing with net use and found this page. Removed the bad credentials and things were instantly fixed. Thanks!

    ReplyDelete
  23. Worked for me, too
    Thanks a lot for posting solutions,
    Axel

    ReplyDelete
  24. I owe you a beer next time you visit Oslo :)

    ReplyDelete
  25. Worked for me!
    I was looking at TCP/IP settings and a dozen other things.
    Thanks for the help!!

    ReplyDelete
  26. Thaank you so much!! Worked like a charm.

    ReplyDelete
  27. thank you ,this was the reason !!

    ReplyDelete
  28. Would just like to add my appreciation as well - that did the trick. Will remember this one, very useful.

    ReplyDelete