Samba share windows 7 no password

Yes No. Sorry this didn't help. Thanks for your feedback. I have the same question 4. Report abuse. Details required :. Cancel Submit. Hi Nitin, Thank you for posting your query in Microsoft Community. To troubleshoot this issue, please refer to the following steps: First, if any firewall or anti-virus program is installed, please disable it: Step 1: Change Workgroup settings: 1.

Please make sure these machines are in the same workgroup: To change workgroup settings, please refer to the following steps: 1. If the issue persists, please refer to step 2: Step 2: Advanced Share Permission 1. View and connect to available wireless networks Share files with someone File sharing essentials Sharing files using the Public folders Hope this information is helpful.

I am running Samba 4. The client machine is running Windows 10, version , build Anyone have any ideas of what else I can try? It could be the Windows 10 machine is checking the password against the wrong system, i. It has done that for me at times. To specify where the check the password the server can be put before the username separated with a backslash. Just gave it a whirl, and I get the same system error I've also tried using both my client and my server as the domain for the username in the Map network drive wizard with the same results.

Have you looked at the logs on the samba server? You can try turning up the samba server's log verbosity and see if that produces anything useful in the logs. My gut feel, however, is that somehow your password is either not getting into the 'net' command correctly, or windows is doing something funny with it before it sends it to the samba server.

Are you able to capture the traffic with tcpdump or wireshark and then post the. I could look at the network traffic for you to see if there is something strange there. I'm having trouble posting a link to the full pcap apparently they can't verify my account , but I'll try to make that available shortly as well. Thanks for sending the logs. Also, is there a line that says something like "client ntlm auth"? If you are unable to for the windows machine to NTLMV2 for whatever reason, you might need to disable the 'client ntlmv2 auth' and turn on the 'client ntlm auth' in order to make it work see below.

This parameter determines whether or not smbclient 8 will attempt to authenticate itself to servers using the NTLMv2 encrypted password response.

Similarly, if enabled, NTLMv1, client lanman auth and client plaintext auth authentication will be disabled. Supposedly it's not a bug on the mask when you try to re-install samba on the samba-dc-ad. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 5 years, 7 months ago. Active 3 years, 7 months ago.

Viewed k times. What I need: Simple samba config for file server without password and full read write for everyone. History: I'm making a server to host files for my home. Improve this question. Community Bot 1. Possibly related to serverfault. Add a comment. Active Oldest Votes. Yes, Samba can be a pain. This means that the password set with smbpasswd should match that of the user's password on the Windows client.

The password may not be the empty string at least I have not found a way to force this while also passing the authentication step. File shares are often group-oriented group of users need access to the same data.

This is why I prefer to implement shares by groups not by users like in most documentation :. Note the smbmedia. This means that anyone in the group smbmedia may access this share. I have create mode and directory mode in there, but its mostly for good measure and redundant.

Because this share is writable, the default umask will apply. I like to override this because I want ensure that new files are owned by the group smbmedia and the user should be set to the user who created the file for record keeping. Set the sticky bit to ensure new directories keep the same ACLs which we'll set next. The group stick bit will therefore only work for new directories at 1 level below the base level of the share.

This means that newly created directories at level 1 will have the ACLs applied minus the group sticky bit, so that level 2 directories will assume the primary group permissions of the user that created the new directory, and not necessarily the "shared" group permissions something like this.

There are two ways to deal with this: One way it to use something like inotify to watch for new directories and apply the group sticky bit on newly created directories recursively. Now you can be sure that new files will be created with the correct permissions so that they can be seen and changed by smb client users. This will allow anyone in the smbmedia group to change files owned by other people, however. You can adjust the ACLs accordingly. Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.