I can access this Desktop folder across the LAN and upload files from it.
But I cannot write to it.
I have other folders on that machine that I can write to.
I set them up.
I believe I've done all the same things with this Desktop folder yet I cannot write to it. Cannot drag and drop to it.
Anyone have any idea why?
Or what I should look at and check?
All users folders have special permissions the best way is to connect with the username password for that user or you will have to set NTFS permissions which can be dodgy
The shared Desktop folder must have read /write permissions (shared and NTFS permissions)
As a guide Laptop Drive share Solved - Windows 7 Forums
I get it. 'Downloads' is actually a sub folder in the 'Users' tree and that's what makes the difference. Whereas anything in C: like C:\blahblah that I might have created is not?
- - - Updated - - -
Thankyou. Looks like this is the bit I need:
If you are not that concerned about security, then you can set the Sharing permission for Everyone to have Full control. However, you will still be subject the NTFS permissions on that drive. To have full access you will need to add the Everyone group to the drive's permissions and grant it Full control. You should also turn off Password Protected Sharing in the Network ans Sharing Centre.
Because I did already share to everyone with full control and was surprised it didn't work. must be that. :)
The other problem if the folder your connecting to is a user folder and if the same user is logged in it may be locked as being in use
If you use cmdline you can connect as the user on the pc so no need to change permissions
# Authenticate with the username VboxSrv\user1 and password Passwrd123
Net use h: \\VBoxSvr\Win11\Documents /user:VboxSrv\user1 Passwrd123 /p:yes
Well that always will be the case in my setup here currently. For the 'other machine' I'm talking about is my own only in another building and when it is switched on I've usually logged in as the owner/admin of that machine. So that's the case you're talking about. I leave it like that when I go out.
Would it be different if the machine were switched on but no one logged in to it?
I think that 'net use' command creates a 'new disk' - 'h:' in the case you've given? Tried that some time ago and it wouldn't do it. Claimed there was already a connection to that drive. I was using drive 'K:' then. Got various hassles. I gave up on it.
I just can't get it straight. Instead of trying to fix my way of going about it how about if I asked instead what would be the optimum way to set your machines/user accounts up if that's what you want to do?
i.e. if you want to be able to access any of your machines on the LAN from any machine on the LAN. (they're all 'mine', being family machines I maintain) and read/write to any folder on them at any time?
The problem is if it was simple then it makes it simple for hackers and malware so MS have tightened it up after massive malware attacks. The cmdline works and you can use any drive letter you want
Quote