Nope. Your server won't understand the credentials from your local PC because the SIDs would be completely different even if you have the same name on both servers.

If you're looking to have a central file space, you can just map the share as a network drive and the auto-login capabilities will take care of your requirement.

To be thorough:

First, create a samba user if you haven't already:

useradd sambauser
smbpasswd -a sambauser

Enter and confirm the password for sambauser.

Change that part of your /etc/samba/smb.conf to this:

[share]
comment = Ubuntu File Server Share
path = /srv/samba/share
valid users = sambauser
browsable = yes
writable = yes
write list = sambauser
create mask = 0755

Make sure that the directory and everything that might be inside has the proper ownership and permissions:

chown -R sambauser:sambauser /srv/samba/share
chmod -R 755 /srv/samba/share

Make sure that you have allowed samba through selinux with this command if it is enabled. If selinux is not enabled then you can skip this part:

chcon -R -t  samba_share_t /srv/samba/share

Lastly, make sure that the ports are open for samba on the firewall.

firewall-cmd --permanent --zone=public --add-port=445/tcp
firewall-cmd --permanent --zone=public --add-port=139/tcp
firewall-cmd --reload
systemctl restart firewalld

If using `iptables:

iptables -A INPUT -p tcp --dport 445 -j ACCEPT
iptables -A INPUT -p tcp --dport 139 -j ACCEPT
iptables-save
iptables-restore

Restart the samba service and then log in with the credentials of sambauser.

I assume that you have a central windows server with central user profiles (active directory). To integrate these workstations you have to mount the user home directories into /home on your linux machines and hook up the active directory into linux.

The keywords that you want to search for are: ldap pam active directory integration. Useful links:

• Ubuntu Active Directory Howto
• Debian LDAP/PAM

note that integrating a windows machine into linux/ldap is generally not recommended (unless you have lots and lots of spare time on your hands). It might work satisfactorily with Samba 4.0. I haven't tried since it provides its own ldap...

Edit: I think I might have misunderstood you. If you want to access a linux samba share from windows simply follow the Ubuntu Samba Server Guide. If you want to login with as $user to the server simply create $user on the server. And set a samba password for the user:

smbpasswd -a $user

the configure the samba server according to your needs. Note: You don't need ldap/kerberos for this kind of setup. It usually helps to use your windows username and password as username/password for the linux user $user. In that case you won't need to configure any passwords on Windows.

I've managed to figure out how to make what I requested work and will post the instructions.

1. First, you need to figure out what the username you need to add is. The easiest way to do this is to first add log level = 2 to smb.conf. Then start and enable the Samba service. Then connect to the Samba server using File Explorer on the Windows PC while logged into the relevant account (you don't have to open any shared directories). Then open the log file found at /var/log/samba/log.<ip address of Windows PC> and the required username will be noted there. You can now set log level to 0 if you want.
2. Create a Linux account for the Samba user using the useradd command (or use an existing one if you prefer). You don't need to worry about passwords with this account but if you create a new account, you may want to block login on it. This account's username doesn't have to be the same as the name noted above but it would be easier if it was. This account's purpose is for the purpose of file permissions and for Linux to determine what files and directories the Windows user is allowed to access.
3. Create a Samba user with the same name as the Linux account in step 2 using the smbpasswd command. Make sure the password assigned to this account is the same as the one used for the Windows account.
4. If the Samba and Windows accounts don't share the same username, you will have to either add !<Samba user> = <Windows user> to smb.conf or add <Samba user> = <Windows user> to smbusers and username map = /etc/samba/smbusers to smb.conf.
5. And that should be it. Be sure to set the valid users = option on any shares you want accessible only by your Windows account.

I recommend to create a dedicated user for that share and specify it in force user(see docs).

Create a user (shareuser for example) and set the owner of everything in the share folder to that user:

adduser --system shareuser
chown -R shareuser /path/to/share

Then add force user and permission mask settings in smb.conf:

[myshare]
path = /path/to/share
writeable = yes
browseable = yes
public = yes
create mask = 0644
directory mask = 0755
force user = shareuser

Note that guest ok is a synonym for public.

You can override stored credentials for shares in Windows via the credential manager.

Under Windows Credentials:

• If the server in question has an entry, delete it.
• Select Add a Windows Credential.
• Enter the server (e.g. \\IP address\Share).
• Enter new desired credentials.

Navigating manually to \\IP address\Share, it will not use the old credentials any more.

I don't know complicated the permissions per user you require but does something like this work for you : https://ubuntuforums.org/showthread.php?t=2453008

In that situation the user created a share of one folder ( /FolderRoot ) with many subfolders with the intent that only some users would have access to each subfolder.

He wanted the parent folder and the whole tree to be read/writeable to only one user ( User1 ) for which I suggested this:

[FolderRoot]
path = /FolderRoot
read only = no
valid users = User1
force user = UserMaster

Then he wanted a subfoler that only User1 and User3 could access. I suggested just creating a different share of that subfolder like this:

[Folder2]
path = /FolderRoot/Folder2
read only = no
valid users = User1, User3
force user = UserMaster

You might want to look at the original posters question to see how applicable his use case is to yours.

As for this specific error message:

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

The problem here is that when a user on Windows first makes contact with a server it automatically passes that users' local login username. If you have a public share it remembers that it took that username successfully. When you try to connect to a private share and don't pass the exact same username and password, it thinks you are trying to access with another name.

Some workarounds:

1) Map the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft account.

• Create a file at /etc/samba/smbusers

• Map the local Linux user to the Windows user by adding the conversion to the file. For example:

luci = [email protected]
john = "John Smith"

• Then add a reference to the map in /etc/samba/smb.conf in the [global] section:

username map = /etc/samba/smbusers

• Finally restart smbd: sudo service smbd restart

2) Make another connection to the Linux server

Windows can address a Linux server in two (three in Win10) different ways. By hostname, by ip address, or by mDNS name (Win10 only):

\\ubuntu\Protected
\\192.168.0.100\Protected
\\ubuntu.local\Protected

Even though all of these point to the same machine, Windows sees them a three separate hosts.

3) Map the "network drive"

When mapping a drive, select the "connect using different credentials" option.