samba - Sep 2025 - Hyper-V delay with Samba

Setup:

  * SMB client: Windows 11 Pro x64

  * SMB server: Arch Linux VM in Hyper-V under the above Windows, using
    the default Hyper-V network adapter

Samba version: 4.22.4

`/etc/samba/smb.conf`:

    [global]
            map to guest = bad user
            guest account = felix

    [share]
            path = /home/felix/tmp
            read only = no
            guest ok = yes

When I connect to the share from Windows, it takes about a minute, until
there is the message that the password is wrong, and I?m asked for
credentials:

    > net use \\hv-linux.local\share
    The password is invalid for \\hv-linux.local\share.

    Enter the user name for 'hv-linux.local':

*What could be the reason for this extreme delay?*

What I tried:

  * Running Samba on a second network adapter connected to a Hyper-V
    virtual internal switch: same issue

  * Sustituting Sambe with KSMBD: [same issue][1]

  * Samba in WSL2: The issue does not exist

I also would like to understand why credentials are even needed with
`guest ok = yes`.

[1]: https://github.com/namjaejeon/ksmbd/issues/511

On Sat, 13 Sep 2025 22:55:42 +0800
"Felix E. Klee via samba" <samba at lists.samba.org> wrote:
> Setup:
> 
>   * SMB client: Windows 11 Pro x64
> 
>   * SMB server: Arch Linux VM in Hyper-V under the above Windows,
> using the default Hyper-V network adapter
> 
> Samba version: 4.22.4
> 
> `/etc/samba/smb.conf`:
> 
>     [global]
>             map to guest = bad user
>             guest account = felix
> 
>     [share]
>             path = /home/felix/tmp
>             read only = no
>             guest ok = yes
> 
> When I connect to the share from Windows, it takes about a minute,
> until there is the message that the password is wrong, and I?m asked
> for credentials:
> 
>     > net use \\hv-linux.local\share
>     The password is invalid for \\hv-linux.local\share.
> 
>     Enter the user name for 'hv-linux.local':
> 
> *What could be the reason for this extreme delay?*
> 
> What I tried:
> 
>   * Running Samba on a second network adapter connected to a Hyper-V
>     virtual internal switch: same issue
> 
>   * Sustituting Sambe with KSMBD: [same issue][1]
> 
>   * Samba in WSL2: The issue does not exist
> 
> I also would like to understand why credentials are even needed with
> `guest ok = yes`.
> 
> [1]: https://github.com/namjaejeon/ksmbd/issues/511
> 
It could be because Windows 11 pro has guest access turned off by
default.

Rowland