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

Open

#604 opened on Jul 24, 2025 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 42/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Active
Tech stack: docker, powershell
Domain: networking, operating-systems

Research direction

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.

Written by the indexing model from the issue text.

Description

bug triage

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

Mount a SmbGlobalMapping using using https://learn.microsoft.com/en-us/powershell/module/smbshare/new-smbglobalmapping?view=windowsserver2019-ps
Start a docker with a -v option
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

Dominant language: PowerShell
Stars: 551
Forks: 76
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.