F5F Stay Refreshed Software Operating Systems Unable to reach the shared directory on a Windows 10 machine (hosted on another Windows 10 device).

Unable to reach the shared directory on a Windows 10 machine (hosted on another Windows 10 device).

Unable to reach the shared directory on a Windows 10 machine (hosted on another Windows 10 device).

C
cabub3
Junior Member
38
10-14-2016, 05:06 PM
#1
Hi, I've got a Plex server on another Windows 10 machine that I own. For some time I used file sharing to manage files on the other computer, but recently it stopped working intermittently. I also rely on remote desktop for access, though transferring files via it is slow and tiring because you need to maintain the connection constantly. I followed the setup instructions and everything was functioning well until now. The error message is attached as an image in this post. Any assistance would be greatly appreciated!
C
cabub3
10-14-2016, 05:06 PM #1

Hi, I've got a Plex server on another Windows 10 machine that I own. For some time I used file sharing to manage files on the other computer, but recently it stopped working intermittently. I also rely on remote desktop for access, though transferring files via it is slow and tiring because you need to maintain the connection constantly. I followed the setup instructions and everything was functioning well until now. The error message is attached as an image in this post. Any assistance would be greatly appreciated!

N
noahHVH
Junior Member
4
10-28-2016, 10:56 AM
#2
Join the group. The system often behaves oddly, so restarting usually fixes things. Creating a real domain might work better.
N
noahHVH
10-28-2016, 10:56 AM #2

Join the group. The system often behaves oddly, so restarting usually fixes things. Creating a real domain might work better.

G
Gladiador70
Senior Member
698
11-03-2016, 12:16 PM
#3
I observed this too, it's frustrating. What exactly are you trying to set up with the domain? Also, just to clarify, I'm linking to a device on the same local network, and I don't require external access. That's the situation.
G
Gladiador70
11-03-2016, 12:16 PM #3

I observed this too, it's frustrating. What exactly are you trying to set up with the domain? Also, just to clarify, I'm linking to a device on the same local network, and I don't require external access. That's the situation.

M
MasterChi101
Member
117
11-09-2016, 02:28 AM
#4
I've encountered several problems when working with network share drives on Windows. Fixes have included name changes without my input, IP address errors, and the system failing to resolve issues on its own. Passwords sometimes lock files even though they’re empty, triggering pop-up warnings. I suspect there are more unnoticed factors at play. First, verify the computer names are accurate and that both PCs appear correctly on the switch. Test access with another machine to determine if the issue lies with the client or server side. Confirm security and sharing settings match your expectations. Consider adding your account as a specific user on the client PC instead of a general "all users" setting, and ensure the folder location matches the original creation point. Try disabling and re-enabling sharing. Unfortunately, the error messages are unclear, so you may need to troubleshoot each level of the network path. Sometimes it’s not obvious whether the problem is a wrong address or an access restriction, requiring a step-by-step split until the root cause emerges.
M
MasterChi101
11-09-2016, 02:28 AM #4

I've encountered several problems when working with network share drives on Windows. Fixes have included name changes without my input, IP address errors, and the system failing to resolve issues on its own. Passwords sometimes lock files even though they’re empty, triggering pop-up warnings. I suspect there are more unnoticed factors at play. First, verify the computer names are accurate and that both PCs appear correctly on the switch. Test access with another machine to determine if the issue lies with the client or server side. Confirm security and sharing settings match your expectations. Consider adding your account as a specific user on the client PC instead of a general "all users" setting, and ensure the folder location matches the original creation point. Try disabling and re-enabling sharing. Unfortunately, the error messages are unclear, so you may need to troubleshoot each level of the network path. Sometimes it’s not obvious whether the problem is a wrong address or an access restriction, requiring a step-by-step split until the root cause emerges.

W
117
11-16-2016, 05:21 PM
#5
I'm checking the DNS settings first, then looking at the HOSTS file if needed.
W
whitecastle200
11-16-2016, 05:21 PM #5

I'm checking the DNS settings first, then looking at the HOSTS file if needed.

T
TrueMM2
Member
227
11-17-2016, 01:44 AM
#6
Updated to Windows forum area
T
TrueMM2
11-17-2016, 01:44 AM #6

Updated to Windows forum area

J
JenpaiMC
Member
106
11-17-2016, 01:53 AM
#7
I resolved the problem by setting up the internal FTP server on Windows instead of relying on the unreliable shared folder. This approach worked for me; if not, I’m unsure of the solution.
J
JenpaiMC
11-17-2016, 01:53 AM #7

I resolved the problem by setting up the internal FTP server on Windows instead of relying on the unreliable shared folder. This approach worked for me; if not, I’m unsure of the solution.