Suddenly, few days ago my computer failed to connect to any shared network folder and greeted me with the error "Windows cannot access \\machine\sharedfolder, error code 0x80004005" every-time I tried accessing I am able to map a drive (both manually as via Explorer), but when I try to access the mapped drive I get an error "An unexpected network error occurred". Join 12,519 other subscribers Email Address Popular Recent Comments Unable to Sign In to Microsoft Money 2007 with Windows Live ID in Vista May 1st, 2007 Microsoft Money 2007 Unable to Error message when you use applications that are based on legacy Transport Driver Interface (TDI) filter drivers on a computer that is running Windows 7 Beta or Windows Server 2008 R2: check over here
IPv6 is disabled on all machines and it's not a "Server/Client" environment; merely shared drives/directories. user Thx, it helps me! Matthew Kent I wish this worked for me. It worked to fix a Windows 7 system and to fix a Windows 10 system. https://social.technet.microsoft.com/Forums/office/en-US/17c9ea7d-52df-4ef9-95fa-0a961d11bfa3/fix-for-cannot-access-nas-drives-sharefolder-is-not-accessible-or-error-code-0x80070035?forum=w8itpronetworking
Turtle Sunday, October 09, 2016 8:29 AM Reply | Quote 0 Sign in to vote Another one worked for me: Open your hosts file inC:\Windows\System32\drivers\etc. Win7 tries to open '\'. reply Actually, for all it helpe, I Permalink Submitted by DTMOC (not verified) on Fri, 02/20/2015 - 16:52 Actually, for all it helpe, I just used the string "RDPNP,LanmanWorkstation,webclient" without the Such a simple fix...
See below an example from the commandline This happens in all situations: - When a username and password are required for the share. On preview I did not have any issues browsing ny NAS, but after the fresh install I can not access the file shares at all. Now my mapped drives to a NAS don't work, and when I try to access the server, I get a "windows security" pop up asking for the network credentials. Cannot Connect To Nas Drive On Network They are Windows Shares that my XP partition can see and map to, same with my Linux box.
This should be better than sending a clear text password, but I think MS need to fix this. Nas Drive Not Showing On Network Windows 10 I've found articles where this issue has been solved by enforcing communication only to SMB 1.0 (on some other WD NAS products) unfortunately WD MY Cloud dont have that optionon Web Denis Friday, September 04, 2015 9:41 AM Reply | Quote 0 Sign in to vote THANKS IT WORKED!! https://forum.qnap.com/viewtopic.php?t=112857 Some background.
In Vista, Windows Explorer, I could access all the folders and files on all the NAS boxes. Windows 10 Nas Drive Not Accessible Enter the remote server computer name as the Internet or network address, and then enter the user name and password similar to MSA created on the remote server. My solution is: 1. On my old Vista notebook PC all five NAS devices were OK.
By the way, a colleague received the same update and had exactly the same problem on a different machine. http://support.wdc.com/knowledgebase/answer.aspx?ID=13180 No redundant technologies at all. Windows 10 Nas Access There is no restrictions for accessing this NAS, I can access it with my Vista computers, and when I use this computer (it is dual boot Vista/7) with Vista I can Nas Is Not Accessible. You Might Not Have Permission Good luck.
In the middle: Certificate Based Credentials On bottom: Generic Credentials I found my NAS in "Generic Credentials" but my NAS is configured for windows based authentication. check my blog anther Reboot of your machine? reply Yap, it works. Support from WD has failed to resolve, and I can access the NAS via other methods to play media etc so the NAS appears to be working correctly and WD have Nas Not Accessible Windows 10
Any idea how to fix it? Solution Assuming that you can save files on this share using standard methods and only access via Acronis vmProtect does not work, the troubleshooting steps are: Try specifying the share using Network-attached storage removes the responsibility of file serving from other servers on the network. this content In my case was due to the "jumbo packet" setting.
I hoped that the final update would fix this, but this still seems to be true. Nas Not Showing On Network Windows 7 Strangely, the computer was discovering other computers on the network and I was able to ping and SSH into them like my Raspberry Pi Network Attached Storage (NAS). There are evidently more Security and Permissions additions in Win 7 over and above Vista.
To solve this issue, all you need to do is to make this entry correct. Gillett. The future versions of Acronis vmProtect will be based on Linux kernel 3.3.xx + (currently it is 2.6.xx) with new SMB protocol version so these issues may be gone automatically. Buffalo Linkstation Cannot Access Shared Folder I was able to create new folder link targets under Network Locations.
Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks has to be installed on one the network connections. SAN use in network architecture NAS provides both storage and a file system. MyBookLive 192.168.1.174Click Save on the Edit menu, making sure it doesn’t save with any file extension Subsequently, I was able to use the name successfully to map the drive and my have a peek at these guys I have not been able to access my NAS with Windows 7.
Marten Thursday, December 12, 2013 8:21 PM Reply | Quote 6 Sign in to vote Hi, Many thanks for your posting on this nas drive issue, was helpful in directing me Reboot de Machine Info: http://technet.microsoft.com/en-us/library/ff633425(v=ws.10).aspx Edited by Stormbolie Tuesday, May 13, 2014 10:50 AM Tuesday, May 13, 2014 10:11 AM Reply | Quote 0 Sign in to vote Hi Stormbolie, Thanks I allow myself to ask people publishing on this or other forums, to say precisely what solution has worked for them. Sunday, January 05, 2014 7:42 PM Reply | Quote 0 Sign in to vote I tried the steps above without success.
IP address are assigned through DHCP. Friday, April 08, 2016 8:20 AM Reply | Quote 0 Sign in to vote Success! Once the items are installed you should see the NAS. Simply changing the network location to private resolved the problem.
also could try disabling homegroup. #3 montyuk, Jan 22, 2009 Thanweb New MemberJoined:Jan 20, 2009Messages:6Likes Received:0 i have disabled the homegroup, the network is home and still the same. #4 Thanweb, I ran an unnamed auto-tune software on my Windows 8.1 laptop to try to improve performance, after which I could no longer connect to my WD NAS Drive. The time now is 08:51. What finally worked for me was to add an entry to the Host.
You can now try to connect to network shared folders. Also, I am going to suggest to my provider at Telus that they should advise people of this possibility when a modem is changed or upgraded! Solution: Run Windows Updates on the Windows 10 computer. To make sure you have these items installed Open Network and Sharing Center.
Did you try to directly connect the device (via USB) to your Win 7 PC to see what happens? Run PowerShell as Administrator 2.Set-SmbClientConfiguration -RequireSecuritySignature 1 Answer Ywhen prompted to confirm the modification. 3.Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force Thursday, June 26, 2014 12:47 PM Reply | Quote 0 Math question * 15 + 5 = Solve this simple math problem and enter the result. My System Specs OS Windows 7 Enterprise TomTieDom View Public Profile Find More Posts by TomTieDom Page 1 of 2 1 2 > Error accessing NAS shares « Previous Thread |
NAS shares now work properly and I can access the NAS admin configuration pages. Friday, September 25, 2015 4:20 AM Reply | Quote 0 Sign in to vote Oh, thank you very much, machaeldowns, I'd like to add that your method works in Windows 10 Here is the information from the Ststus Page of the NAS. Not the answer you're looking for?