Even with guest=yes, windows still ask for password

[shalak]

Here's my configuration:

  samba:
    image: dperson/samba
    container_name: samba
    network_mode: host
    environment:
      TZ: 'Europe/Warsaw'
      NMBD: true
      GROUPID: 1000
      USERID: 1000
      WORKGROUP: WORKGROUP
    read_only: true
    env_file:
      - samba.env  # contains SMB_PASSWORD
    tmpfs:
      - /tmp
    restart: unless-stopped
    stdin_open: true
    tty: true
    volumes:
      - /srv/storage/install/:/mnt:z
      - /srv/storage/public/:/mnt-public:z
    command: '-s "instalki;/mnt;yes;yes;yes;;;;instalatory" -s "instalki-public;/mnt-public;yes;no;yes;mirek,guest;mirek;mirek,guest;instalatory-publiczne" -s "instalki-rw;/mnt;yes;no;no;mirek" -u "mirek;$$SMB_PASSWORD" -p'

Unfortunately, when I enter \\servername in windows explorer, it immediately asks for password. Even though, it should allow guest access to instalki and instalki-public shares (with instalki-public having guest write pemissions), and only when trying to access instalki-rw it should prompt for password.

I even tried starting the container with only single share via -s "instalki;/mnt;yes;yes;yes" and it still prompted for credentials...

What am I missing?

[shalak]

I made sure, on the windows client, that Enable Insecure Guest Logons it not disabled (also tried to set it explicitly to Enabled), didn't help:

[pakair]

did you enable SMB1 in Windows?

control panel | programs | firewall features | click smb1 from the list (you have to reboot)

Do you have the same WORKGROUP in win and linux?

[shalak]

did you enable SMB1 in Windows?

No, it's extremely unsecure to do so.

Windows is able to create SMB2/3 guest shares without password, so SMB1 cannot be a requirement from protocol point point of view.