Seagate Personal Cloud

Topic

New Reply

I purchased a Seagate Personal Cloud hard drive and connected it to my home network.  The drive appears under “This PC/Network” on all my computers (Windows 7, 8, and 10).  When I click on the drive icon on my Windows 7 & 8 computes, the Public folder appears; and I simply click on the Public folder to access the drive space for copying and pasting files.

However when I click on the drive icon on my Windows 10 computers, I receive the following error message:

\\MYCLOUD-7FK48J is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  The network address is invalid.

I have done an Internet search, but I cannot find the solution to this issue.  Is there some sort of security or network setting in Windows 10 that needs to be changed in order for me to access the drive?  Is there an IP address for my Seagate Personal Cloud that would allow me to access the drive using a web browser?

Reply | Quote

Replies

The Homepage of my Western Digital \\MyCloud server which is attached to a router and a Win7 box appears at 192.168.0.3.

Reply | Quote

There could be several things going on, which version of Windows 10 do you use?

When the Windows 7 computer is off have you tried access the My Cloud server with Windows 10?

Reply | Quote

How do you know the unit is called “\\MYCLOUD-7FK48J”?
Try connecting via the IP address, e.g “\\192.168.0.5”.

cheers, Paul

Reply | Quote

How do you know the unit is called “\\MYCLOUD-7FK48J”?

He/she is simply quoting the error message that they got from Windows when they tried accessing the drive. The following is a direct quote from the original post that started this thread:

I receive the following error message:

\\MYCLOUD-7FK48J is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  The network address is invalid.

The above is a standard error message when Windows can’t find a network path it has set up. I’ve gotten it when a path suddenly isn’t available that has been available before.

However, since @ctnance ‘s problem is on a Windows 10 machine, is it possible that one of the very recent Win10 updates has disabled a version of SMB within Win10 that the Windows 7 and 8 computers are using to access the drive? In other words, could Win10 be running with SMB1 completely disabled through Win10’s default recent behavior which is then rendering the drive inaccessible due to the drive needing to use SMB1 instead of SMB2?

Reply | Quote

If the Seagate Personal Cloud drive is using SMB1 to communicate, then the OP won’t be able to access it from a Windows 10 (1809 or newer) computer unless he first enables SMB1 in Windows 10.

Search for “Turn Windows Features on or off”, then scroll through the list of Windows features till you find “SMB1.0/CIFS File Sharing Support”. Make sure it is checked (i.e. allow it). Expand it, and make sure all options other than “Server” are checked (you don’t need that one). Click Apply. Reboot, and you should be good to go.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote