Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 6, 2015 12:33 PM | 1 vote
Hi there,
After updating to Windows 10 Home Single Language from 8.1, I can no longer connect to private folders on my 2Tb Seagate Central network drive (The drive is connected via LAN to a wifi router, which my laptop connects to).
The drive appears as a computer under the network tab, but when I click on it, I get an error of :
"Windows cannot access //DRIVE
Check the spelling of the name, there might be a problem with your network"
If I try to map it to a new network drive, I get the same error.
The DLNA server of this drive appears under This PC -> Network Locations and all of the public folders can be accessed without a problem.
I can ping the drive, both by its IP and its name. The http management interface also works fine.
If I try "net view \DRIVE" from the command prompt, I get: "System Error 53".
If I try "net use \DRIVE" I get: "System error 64 The specified network name is no longer available"
I have gone to credential manager, as suggested by other forums, and have:
- removed the credentials entirely
- tried //DRIVE, username and password
- tried //DRIVE, COMPUTERNAME/username and password
- tried //DRIVE, DRIVE/username and password
This all makes no difference - still get the same errors.
I have installed the Seagate Discovery Tool, which finds the drive immediately - still cannot connect via explorer. Seagate Dashboard can connect fine.
Any advice or help would be MOST appreciated!
All replies (39)
Thursday, August 13, 2015 2:40 PM ✅Answered | 1 vote
UPDATE - SOLVED
The issue is with the account you use to log onto the machine with.
Using the Microsoft account does not work, but when I switched to using a local account I could then use the Seagate Discovery Tool successfully.
--> 1. Open Settings, and click on the Accounts icon.
--> In Your account, click on the "Sign in with a local account instead" link on the right side at the top.
--> Follow the prompts, log out, log in - issue is resolved
Thursday, August 6, 2015 12:38 PM
Have you verified that the Windows firewall isn't blocking attempts?
Thursday, August 6, 2015 12:39 PM
NB:
- I have also tried mapping the network drive to the IP - not working.
- The network drive has the most recent firmware installed
Thursday, August 6, 2015 12:42 PM
I have also tried :
"Are they in the same workgroup?
You can try:
- Right click on the Network icon in the right bottom, select Network and Sharing Center.
- Click “Change advanced sharing settings”.
- Under “All Network”, select on “Enable file sharing for devices that use 40- or 56-bit encryption”
With no success.
Thursday, August 6, 2015 12:43 PM
I have also tried turning off Window Firewall - no change.
Thursday, August 6, 2015 1:20 PM | 1 vote
I've read several other posts where users are having issues connecting to NAS/NAS type devices. I haven't seen a resolution yet; will post back if I do.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Friday, August 7, 2015 6:10 AM
Hello,
Can you temporarily remove any third-party AV program or Firewall to have a test. Sometimes, disabling the software may not work.
Thanks,
Simon Wu
TechNet Community Support
Friday, August 7, 2015 12:35 PM
I am having the same problem.
However if I plug the computer in via Ethernet cable it can read and find it, My other 2 computers on Wifi can access and find it (one on windows 10 also, the other on windows 7)
It just appears this one on wifi I have the issue.
Any ideas on what might be setting/problem I am missing?
Friday, August 7, 2015 1:58 PM
I have AVG Free - removed completely, and disabled Windows Firewall. Still the same issue.
Friday, August 7, 2015 2:00 PM
Also : If the credentials are removed completely, I get no pop up to enter new ones. It doesnt get to the authentication stage, but dies with an error of "The network name has changed".
Saturday, August 8, 2015 4:15 PM | 1 vote
Hi I was having the same issue with my Seagate Central 2TB Network drive. The only difference was I'm using Windows 10 Pro.
I was able to solve my problem by running the Seagate Discovery Tool for Windows which is available from the Seagate site.
When I ran it, it spotted my drive straight away and asked me to log in. It then mapped the public folder and my own private folder to the Z: and Y: drives on my machine. I was able to then access both fine.
Hope this will also solve your issue.
Monday, August 10, 2015 5:36 AM
Hi, thanks for the advice, but this does not work. As I previously wrote, the Discovery Tool finds the drive immediately, but when clicking on the drive in the tool, nothing happens, no log in boxes appear. I get the circular waiting cursor for a few seconds, but nothing happens after that.
Monday, August 10, 2015 5:40 AM
The error log directly after that shows ::
"The description for Event ID 0 from source Discovery tool cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Discovery tool error
Can't map public folder of DRIVE(10.0.0.6), error code:64"
Thursday, November 19, 2015 12:29 PM
This did not resolve my issue.
Installed discovery tool and this mapped the drive but as an IP address, but I was still unable to manually map the drive manually using the IP address.
Turned out that my local network was not showing up as a "Trusted Network", and was down as a "Public Network"
Now I can map and it connects to NAS perfectly
Friday, November 20, 2015 12:11 PM
I am having the same problem. Can you tell me how to check if my local network is showing "trusted network"?
Thank you
Monday, November 23, 2015 6:01 PM | 1 vote
Open the "Network and Sharing Center" from the Control Panel, and it will tell you if you're network connection is either 'public', 'private' or 'work'.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Sunday, March 13, 2016 2:23 AM
This issue is not solved... I want to log with my hotmail account always and be able to see my cloud disk.
Wednesday, March 16, 2016 7:24 PM | 1 vote
See if anything in this thread helps you. Someone posted on March 1st that MS released a patch for Win10 that helped them. Not sure if it will apply to you.
Patch:
March 1, 2016 — KB3140743 (OS Build 10586.122)
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Wednesday, April 12, 2017 8:09 AM
Great that you have a solution. Can we have this in common man's language please.
Sunday, May 21, 2017 1:41 PM | 6 votes
Hi Anodyne4
I have tried the following and it worked:-
-Ensure your network is Private
-You are accessing your Windows 10 with local account
-At Windows Feature, ensure SMB Direct, SMB 1.0/CIFS File Sharing Support are checked.
-Use the Seagate Discovery Tool to locate your Seagate Central NAS.
You should be able to see your folders! Hope it works for you :)
Thursday, August 31, 2017 9:27 PM
Hey, thanks for that! Just solved my problem ^^
Wednesday, September 27, 2017 2:58 PM
I've tried all 4 steps that you suggest and it still won't find the drive. All other PCs and Macs can see it but this new Windows 10 Pro cannot.
Saturday, December 23, 2017 2:32 PM
I have this same issue but cannot get it resolved. Can you help?
Sunday, January 21, 2018 6:32 AM | 6 votes
Thank you! For some unknown reason access to my Seagate Central had become corrupted and i tried a lot of suggestions. When i checked Windows Feature, SMB 1.0/CIFS Client was the only of 3 items not checked. After checking it and rebooting, normal access was restored. And i'm using my normal Windows login, not a local login. Thanks very much.
Sunday, January 28, 2018 12:24 PM
Well done mate.
Your solution was the only one helped me.
Thanks
Saturday, March 31, 2018 5:22 PM
As a result I lose access to my Microsoft one drive, my dropbox and must login to my email every time I check it. This is ridiculous. This is also a security risk since I don't have a domain controller to enforce security rules for access.
Thursday, April 26, 2018 8:18 PM | 3 votes
Microsoft have disabled SMB1 in Windows 10 Pro (and maybe elsewhere), nice one again MS. I went into Control Panel >> Programs and Features >> Turn Windows Features On or Off and selected to activate SMB1 (against online recommendation). My 2 TB Seagate NAS now talks to me again... after a reboot, please wait, configuring windows etc. God, what a lash-up this system has become. I (sort of!) loved Windows until Windows 8 landed... who dreamt that rubbish up?
Jonno1945
Saturday, June 2, 2018 5:32 AM
it works thanks
Tuesday, June 5, 2018 1:59 PM
Lol never knew it was your initial link I followed
Wednesday, September 5, 2018 2:05 AM
This didn't solve the issue for me. I was already signed in as a local account.
Monday, September 17, 2018 1:33 AM
Solved: create a new windows credential
search for "manage windows credentials"
Then add a windows credential. I put in \PERSONALCLOUD for the network address and used my username and password to log into the nas with a web browser.
I tried all the other ways to solve the problem first listed above which didn't work for me, so you still might need to do those too.
Tuesday, January 1, 2019 3:48 PM | 3 votes
"At Windows Feature, ensure SMB Direct, SMB 1.0/CIFS File Sharing Support are checked".
This is the actual solution to the thread of unable to open or connect to the Files on your NAS even though you can see it on your network in File explorer. 2 Thumbs up!!!
Wednesday, January 2, 2019 7:10 AM
The primary reason for this issue on <g class="gr_ gr_29 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="29" id="29">windows</g> 10 - is the removal of support for SMB 1.0 client, you need to turn this feature on from the add remove programs menu - turn on/off windows features -> <g class="gr_ gr_140 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="140" id="140">smb</g> 1.0 client - select it to install and then restart ur machine.
Saturday, February 9, 2019 4:47 AM
Hey,
I had the same issue and finally found the following solution from "OmShinde" which solved the issue:
I was facing the same issue and it was very difficult to find the solution. In my case, I was able to see the devices available in my network but I was not able to connect them.
Finally, I got it working by following steps:
Step 1:
1.1) Press Windows+R (Open Run)
1.2) Execute gpedit.msc. It will open the Local Group Policy Editor.
1.3) Follow the dropdown options as:
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation
Then Enable the Enable insecure guest logons
Try to access the devices over the network once.
If it does not works then Step 2 can be followed.
Step 2:
1.1) Press Windows+R (Open Run)
1.2) Execute gpedit.msc. It will open the Local Group Policy Editor.
1.3) Follow the dropdown options as:
Local Computer Policy -> Computer Configuration -> Windows settings -> Security Settings -> Security Options
Then Disable the Microsoft Network client: Digitally sign communications(always)
While searching for solutions, I could found a lot of solutions and most of them have been included in this thread. As above steps worked for me, I thought of including them here.
Source: <https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-explorer-network-error-0x80070035-the/f30a1112-ffa7-4230-b843-ecc7ab8b5119?page=5>
Best regards,
NikPinguin
Monday, March 25, 2019 10:41 PM
this worked after I had to reinstall win 10 pro I needed to go back and check the boxes for Windows Feature, SMB 1.0/CIFS Client and re-enter the Personalcloud windows credentials back in. Now it works in windows explorer like always.
thanks
Saturday, June 22, 2019 7:50 PM
Thanks so much for your help. This worked a treat!!
Monday, June 24, 2019 6:28 AM
The solution in this link solved my problem. Give it a try!
Monday, November 11, 2019 10:50 PM
Microsoft have disabled SMB1 in Windows 10 Pro...
...I went into Control Panel >> Programs and Features >> Turn Windows Features On or Off and selected to activate SMB1...
...2 TB Seagate NAS now talks to me again... after a reboot...
Jonno1945
This resolved my issue, and did not require me to log in using a local account (as erroneously reported in a different response to this thread).
Saturday, February 29, 2020 2:01 PM
Is there anyway to post the SMB1 solution to the top of this thread? This is the solution.