SmbGlobalMapping Username and Domain is set to Null/Null after beeing mounted

Describe the bug
After an SMB Share is mounted using a SmbGlobalMapping (using https://learn.microsoft.com/en-us/powershell/module/smbshare/new-smbglobalmapping?view=windowsserver2019-ps), the initial authentication request does contains the username and domain specified with the -credential option but when the global mapping is used under windows container/docker, it contains NULL/NULL. It does lead to try to establish a session for every file read/write and can also lead to network port exhaustion if the NAS Provider does not support those null/null

To Reproduce

1. Mount a SmbGlobalMapping using using https://learn.microsoft.com/en-us/powershell/module/smbshare/new-smbglobalmapping?view=windowsserver2019-ps
2. Start a docker with a -v option
3. Take some network capture with Wireshark

Expected behavior
We expect authentification token to contains the user given with the -credentials option when mounted the folder

Configuration:

• Windows Server 2019

Start by reproducing the Windows Server 2019 scenario with New-SmbGlobalMapping, a Docker volume mount, and a Wireshark capture. Compare the initial authentication request with requests made through the container; done means the specified username and domain are preserved instead of becoming NULL/NULL and repeated session attempts stop.