A
Anodyne4
Guest
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, 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!
More...
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!
More...