Error 2221 Net Use
Contents |
very strange, with "System Error 2221 has occurred" message. This probably is a stored credential problem. SOLUTION: Press your Windows' Start / Launch, in "Search system error 2221 has occurred. the username could not be found programs and files" field type "Credential Manager" and you should see it shows
Net Use Erreur 2221
up on the list. Run it. Check the stored credentials and remove related credentials, by click on the "Remove
Windows System Error 2221
from vault". Now, try your NET USE command to map drives again. Posted by Jacky Tse at Monday, October 08, 2012 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Troubleshooting 29
The Username Could Not Be Found Network Share
comments: AnonymousOctober 17, 2012 at 9:49 PMI was getting the same problem, drive mappings were not working.I deleted the entry in Credential Manager and rebooted, worked like a dreamReplyDeleteAnonymousFebruary 18, 2013 at 7:57 AMjust found this answer through various searches, and you have just solved a problem i have had for 2 days. Thank You so muchReplyDeleteAnonymousMarch 28, 2013 at 11:18 AMGood work Jack.My situation net user user not found 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.ReplyDeleteAnonymousJuly 10, 2013 at 2:43 AMHelped me today. Thanks. Trevor.ReplyDeleteAnonymousJuly 26, 2013 at 3:13 AMHello 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.ReplyDeleteAnonymousAugust 13, 2013 at 5:22 AMTHAT'S THE FACT JACK! Thank you sir! This helped me too. ReplyDeleteAnonymousSeptember 16, 2013 at 5:15 PMThanks man, that did the trickReplyDeleteEldeeSeptember 23, 2013 at 7:18 PMThanks a lot, that helps a lot on VPN / credential issuesReplyDeleteAnonymousOctober 28, 2013 at 3:18 PMThank you!ReplyDeleteCRM-9December
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: VPN net user username cannot be found - net use error 2221 Windows 7 IT Pro > the username could not be found command prompt Windows 7 Networking Question 0 Sign in to vote Hello, we are migrating to Windows net user helpmsg 2221 7 and have some VPN Users. Now we are testing the VPN Scenario in Windows 7. We have recognized that, we cant connect network drives, http://techat-jack.blogspot.com/2012/10/solved-system-error-2221-has-occurred.html when we are connected through VPN. We get: system error 2221 the username could not be found I have done some testing and figure out: - ping ip works - ping servername works - ping domainname works So I assume its not an Name resoultion issue. If I map the https://social.technet.microsoft.com/Forums/office/en-US/bb139932-9b7f-47a1-b116-fc8ac105d8f4/vpn-net-use-error-2221?forum=w7itpronetworking Networkdrive with "\\server\sharename" I get immediately error 2221 as mentioned above, but if I try to map \\IP\sharename" I get asked for username and password. May somebody have a clue? My other question is, if we possibly could map drive via "\\IP\sharename", how we could automate this, that the user dont must enter credentials. This has been working with Windows XP with no issues. Thanks Friday, July 25, 2014 2:06 PM Reply | Quote Answers 2 Sign in to vote Sometimes the issue has to deal with the stored credentials on your machine. Open Control Panel and navigate to Credential Manager then remove the credentials relating to VPN/network drives. Restart your computer, it will ask you for your credentials the first time. See if it asks again.Don't forget to mark the post that solved your issue as "Answered." By marking the Answer you are enabling users with similar issues
a System error 2221. The user name could not be http://microsoft.public.windows.server.dns.narkive.com/XnvF3MpG/system-2221-error-mapping-drive found.But if I do the same thing with an https://community.spiceworks.com/topic/844191-windows-7-startup-error IP address, such as:Net Use Q: \\192.168.52.11\ShareNameIt is successfull.If I Ping Nt4SrvName it resolves to the correct I/P Address.What is going on here? Heinz 2005-04-04 17:49:01 UTC PermalinkRaw Message I should add that the net use NT-Server is not in the 2003 domain, but DNS containsboth Forward and Reverse Lookup records for the server as below:Forward Lookup Zonesophl.caNT4SRVNAME Host(A) 192.168.52.11Reverse Lookup Zones192.168.52.x Subnet192.168.52.11 OPSWPGNT1.ophl.ca.192.168.52.11 opswpgnt1.Is there something wrong here? Kevin D. Goodknecht Sr. [MVP] 2005-04-05 16:02:37 UTC PermalinkRaw Message not be found Post by HeinzNet Use Q: \\Nt4SrvName\ShareNameI get a System error 2221. The user name could not befound.Net Use Q: \\192.168.52.11\ShareNameIt is successfull.If I Ping Nt4SrvName it resolves to the correct I/PAddress.What is going on here?Does the mapping work if you use FQDN in the mapping\\OPSWPGNT1.ophl.ca\sharename ?--Best regards,Kevin D4 Dad Goodknecht Sr. [MVP]Hope This Helps===================================When responding to posts, please "Reply to Group"via your newsreader so that others may learn andbenefit from your issue, to respond directly tome remove the nospam. from my email address.===================================http://www.lonestaramerica.com/===================================Use Outlook Express?... Get OE_Quotefix:It will strip signature out and morehttp://home.in.tum.de/~jain/software/oe-quotefix/===================================Keep a back up of your OE settings and folderswith OEBackup:http://www.oehelp.com/OEBackup/Default.aspx=================================== Heinz 2005-04-05 17:13:01 UTC PermalinkRaw Message Post by Kevin D. Goodknecht Sr. [MVP]Does the mapping work if you use FQDN in the mapping\\OPSWPGNT1.ophl.ca\sharename ?No,
a user logs into his computer on the domain he receives this message in the control panel. Also the mapped drives that are scripted to connect at logon do not connect. I log in to the same computer with my credentials and all is fine. Everything connects as it should. The error message that show in the command prompt is below. Any help is appreciated. BTW I was so thankful for the help on my last post. I could not stop raving, to anyone that would listen, about the amazing response of the Spiceheads! The network connection could not be found. More help is available by typng NET HELPMSG 2250 The network connection could not be found. More help is available by typng NET HELPMSG 2250 System error 53 has occurred. The network path was not found. System error 85 has occurred. The local device name is already in use. System error 2221 has occurred. The user name could not be found. Reply Subscribe RELATED TOPICS: Windows 7 Error 2149842967 Windows 7 0xc0000005 error Need help on com surrogate has stopped working windows 7   5 Replies Jalapeno OP John910327 Mar 16, 2015 at 7:43 UTC What is likely happening is you are not connected to the domain network. When Windows loads a profile for the first time, it pulls info for that user, including mapped drives and it will store the current local password. If you connect to the local network domain through an Ethernet cable, have the user log in. I'm willing to bet it will pull that users credentials without issue. Then it will not have to be on the network to log in again. It's just when ever you log in, for the first time, on a computer that is registered on a domain, you need to be connected to the domain so any new users profile can get downloaded from the system. 0 Jalapeno OP John910327 Mar 16, 2015 at 7:49 UTC Also, if he is connected to the domain, you can try resetting his tcp/ip settings... sometimes those settings can be broken between user accounts. so one account works fine, another not so much cmd (admin rights) netsh int ip resetalso do:ipconfig /flushdns i