Try to access the devices over the network once.
Then Enable the Enable insecure guest logons
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation It will open the Local Group Policy Editor. In my case, I was able to see the devices available in my network but I was not able to connect them.įinally, I got it working by following steps:ġ.2) Execute gpedit.msc. I was facing the same issue and it was very difficult to find the solution. I had the same issue and finally found the following solution from "OmShinde" which solved the issue: Seagate Dashboard can connect fine.Īny advice or help would be MOST appreciated! I have installed the Seagate Discovery Tool, which finds the drive immediately - still cannot connect via explorer.
This all makes no difference - still get the same errors. tried //DRIVE, DRIVE/username and password tried //DRIVE, COMPUTERNAME/username and password I have gone to credential manager, as suggested by other forums, and have: If I try "net use \\DRIVE" I get: "System error 64 The specified network name is no longer available" If I try "net view \\DRIVE" from the command prompt, I get: "System Error 53". The http management interface also works fine. I can ping the drive, both by its IP and its name. The DLNA server of this drive appears under This PC -> Network Locations and all of the public folders can be accessed without a problem. If I try to map it to a new network drive, I get the same error. The drive appears as a computer under the network tab, but when I click on it, I get an error of :Ĭheck the spelling of the name, there might be a problem with your network" 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).
0 kommentar(er)
