microsoft / microsoft/WSL

can not map \\wsl$\xxx\xxx path to a network drive

Open
#4,657 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\

See our contributing instructions for assistance.

Please fill out the below information:

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    10.0.19013.1
    wsl2 with ubuntu 18.04

  • What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

  1. in explorer, mapping a network driver with path \wsl$\Ubuntu-18.04 succeeded,
  2. in console, "dir \wsl$\Ubuntu-18.04\home" can display directory correctly.
  3. in explorer mapping a network driver with path \wsl$\Ubuntu-18.04\home failed, with error windows can not access \wsl$\Ubuntu-18.04\home
  • What's wrong / what should be happening instead:
    mapping \wsl$\Ubuntu-18.04\home a network driver should succeed

  • Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

  • For WSL launch issues, please collect detailed logs.

Contributor guide

Open the contributing guide

First steps

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

Research direction

Start by reproducing the Explorer network-drive mapping steps for \wsl$\Ubuntu-18.04 and the working console dir command. Review the WSL contributing instructions for detailed logs, since no source file or test is named. Done means mapping the /home path succeeds as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.