Connecting PCs across a network
-
- Administrator
- Posts: 12320
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connecting PCs across a network
Please check the permissions on the directories that were not copied
StuartR
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
They all have permission for full edit. I did that along with the sharing of 20 folders.
-
- Administrator
- Posts: 12320
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connecting PCs across a network
I really have no further idea here. If you can see the files across the network, and you can copy some of them, and you have full permissions on all the files, then I have no more suggestions!
StuartR
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
-
- Administrator
- Posts: 12320
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connecting PCs across a network
I would normally suggest that you check the permissions on the share itself, as well as on the files, but I think if this were wrong then you wouldn't be able to copy any of the files. I guess it's worth a check though. It can't do any harm to check.
Look at the properties of the shared folder. Select the Sharing tab, click on Advanced Sharing..., click on Permissions, grant Full Control access to Everyone.
Look at the properties of the shared folder. Select the Sharing tab, click on Advanced Sharing..., click on Permissions, grant Full Control access to Everyone.
You do not have the required permissions to view the files attached to this post.
StuartR
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
Yes that is what I did for all the folders.
-
- GoldLounger
- Posts: 2599
- Joined: 24 Jan 2010, 15:26
- Location: Olympia, WA
Re: Connecting PCs across a network
Are any of these files in the User Account's "Documents" folder?
If so, that just may be the issue.
If so, that just may be the issue.
I am so far behind, I think I am First 
Genealogy....confusing the dead and annoying the living

Genealogy....confusing the dead and annoying the living
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
-
- Administrator
- Posts: 12320
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connecting PCs across a network
The program files (x86) folder is not a normal folder. I am pretty sure that this would all work if you were accessing files on a normal drive, not C:
Here's something you could try, I have NOT tested this, so I don't guarantee that it will work. Have a look at this article, follow the instructions to set the value of registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy
to 1, and see if doing this on the computer where the files are enables you to access the files.
AFTER you have set that policy, you could also try connecting to the C$ administrative share and see if that lets you get to the files you want.
Here's something you could try, I have NOT tested this, so I don't guarantee that it will work. Have a look at this article, follow the instructions to set the value of registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy
to 1, and see if doing this on the computer where the files are enables you to access the files.
AFTER you have set that policy, you could also try connecting to the C$ administrative share and see if that lets you get to the files you want.
StuartR
-
- GoldLounger
- Posts: 2599
- Joined: 24 Jan 2010, 15:26
- Location: Olympia, WA
Re: Connecting PCs across a network
There really are NOT any files that are in the Program folder that can be or should be shared.
What file(s) are you trying to access that are in the Program folder and their full path?
What file(s) are you trying to access that are in the Program folder and their full path?
I am so far behind, I think I am First 
Genealogy....confusing the dead and annoying the living

Genealogy....confusing the dead and annoying the living
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
Well, whether or not files located in program files (x86), should be shared is a moot point, there are files that are located within a sub sub subs folders that downloaded over time and were far too large to transfer with a jump drive. This is the specific reason for the thread.
Stuart, I have not tried your last suggestion, been away from the two machines for a few days.
Stuart, I have not tried your last suggestion, been away from the two machines for a few days.
-
- GoldLounger
- Posts: 2599
- Joined: 24 Jan 2010, 15:26
- Location: Olympia, WA
Re: Connecting PCs across a network
If they are too large to even copy to an external device, then they would also be way too large to be sharing.
The performance of both machines would be very slow while the sharing of said file(S) is being done.
Edit:
Have read at https://www.addictivetips.com/windows-t ... e-network/
Also note, have you tried to share the C: drive and not just a few folders?
On my network, I have shared the C drive and I can go to both Program Files and Program Files (86) folders.
I have not tried to copy any files over the network as I see no need to.
The performance of both machines would be very slow while the sharing of said file(S) is being done.
Edit:
Have read at https://www.addictivetips.com/windows-t ... e-network/
Also note, have you tried to share the C: drive and not just a few folders?
On my network, I have shared the C drive and I can go to both Program Files and Program Files (86) folders.
I have not tried to copy any files over the network as I see no need to.
I am so far behind, I think I am First 
Genealogy....confusing the dead and annoying the living

Genealogy....confusing the dead and annoying the living
-
- 5StarLounger
- Posts: 1054
- Joined: 21 Jan 2011, 16:51
- Location: Florida
Re: Connecting PCs across a network
Considering that a 1 TERABYTE external HDD is under $50 now, the statement these files are too big raises flags. Just how large are these files?bknight wrote: ↑18 Jan 2022, 10:48Well, whether or not files located in program files (x86), should be shared is a moot point, there are files that are located within a sub sub subs folders that downloaded over time and were far too large to transfer with a jump drive. This is the specific reason for the thread.
Stuart, I have not tried your last suggestion, been away from the two machines for a few days.
Also, since setting a share into the folder structure Windows calls C:\Programs\... is not possible due to system level restrictions, consider this process:
1. Set up a SHARE to a folder named XFER (for example) that you create under your C:\USERS\{userid}\Documents folder.
2. Using a MOVE command in a CMD file or the CMD prompt to move these files to the transfer folder. The MOVE command just changes the folder location and not the data itself so it's very quick.
3. Complete the transfer using the methods outlined above to access shared folders from the destination PC.
PJ in (usually sunny) FL
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
After NET USE \\computerB\IPC$ /user:username worked last week, now I get an error option user:username is unknown.
-
- Administrator
- Posts: 12320
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connecting PCs across a network
That seems improbable. Did you copy and paste the exact same command?
You could try rebooting in case of some strange system corruption.
You could try rebooting in case of some strange system corruption.
StuartR
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
Firstly, tell me how to copy in windows and then paste in command prompt. That is a new one to me.
Secondly, after reading the command carefully it seemed that the command was correct. I'll try this morning again.
ETA: The copy/paste works from windows to command.
I get the same error message.
Secondly, after reading the command carefully it seemed that the command was correct. I'll try this morning again.
ETA: The copy/paste works from windows to command.
I get the same error message.
-
- Administrator
- Posts: 76649
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Connecting PCs across a network
Did you replace username with YOUR Windows username?
Regards,
Hans
Hans
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
I attempted
Comp-PC and that failed also. System error 64 The specified network name is no longer available.
Comp-PC and that failed also. System error 64 The specified network name is no longer available.
-
- 5StarLounger
- Posts: 1154
- Joined: 08 Jul 2016, 18:53
Re: Connecting PCs across a network
After re-booting both PCs this was the final solution, thanks to Stuart and Hans both adding comments toward the final solution. Also, thanks to PJ_inFL for his suggestion of moving files from the program files (x86) to a user folder.
NET USE \\CompB-pc\IPC$ /user:username
NET VIEW \\CompB-pc
NET USE G: \\CompB-pc\C
Copy G:\users\username\documents\xfer\folder1 c:\xfer\folder1
NET USE \\CompB-pc\IPC$ /user:username
NET VIEW \\CompB-pc
NET USE G: \\CompB-pc\C
Copy G:\users\username\documents\xfer\folder1 c:\xfer\folder1