As I can see from your description you want to share a directory.
Since you use Windows 8 and I can see the "Security" tab you are using NTFS-filesystem.
It seems like you didn´t configure NTFS-permissions.
- Click on the "Security" Tab of the Folder you want to share.
- Then "Edit..."
- In the new window click "Add..."
- In the new window click "Advanced..."
- In the new window click "Find Now..."
- Select the user who needs the permission to acces the folder.
- Go back to the "Permissions for " dialog.
- Choose the user you added.
- Set permission to "Allow" / Full controll (Or at least read permission)
- Click Apply.
On the sharing tab, the only entry you Need is:
- Everyone
- With permission "Full Controll".
You can manage the permissions with the NTFS-Permissions of the Security Tab.
The rest of the configuration looks correct.
Answer from Andie2302 on Stack ExchangeAccess Denied error on one shared network resource but not another
How can I troubleshoot access permission errors to network shares on Windows 10 Pro PC
Access denied while running Win10 setup.exe from network share
Unable to Access Network Shares In Windows 10
Videos
As I can see from your description you want to share a directory.
Since you use Windows 8 and I can see the "Security" tab you are using NTFS-filesystem.
It seems like you didn´t configure NTFS-permissions.
- Click on the "Security" Tab of the Folder you want to share.
- Then "Edit..."
- In the new window click "Add..."
- In the new window click "Advanced..."
- In the new window click "Find Now..."
- Select the user who needs the permission to acces the folder.
- Go back to the "Permissions for " dialog.
- Choose the user you added.
- Set permission to "Allow" / Full controll (Or at least read permission)
- Click Apply.
On the sharing tab, the only entry you Need is:
- Everyone
- With permission "Full Controll".
You can manage the permissions with the NTFS-Permissions of the Security Tab.
The rest of the configuration looks correct.
Just a quick heads-up. When using an AD and sharing something to multiple people, using the authenticated users group over the everyone group is slightly more secure.
This is a default group when you do have an AD. It just means that if someone were to plug into a wall outlet they would also need a login that matches with your AD to get to your share.
Hi admins, I really need your help!
It seems I've hit a wall with this. I believe this is a wall I've hit before, however it seems Google doesn't want to take me back to the answers it gave me 3-4 years ago.
This is a home network, no AD domain, just a few (Debian) Linux servers.
I've setup a server with TFTP, and a Samba share, where I've got a win7 and win10 DVDs copied.
All fine and dandy, I can boot from PXE, and receive my WinPe image, do a net use to map my network share. I can also browse and copy files from this share, but it behaves as read-only, which is rather strange.
My problem begins at this step. If I want to run setup.exe for Win7 or Win10 from this WinPE, I get a "Access denied" which I believe is rather unhelpful.
My smb.conf is basically the default with Debian, to which I've added my share:[install]comment = Installation Mediaguest ok = Yespath = /smbshareread only = No
Does anybody have any ideas how to further troubleshoot this?
I don't want to use other tools like MDT or maybe FOG in case they come to mind as suggestions.
Hi Erdinç,
Thank you for your reply. You can try to modify the registry to see if the problem can be solved. Please refer to the following:
Open the registry and navigate to the following location:Computer \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Add the AllowlnsecureGuestAuth item and change the value to 1.
Finally, restart the computer.
Note If you modify the registry incorrectly, you can cause serious problems. Therefore, follow these steps carefully. For additional protection, back up the registry before you modify it. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
Best Regards
Zunhui
Hello Zunhui Han,
First of all thanks for replying, the basic steps you've mentioned are the first steps I've tried with no luck
the computers that cannot access the NAS sharing, can access each others drive, so network discovery is not the issue.
- I've checked services, all the services needed are set to automatic.
- Local Policies - Security Options is set to Send LM & NTLM-use NTLMv2 session security if negotiated.
- On the Advanced TCP/IP settings windows, “WINS” tab, NetBIOS over TCP/IP is enabled.
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing hardwareID and Store keys are deleted.
- 4(TCP/IPv4) Reliable multi-cast protocol is installed.
These are all the steps I've checked but still no luck.
Still get Error Code: 0x80070035 when I try to access the NAS drive.
I have 2 laptops and 3 desktops, they are all visible to each other and can access each other's shared drives without any problem.
With 1 laptop and 1 desktop (windrunning on ows 10 pro full version) I can access the NAS drive.
With the other laptop and 2 desktops (running on windows 10 Tiny IoT Enterprise LTSC , 21H2) is the NAS drive visible but I get the Error code 0x80070035
I hope now you've got a bit more info,
Kind regards,
Erdinç
Clear out any cached passwords you have on the client side.
Is this a domain network? If not, and it is workgroup, are you using the same username on the server and client side for logins?
When a workgroup PC authenticates, if you dont specifiy the domain\ in the login then it can actually try to login as a user account on the remote server.
Such that if the computer had user1, and the server had user1… Even though they have separate workgroups, if you had the same password on both computer and server… you’d be able to login between the devices simply as user1 without specifiying the domain/workgroup at all.
The reason that I raise this… Is to query if you are using workgroups, and if so, do both devices have an identical user account and is that account using the same password.
If you have identical accounts but wish to maintain separate passwords, then you must specify the hostname\user when logging in instead of just username on its own.
Also it appears that you’re using a Public network profile. Is this server side? Why?
Servers should be on domain/private network profiles. Public is intended largely for laptops on untrustworthy shared networks like airports/cafe/hotels etc.
When you have your device on a Public profile a whole bunch of services are shut down.
Your screen shots show EVERYONE permissions, its not unusual to have this at the network level as a bunch of dodgy applications dont handle it if you try to be more restrictive. Also share permissions are a rather legacy thing from back in the FAT days.
But you need to be mindful of what your actual filesystem level permissions are on those shares. Do NOT use EVERYONE permissions at the filesystem level. Its just begging for a crypto to come and fuck up your data.
You have displayed the Network Share Permissions, in the RDP session look at the Folder Permissions to make sure everyone has access.
If you have connected previously to the Server (ie with another mapped driive) it may be trying to connect using a different Username Password