Here are some good troubleshooting steps, shamelessly copied from ServerFault:

1. Maybe your Windows host is prepending your username with the wrong domain name. From the Windows machine, try to login using localhost\simon as the username
2. Issue sudo pdbedit -L (must run as root) and check if user simon is listed. If so, set a trivial password (you can change it later) using smbpasswd simon
3. If user simon is not listed, try to recreate it issuing smbpasswd -a simon
4. If it does not work, delete the passwd file (it is named passwd.tdb; for reference, it is found under /var/lib/samba/private/). Then, recreate your user issuing smbpasswd -a simon
5. If it still not working, try to use the root account issuing smbpasswd -a root and check if you can login using the root user. Note: this is only a try. After having done with it, you must delete root's entry issuing smbpasswd -x root
6. Your last resort is to increase the verbosity of logging and see if you can find clues there. For authentication attempts, edit or add the following line on your smb.conf: log level = 2 winbind:5, check the logs with something like tail -f /var/log/samba/log* and try to login.

Hope some of it helps.

Ran into this issue with a new Windows 11 setup. Tried some different suggestions that did not work. Finally solved it without enabling Smb1 by manually adding the credentials to the credential manager:

1. Run (ctrl+r): control /name Microsoft.CredentialManager
2. Select Windows references.
3. Add Windows reference.
4. Enter your remote path with credentials.

To access the samba share, please pay attention to:

1. You had to create a system user with the same username. In this case, please issue the following command: useradd -s /sbin/nologin benjamin
2. If you are using a SELINUX-enabled system (eg: CentOS), try to temporarily disable it issuing setenforce 0

EDIT: as the problem persists, try the following:

1. maybe your Windows host is prepending your username with the wrong domain name. From the Windows machine, try to login using localhost\benjamin as the username
2. issue pdbedit -L and check if user benjamin is listed. If so, set a trivial password (you can change it later) using smbpasswd benjamin
3. if user benjamin is not listed, try to recreate it issuing smbpasswd -a benjamin
4. if it does not work, delete the passwd file (it is named passwd.tdb; for reference, in a CentOS 6.x system it is found under /var/lib/samba/private/). Then, recreate your user issuing smbpasswd -a benjamin
5. if it still not working, try to use the root account issuing smbpasswd -a root and check if you can login using the root user. Note: this is only a try. After having done with it, you must delete root's entry issuing smbpasswd -x root
6. Your last resort is to increase the verbosity of logging and see if you can find clues there. For authentication attempts, edit or add the following line on your smb.conf log level = 2 winbind:5, check the logs with something like tail -f /var/log/samba/log* and try to login.

By doing some trial and error found the following:

In CMD:

E:\>NET USE Z: \\x.x.x.x\sharename youruserpassword /PERSISTENT:NO /USER:yourusername
Error de sistema 67.

Upgraded Samba to version 4.19.4, I had a look on man smb.conf and made the following changes (since it was configured for SMB2):

[global]

workgroup = BLUECROSS
client min protocol = SMB3
client max protocol = SMB3
client smb encrypt = required
client signing = required
server min protocol = SMB3
server max protocol = SMB3
ntlm auth = ntlmv2-only

It works now:

E:\>NET USE Z: \\x.x.x.x\sharename youruserpassword /PERSISTENT:NO /USER:yourusername
Se ha completado el comando correctamente.


E:\>DIR Z:
 El volumen de la unidad Z es sharename
 El número de serie del volumen es: 3C72-71F2

 Directorio de Z:\

12/01/2024  10:28 p. m.    <DIR>          .
12/01/2024  10:28 p. m.    <DIR>          ..
14/12/2023  09:49 p. m.    <DIR>          Documents
14/12/2023  10:34 p. m.    <DIR>          Downloads
10/01/2024  12:09 a. m.    <DIR>          Music
07/03/2022  01:06 p. m.    <DIR>          Pictures
12/05/2023  07:43 p. m.    <DIR>          Videos
               0 archivos              0 bytes
               7 dirs  537,922,781,184 bytes libres

E:\>NET USE Z: /DELETE
Z: se ha eliminado.

Oher Settings on your Win11 that might help, I had these settings beforehand:

Configuration, Network & internet, Properties: Private (not public) Configuration, Network & internet, Avanced network settings, Advanced Shared settings: All Networks: 128 bit encryption

For Fedora 25, I am not familiar with fedora version numbers but I am with RHEL/Centos 7.x If you have selinux enabled by default, you might try as root setenforce 0 to temporarily put selinux into permissive mode until next reboot, see if this allows samba access to work. If so then it's a selinux problem, and in RHEL/Centos there is etc/samba/smb.conf.example which explains the samba related selinux commands needed to allow samba shares to work with selinux set to enforcing.

For your version of fedora, I would work off the /etc/samba/smb.conf.example.

for reference here is my working smb.conf from an older version of samba showing what i believe is the minimum required to get it to work. If you go too restrictive with settings then you can prevent a successful connection so sometimes it's best to not specify which generally means allow for all.

In your [myshare] take out allow hosts and valid users. Once samba working then consider adding restrictive measures like these as necessary.

[global]
#       min protocol = SMB1 needed for winxp
        min protocol = SMB1
#       max protocol SMB2 needed to work with win10, unspecified for this older version of samba is smb1.
        max protocol = SMB2 
        security = user
        passdb backend = tdbsam
#       map to guest = never prevents popup option, bad user allows popup in windows
        map to guest = Bad User

[data]
    path = /data
    read only = No
#   guest ok = no
#   create mask = 660
#   directory mask = 770

with guest ok = no, and map to guest bad user, will allow popup in windows giving anyone a chance to enter correct linux username and pw. map to guest never prevents popup, meaning the username of the windows user has to be the same as a valid local user in linux, per security=user. You likely do not need min/max protocol specified, I do in samba version 3.6. I don't know what verion of samba u have in fedora 25, if it's samba 3.x then try specifying the min/max protocol.

don't forget to do smbpasswd -a <username on your linux system.

I have problem to connect from Windows 11 to my sambashares on Ubuntu 22.04.3 LTS
but to my sambashare on Linux raspberrypi 6.1.21-v8+ the connection works.

When I tested with Windows 10 I was able to connect both Ubuntu’s and RaspberryPi’s samba shares without problems.
Raspberry Pi has Samba version 4.13.13-Debian installed and Ubuntu has Samba version 4.18.6 installed.

Can some help me with this issue?

In order to enable "guest" access from Windows 11 Enterprise you have to do the following:

1. Open Group Policy, go to Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation, double click "Enable Insecure Guest Logons" and choose "Enabled", click OK.

2. Open Local Security Policy, go to Local Policies -> Security Options and find

• Microsoft Network Client: Digitally Sign Communications (always)
• Microsoft Network Client: Digitally Sign Communications (if server agrees)

Set both of these to "Disabled".