Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Windows cannot access \\machine\sharedfolder, error code 0x80004005

Answered Windows cannot access \\machine\sharedfolder, error code 0x80004005

  • Saturday, April 24, 2010 8:01 AM
     
     
    Sign In to Vote
    1

    Hello,

    These days when I try to open a shared folder in other machines(including XP, Vista, 7, Server 2003/2008) from my own Windows 7 Ultimate pc, I get a Network Error dialog saying:
    Windows cannot access \\machine\sharedfolder, error code 0x80004005, unspecified error.

    It aslo failed with IP.  And I have disable the Firewall

    But the other XP, Vista, Server 2003 and Server 2008 machines can reach each other and they even can open the shared fodler from my Windows 7.

    It's too strange. Maybe you can give me some useful suggestion.

    Thanks.

    Xiaofeng

    问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net
     

All Replies

  • Monday, April 26, 2010 3:56 AM
    Moderator
     
     Proposed Answer
    Sign In to Vote
    0

    Hi,

     

    Try to disable IPv6 and restart your computer, please visit the following site for detailed steps:

     

    How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista, Windows 7 and Windows Server 2008

     

    Best Regards

    Dale

     
  • Monday, April 26, 2010 5:06 AM
     
     
    Sign In to Vote
    0

    Hi Dale

    Thanks for your response.

    Unfortunately, it's not fixed after disabling IP6. I take 0xffffffff as value of DisabledComponents to disable all the IP6 components.

    问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net
     
  • Monday, April 26, 2010 5:34 AM
    Answerer
     
     
    Sign In to Vote
    0

    Hi Dale

    Thanks for your response.

    Unfortunately, it's not fixed after disabling IP6. I take 0xffffffff as value of DisabledComponents to disable all the IP6 components.

    问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net


    Did you ensure file and folder sharing in xp and vista is enable and there's no third party firewall on this two rig? I suggest you to map using it's IP as well as host name of the xp and vista machine

    Use the following method if you're mapping through IP \\192.168.X.XXX or alternatively if through host name \\Wang=PC

    First of all you need to find out the exact IP or host name of the xp and vista rig before you could mapped it from the win 7 rig

     
  • Monday, April 26, 2010 6:08 PM
     
     
    Sign In to Vote
    0

    Hi Daniel

    I have disabled all the firewall for the test. Neither IP nor host name can be avaiable.

    As I said above,  only one Window 7 can not access shared resources from other machines(xp, vista, server 2003, server 2008), but  other machines can access  each other, they also can access shared resouces from the Windows 7. It seems this Windows 7 guy locks himself in the room but seeing others get in and go out. too strange.

    Thanks.

    问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net
     
  • Friday, April 30, 2010 2:57 AM
     
     Answered
    Sign In to Vote
    0

    In case this helps... I was having a similar problem on a new laptop (Toshiba) with Windows 7 Home Premium using wifi.  Accessing a share on an XP desktop "suddenly" stopped working.

    It appears the issue is related to the Microsoft Virtual WiFi Miniport Adapter, which was evidently installed with a driver update around the first week of April.  Even though the adapter is disabled, it appears that any changes that you make to the settings on your "normal" wireless adapter also need made on this one.  For me, this included enabling NetBIOS over TCP/IP (under IPv4 settings) and ensuring IPv6 was disabled.  Again, THE INTERFACE IS DISABLED, but these changes still "magically" made my sharing work immediately.

     
  • Thursday, July 29, 2010 3:56 PM
     
     
    Sign In to Vote
    0

    I have exactly the same problem with my Windows 7 Enterpise x64 on my laptop. It happened sometimes around last week, and it worked fine before that.
    I also have this strange Microsoft Virtual WiFi Miniport Adapter, but disabling, uninstalling it, or changing its settings - doesnt help.

    I tried disbling IPv6 - it doesnt help either.

     

    Any help will be really appreciated.

     

    Thanks

     
  • Monday, August 02, 2010 4:04 AM
     
     
    Sign In to Vote
    0
    I really need some help here. Any suggestions?
     
  • Wednesday, August 04, 2010 9:52 PM
     
     Proposed Answer
    Sign In to Vote
    2

    In two words: Domain vs. Workgroup

     

    Basically, here’s why it took an hour to figure this out: after using this file share SUCCESSFULLY for one Windows session thru address bar in Windows Explorer and subsequently mapping the drive and asking Windows to restore the network mapping on reboot, things got sour after the actual reboot.

    Typing share location in address bar would time out in 90 seconds.  The error is beyond cryptic.  I would know what to do if it said that IOINC Active Directory does not contain such-and-such user name.  Instead it said unspecified error 0x80004005.  Diagnostics could not determine anything either.

    After scratching my head, I went to disconnect the share, and try to re-establish it.  Direct approach (typing \\PCName\FileShare ) still led to the error code 0x80004005.

    Resolution was in sight, but still not obvious.  Map network share dialog has a way to enter new credentials.  Just re-tying password still took me to 0x80004005.

    I had to see DomainName\UserName as the fully-qualified user name to get what was going on.  Windows 7 Pro assumed that UserName was a domain user, whereas it isn’t. BUG, N times over.

    Having supplied the new credentials, I can now type \\PCName\FileShare in Windows Explorer address bar and see the files.  I haven’t tried, but I guess clearing passwords in Internet Explorer Options would have resolved the issue as well.

    Does this have anything to do with the version of our Active Directory server?  Is the behavior nicer with new AD?

    Vote up if this helps,

    -Greg


    • Proposed As Answer by GregChernis Friday, August 06, 2010 12:53 AM
    •  
     
  • Saturday, August 21, 2010 2:03 PM
     
     Proposed Answer
    Sign In to Vote
    0

    Thanks for your suggestions. Unfortunately this doesnt help me. Tried everything and still getting error 0x80004005

    I'm sure that one of windows updates makes it, because it worked before, and just stopped working without any reason.

     

    Additional information. When I'm trying to browse by clicking on computer name from my homegroup it first shows list of shared folders. but when I'm trying to open one of them it first trying to do this, but then after 5-10 seconds shows me error Network path not found 0x80070035

    What else I might try to restore my network access?

    • Proposed As Answer by Geron Profet Sunday, August 22, 2010 7:28 PM
    •  
     
  • Sunday, August 22, 2010 7:41 PM
     
     
    Sign In to Vote
    0

    I had the exact same problem as descibed. For some reason I could no longer connect to my NAS drive via my network share or by typing  \\machine\share in windows explorer.

    Then I remembered that I had installed PHP5, apache, a web deployment tool and some other additional tools to run Wordpress locally. The troubles started around that time. I used system restore to go back before the newly installed programs.

    That solved it for me. See this site for instructions on how to use system restore: http://www.sevenforums.com/tutorials/700-system-restore.html

    @axlns - The problem is probably not caused by windows update because I just updated my system (windows 7 ultimate - 32bit) to all latest updates and I can still connect to my network shares.

     

     
  • Monday, August 30, 2010 4:09 AM
     
     Proposed Answer
    Sign In to Vote
    13

    I finally fixed my problems. It turns out that my network adapter somehow loosed component called "Client for Microsoft Networks", not sure how that happened, I certainly did not removed it manually. Anyway, I have installed it back, rebooted, and voila, everything started working again!

    • Proposed As Answer by axlns Monday, August 30, 2010 4:09 AM
    •  
     
  • Thursday, November 04, 2010 6:32 PM
     
     
    Sign In to Vote
    0

    Xiaofeng did you ever fix the problem?  I too got the same problem on my Windows 7 Professional Ed PC... I get the same "Windows Cannot Access \\192.168.102.220", "Error code 0x80004005" when I access my own machine's shares from my file explorer's address bar.  Same error when I type in my IP and hostname directly. I also have Firewall disabled.  This computer is NOT inside an AD domain, just the default workground named WORKGROUP.

    I did not install any new hardwares and didn't move any shares. There's only 2 connections, "Bluetooth Network Connection" and "Local Area Connection". Client for Microsoft Networks, File and Printer Sharing, and NetBIOS over Tcpip are all enabled in my LAN.

    PLEASE HELP!! Could this be a bug in Windows 7?

     
  • Sunday, November 28, 2010 4:19 PM
     
     
    Sign In to Vote
    1

    Had similar issues as described in 'Lyndon's Mobile' post above.  NAS (\\192.168.1.xx\Public) accessible from laptop and mac mini, desktop system refuses to connect throwing 0x80004005 error.  Both the laptop and desktop system are win7 home premium.  Following the suggestion from 'axlns' post 'Client for Microsoft Networks' was not installed on the desktop system network adapter.  Installing it fixed the issue and NAS is now accessible to all three systems.   It was working on all three platforms in the past, I'm not sure how it 'broke'.  About the only difference between the laptop and desktop systems has been the installation of HP networked printer drivers.  As a test the same drivers were installed on the laptop and shutdown/restart preformed.  NAS and printer are working fine so I haven’t got a clue when or how the 'Client for Microsoft Networks' got uninstalled on the desktop system.  Something else ‘changed’ between 11/27/2010 and 10/17/2010, my last desktop backup date to the NAS.

     
  • Sunday, January 02, 2011 8:33 PM
     
     
    Sign In to Vote
    0
    I too, am having the same problems WIH7 ULT, 64bit.  I can open the web brower for the webpage setup but cannot access the drive, no matter what I try.  Am using a work group setup.Another laptop and two desktops have no issues.  Just this laptop. The problem just appeared.  I tried reverting without success.
    William R. Johnson
     
  • Monday, January 17, 2011 11:59 AM
     
     Proposed Answer
    Sign In to Vote
    1

    I had a similar problem as axlns and followed the steps advised and now my windows 7 laptop can "see" xp and earlier computers on the network. 

    the solution was to add back clients for microsoft network which for some reason was not there in the wireless adapter properties.

    adoor

    • Proposed As Answer by Driftmotion Sunday, December 02, 2012 5:13 AM
    •  
     
  • Tuesday, February 08, 2011 7:33 PM
     
     
    Sign In to Vote
    0

    Same problem with a MSI Wind Notebook.
    I was looking for anything else but I could't see that the "Client for Microsoft Networks" didn't appear in the properties fo the network adapter.
    Now, I wonder why it dissapeared in the first place!

    Thank you axlns anyway

     
  • Wednesday, February 09, 2011 12:45 AM
     
     Proposed Answer
    Sign In to Vote
    2

    THANKS!  IT'S FIXED ==> (GregChernis's "In two words: Domain vs. Workgroup")


    ====FIX
    Mapping a network drive to the share (\\192.168.x.y\folder_name) and selecting "use different network credentials" did the trick even though the network credentials I typed were identical the logged-on user's Windows UserID and password (no domain prefix, btw). The network share appeared immediately.


    ====My 80004005 problem background
    For awhile now, I've been dealing with that 80004005 error when trying to access a network share via \\192.168.x.y\folder_name on one of our remote client PCs accessing a shared folder on our Win2008R2 server (workgroup, not ActiveDirectory) over VPN.  Over VPN, all our OSX Macs (using smb://192.168.etc.etc) worked perfectly first try, as did WinXP PCs and a Win7 PC, but our only Vista PC Home Premium (gag) kept getting the error 80004005. About a month ago, I told the remote user to upgrade to Vista SP1, then SP2 plus install remaining updates, but the ole 80004005 persisted. After connecting with VPN, the Vista PC could ping the server no problem, but typing the UNC (IP+folder) in an explorer bar always the generated 80004005; my goal was to create a shortcut for the user and not use a mapped drive.  But mapping a drive ( including typing in the UNC and choosing alternate credentials) fixed the problem!  After this, typing the UNC in explorer also worked, but not after restarting Vista and reconnecting the VPN; we have to use a mapped drive instead so the credentials are stored ok.
    Basically, it seems the credentials that Vista used for the UNC were wrong and it never prompted for alternate credentials. I dodeca-checked that the Vista Windows log-on user ID and password matched the Server's credentials for this user (which also matched the successful VPN credentials, too, btw) but 80004005 always appeared.


    ====Theory
    I concur that mapping the network drive per se didn't fix the problem, but the mapping option of entering alternate credentials did the trick.  The bugs, in my opinion, are (1) that Vista Home Premium SP2 (and pre-SP1 and SP1) don't prompt for a user id/password when its stored credentials fail to connect to a UNC address typed into the explorer bar, and (2) that Vista didn't apply the user's Windows log-on credentials to the attempted UNC access (I know this because the alternate credentials I typed that worked were identical to the Windows logon (and VPN credentials)).


    ====Request from MS
    Make Vista Home Premium prompt for connection credentials if the stored ones don't match for a UNC-typed connection in the explorer bar rather than throw up an error.


    THIS THREAD HAD THE BEST 80004005 ANSWERS BY FAR of any I scoured via Google.

    • Edited by UpAndRunning Wednesday, February 09, 2011 12:46 AM credit to gregchernis
    • Proposed As Answer by joggerjed Wednesday, September 19, 2012 2:06 PM
    •  
     
  • Monday, July 04, 2011 5:39 PM
     
     
    Sign In to Vote
    1
    Mine was also the client for MS networks had been removed. Added this back and was able to browse. Have no clue how it was removed, but it is better now.
     
  • Wednesday, September 14, 2011 7:31 AM
     
     
    Sign In to Vote
    0

    Hi,

     

    Can you pls tell me how to reinstall the client for microsoft networks.

    I am having the same problem!

     
  • Thursday, October 06, 2011 9:48 PM
     
     
    Sign In to Vote
    0

    Any other solution on that problem? I tried all the mentioned things, but nothing helped.

     

    Thanks,

     

    S.

     
  • Monday, October 24, 2011 11:13 PM
     
     
    Sign In to Vote
    1

    I finally fixed my problems. It turns out that my network adapter somehow loosed component called "Client for Microsoft Networks", not sure how that happened, I certainly did not removed it manually. Anyway, I have installed it back, rebooted, and voila, everything started working again!


    You are my hero! I have been searching online for two days and going down the path of virus removal, registry edits, updates, firewalls and everything else under the sun! Added the Client for Microsoft Networks and I'm back up and running on my network. No idea how that was ever removed?! I had been sharing on the network with no problem for a couple months and then this randomly came up. Thanks for the weird fix that actually fixed it!
     
  • Monday, October 24, 2011 11:17 PM
     
     
    Sign In to Vote
    0
    codenamemessiah - go to your network connections, right click and go to Properties. In there, click 'Install' and choose 'Client' and you'll see the option there. Hope that helps.
     
  • Friday, November 11, 2011 10:14 PM
     
     
    Sign In to Vote
    0

    THKS, It works for me too,

    I don't know how to disapear it, but now works.

     

    Thanks.

     
  • Monday, December 12, 2011 9:51 PM
     
     
    Sign In to Vote
    0

    This will only work if you are trying to access computer from a different domain or workgroup. Under your NIC, IPV4 propreties -> Advance -> DNS tab -> Append these DNS suffix(in order): -> add domain names or workgroup names from which you are trying to access the resources.

    I hope this helps.

     
  • Monday, December 26, 2011 3:53 PM
     
     
    Sign In to Vote
    0

    I had the same problem and this work for me:

    http://www.ryanvictory.com/posts/automating-6to4-adapter-removal-in-windows/

     

     

     
  • Friday, January 20, 2012 4:07 PM
     
     
    Sign In to Vote
    3

    Had same problem, but nothing here worked.

    Oddly I could bring up a cmd window and dir \\shareip\share, I could even xcopy files from shares.

    I used autoruns and eventually figured out that my NetworkProvider order was incorrect. the "LanmanWorkstation" entry had been chopped in half. Modifying the entry restored functionality instantly.

    Registry key... HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order  = (REG_SZ) "RDPNP,LanmanWorkstation"

     

     
  • Monday, April 23, 2012 8:31 AM
     
     
    Sign In to Vote
    0

    Hello,

    These days when I try to open a shared folder in other machines(including XP, Vista, 7, Server 2003/2008) from my own Windows 7 Ultimate pc, I get a Network Error dialog saying:
    Windows cannot access \\machine\sharedfolder, error code 0x80004005, unspecified error.

    It aslo failed with IP.  And I have disable the Firewall

    But the other XP, Vista, Server 2003 and Server 2008 machines can reach each other and they even can open the shared fodler from my Windows 7.

    It's too strange. Maybe you can give me some useful suggestion.

    Thanks.

    Xiaofeng

    问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net

     
  • Friday, June 01, 2012 9:15 PM
     
     Proposed Answer
    Sign In to Vote
    0

    Thank you, mcgoober.  You set me on the right path.  I discovered:
    HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order - Provider Order
    and
    HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HWOrder - Provider Order
    values were set to LanmanWorkstation,RDPNP in both string values referenced above.  I changed these both to RDPNP,LanmanWorkstation and I was then able to connect without a problem.

    • Proposed As Answer by sharpwaves Thursday, September 27, 2012 10:18 AM
    •  
     
  • Sunday, July 01, 2012 9:38 PM
     
     
    Sign In to Vote
    0
    McGoober, you saved my arse.  I had a working Win 7 Pro computer on a domain and lost access to the server and mapped drives.  With your comments, I determined that a Lotus update I performed earlier today to support a feature called "single user logon" wiped out the contents of the HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order key with the exception of one entry the update made.   I was able to use a working Win 7 Pro workstation to re-enter the correct values and am now connected to server with all mapped drives back.  Thanks.
     
  • Monday, July 09, 2012 1:41 PM
     
     
    Sign In to Vote
    0

    This worked for me

    http://www.orison.biz/blogs/chall3ng3r/?p=2932

     
  • Wednesday, September 19, 2012 2:12 PM
     
     
    Sign In to Vote
    0
    I tried this as a resolution for the same error message on a Win7 64 bit enterprise system that was unable to access our institution's data shares.  I created the mapped network drive, and checked options to reconnect at logon (created an error at reboot or log on, but ignored) and to connect using different credentials.  The client connected manually to the mapped drive and also had to type in the domain name\user name to successfully connect.  Thanks for the resolution.
     
  • Thursday, October 04, 2012 5:07 AM
     
     Proposed Answer
    Sign In to Vote
    3
    Please ensure the windows service below was started:
    - Server
    - TCP/IP NetBIOS Helper
    - Workstation
    • Proposed As Answer by Joachim89 Wednesday, October 31, 2012 10:15 AM
    •  
     
  • Wednesday, October 31, 2012 10:16 AM
     
     
    Sign In to Vote
    1
    Please ensure the windows service below was started:
    - Server
    - TCP/IP NetBIOS Helper
    - Workstation

    We had this problemen on a 2008 server.

    Thanks to this post we found out the service "Server" wasn't running.

     
  • Sunday, November 18, 2012 7:48 PM
     
     
    Sign In to Vote
    0
    for me, the solution was noticing that Client for Microsoft Networks was missing for my network adapters... added that in and voila... access to all drives restored.
     
  • Friday, January 04, 2013 3:38 PM
     
     Proposed Answer
    Sign In to Vote
    1

    Had same problem, but nothing here worked.

    Oddly I could bring up a cmd window and dir \\shareip\share, I could even xcopy files from shares.

    I used autoruns and eventually figured out that my NetworkProvider order was incorrect. the "LanmanWorkstation" entry had been chopped in half. Modifying the entry restored functionality instantly.

    Registry key... HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order  = (REG_SZ) "RDPNP,LanmanWorkstation"

     


    I am on Windows 8, and I also had this problem. Tried everything on this thread, and nothing helped me.

    What saved me was this post: I went to command line, and tried NET USE, and received another error code: "System error 2148073478". Googled it, and the first hit was this post -> http://support.microsoft.com/kb/2686098

    It seems that Windows 8 / Server 2012 implements a new SMB protocol, 3.0 according to this post, and it may have some problems with older protocols. I made the 2nd workaround, and now it works :)

    If you are on Windows 8 / Server 2012, you should definitely try this!
     
  • Tuesday, March 05, 2013 9:47 AM
     
     
    Sign In to Vote
    0
    I uninstall SHREWSOFT VPN software and it solve this problem (after restart).
     
  • Thursday, April 04, 2013 9:12 AM
     
     
    Sign In to Vote
    0

    Hello,

    Obviously a lot of things can cause this.  Here's what fixed it for me.

    Opening the properties of my network adapter (in my case my wifi) and found that CLIENT FOR MICROSOFT NETWORKS was unticked.

    As soon as I ticked it, and clicked OK, swoosh!  Everything started working, queue started printing, and I could browse other shares.

     
  • Monday, April 08, 2013 6:12 PM
     
     
    Sign In to Vote
    0

    Had same problem, but nothing here worked.

    Oddly I could bring up a cmd window and dir \\shareip\share, I could even xcopy files from shares.

    I used autoruns and eventually figured out that my NetworkProvider order was incorrect. the "LanmanWorkstation" entry had been chopped in half. Modifying the entry restored functionality instantly.

    Registry key... HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order  = (REG_SZ) "RDPNP,LanmanWorkstation"

     


    I am on Windows 8, and I also had this problem. Tried everything on this thread, and nothing helped me.

    What saved me was this post: I went to command line, and tried NET USE, and received another error code: "System error 2148073478". Googled it, and the first hit was this post -> http://support.microsoft.com/kb/2686098

    It seems that Windows 8 / Server 2012 implements a new SMB protocol, 3.0 according to this post, and it may have some problems with older protocols. I made the 2nd workaround, and now it works :)

    If you are on Windows 8 / Server 2012, you should definitely try this!
    It worked! Thanks!
     
  • Tuesday, April 16, 2013 4:48 PM
     
     
    Sign In to Vote
    0

    We're having this problem intermittently. Several Win 7 64 bit workstations are randomly losing connection to one of our shared drives from a Windows 2003 server.
    1) In Windows Explorer for example trying to access \\caedc1\Macshare results in:

    Windows cannot access \\caedc1\Macshare
    Error code: 0x80004005
    Unspecified error

    2) Then net use results in the following seemingly, the share is still there:

    Status       Local     Remote                    Network

    -------------------------------------------------------------------------------
    OK           H:        \\caedc1\users$\me        Microsoft Windows Network
    OK           S:        \\caedc1\shared$          Microsoft Windows Network
    OK           Z:        \\caedc2\T-L-Video        Microsoft Windows Network
    OK                     \\10.0.225.240\Macshare   Microsoft Windows Network
    OK                     \\caedc1\users$           Microsoft Windows Network
    The command completed successfully.

    3) Pinging the DNC path works:
    C:\Users\me.CAE>ping caedc1

    Pinging caedc1.xyz.com [10.0.225.240] with 32 bytes of data:
    Reply from 10.0.225.240: bytes=32 time=17ms TTL=128
    Reply from 10.0.225.240: bytes=32 time<1ms TTL=128
    Reply from 10.0.225.240: bytes=32 time<1ms TTL=128

    Ping statistics for 10.0.225.240:
        Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 17ms, Average = 5ms

    4) I can also access the files if I use the IP address like this, in Windows Explorer:
    \\10.0.225.240\Macshare\

    5) Trying to map another temporary share via the net use command results in this:
    C:\Users\me.CAE>net use t: \\caedc1\shared$
    System error 64 has occurred.

    6) IPv6 is disabled & "Client for Microsoft Networks" still exists.

    7) Windows Firewall is disabled.

    8) We use Symantec Endpoint Protection as our AV.

    9) A reboot always fixes the share.