How to access network mounted drive on Windows Linux Subsystem?












33














I have a samba drive which is mounted on my local windows computer.



I have a "/mnt/c" drive in WLS ("Windows 10 bash"), but no "/mnt/z".



Is there a way to access it somehow? Can I remount it in WLS?










share|improve this question


















  • 3




    There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
    – Nelson
    Jan 25 '17 at 1:03
















33














I have a samba drive which is mounted on my local windows computer.



I have a "/mnt/c" drive in WLS ("Windows 10 bash"), but no "/mnt/z".



Is there a way to access it somehow? Can I remount it in WLS?










share|improve this question


















  • 3




    There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
    – Nelson
    Jan 25 '17 at 1:03














33












33








33


10





I have a samba drive which is mounted on my local windows computer.



I have a "/mnt/c" drive in WLS ("Windows 10 bash"), but no "/mnt/z".



Is there a way to access it somehow? Can I remount it in WLS?










share|improve this question













I have a samba drive which is mounted on my local windows computer.



I have a "/mnt/c" drive in WLS ("Windows 10 bash"), but no "/mnt/z".



Is there a way to access it somehow? Can I remount it in WLS?







windows-subsystem-for-linux






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 27 '16 at 4:14









Charles Shiller

281136




281136








  • 3




    There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
    – Nelson
    Jan 25 '17 at 1:03














  • 3




    There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
    – Nelson
    Jan 25 '17 at 1:03








3




3




There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
– Nelson
Jan 25 '17 at 1:03




There's discussion about this feature at Microsoft Developer Feedback wpdev.uservoice.com/forums/…
– Nelson
Jan 25 '17 at 1:03










3 Answers
3






active

oldest

votes


















19














[Update -- apparently this feature is available in build 16176. I haven't tried it yet.]



No, though there may be some trick I haven't discovered. Windows Subsystem for Linux does not mount network drives. A Microsoft employee says here (in a comment):




We only “mount” fixed drives at this time. USB/removable/network drives are not handled at this time. This capability is on our backlog, but it’s not on the cards anytime soon.




So don't hold your breath.



I attempted to work around it by using a symbolic link, like this:



c:> mklink /d \some_serversome_share c:somedirectory


The link works just fine in "normal" Windows (cmd.exe, PowerShell, file explorer, etc.), but is invisible to WSL:



$ ls -ld /mnt/c/some/directory
/mnt/c/some/directory not found


For my own use, this limitation is a show-stopper. I have things on network drives that I'm not willing to move. There are alternatives; I'm using Cygwin.






share|improve this answer























  • Agreed, this is a showstopper for me too - I just installed msys2 for this.
    – Ela782
    Apr 7 '17 at 17:55






  • 3




    Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
    – bleater
    May 3 '17 at 0:34










  • the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
    – masterxilo
    Dec 5 at 22:10



















50














from the link bleater posted




Mounting DrvFs



In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:



$ sudo mkdir /mnt/d
$ sudo mount -t drvfs D: /mnt/d


Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:



$ sudo umount /mnt/d


Mounting network locations



When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it's also possible to mount them directly using a UNC path:



$ sudo mkdir /mnt/share
$ sudo mount -t drvfs '\servershare' /mnt/share


Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don't surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\server\share).



WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.







share|improve this answer























  • totally worked for my "bash for windows 10"! Thank you so much!
    – Ying Zhang
    Jan 26 at 0:55










  • The correct answer should be changed to this one as it directly answers the question.
    – Tomek
    Jan 31 at 2:43










  • You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
    – FractalSpace
    Feb 27 at 21:39








  • 2




    I don't have windows insider build and it's working for me
    – gman
    Feb 28 at 1:14










  • That is completely awesome.
    – Erik
    Mar 24 at 2:41



















0














There are (at least) two ways to use Bash in Windows:




  1. The Bash that comes with WLS (when installing Linux on Windows 10 from Windows Store or other sources)


  2. Git-Bash on Windows


Git-Bash has access to network folders (install git-bash > go to the network folder > right-click > "Git Bash Here" > run pwd to see the path).



If you have to use the WLS version of bash, then you can call Git-Bash from WLS bash as follows:



WLS_Bash_Shell:$ /mnt/c/Program Files/Git/bin/bash.exe ScriptThatUsesNetworkFolders.sh





share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1128634%2fhow-to-access-network-mounted-drive-on-windows-linux-subsystem%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    19














    [Update -- apparently this feature is available in build 16176. I haven't tried it yet.]



    No, though there may be some trick I haven't discovered. Windows Subsystem for Linux does not mount network drives. A Microsoft employee says here (in a comment):




    We only “mount” fixed drives at this time. USB/removable/network drives are not handled at this time. This capability is on our backlog, but it’s not on the cards anytime soon.




    So don't hold your breath.



    I attempted to work around it by using a symbolic link, like this:



    c:> mklink /d \some_serversome_share c:somedirectory


    The link works just fine in "normal" Windows (cmd.exe, PowerShell, file explorer, etc.), but is invisible to WSL:



    $ ls -ld /mnt/c/some/directory
    /mnt/c/some/directory not found


    For my own use, this limitation is a show-stopper. I have things on network drives that I'm not willing to move. There are alternatives; I'm using Cygwin.






    share|improve this answer























    • Agreed, this is a showstopper for me too - I just installed msys2 for this.
      – Ela782
      Apr 7 '17 at 17:55






    • 3




      Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
      – bleater
      May 3 '17 at 0:34










    • the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
      – masterxilo
      Dec 5 at 22:10
















    19














    [Update -- apparently this feature is available in build 16176. I haven't tried it yet.]



    No, though there may be some trick I haven't discovered. Windows Subsystem for Linux does not mount network drives. A Microsoft employee says here (in a comment):




    We only “mount” fixed drives at this time. USB/removable/network drives are not handled at this time. This capability is on our backlog, but it’s not on the cards anytime soon.




    So don't hold your breath.



    I attempted to work around it by using a symbolic link, like this:



    c:> mklink /d \some_serversome_share c:somedirectory


    The link works just fine in "normal" Windows (cmd.exe, PowerShell, file explorer, etc.), but is invisible to WSL:



    $ ls -ld /mnt/c/some/directory
    /mnt/c/some/directory not found


    For my own use, this limitation is a show-stopper. I have things on network drives that I'm not willing to move. There are alternatives; I'm using Cygwin.






    share|improve this answer























    • Agreed, this is a showstopper for me too - I just installed msys2 for this.
      – Ela782
      Apr 7 '17 at 17:55






    • 3




      Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
      – bleater
      May 3 '17 at 0:34










    • the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
      – masterxilo
      Dec 5 at 22:10














    19












    19








    19






    [Update -- apparently this feature is available in build 16176. I haven't tried it yet.]



    No, though there may be some trick I haven't discovered. Windows Subsystem for Linux does not mount network drives. A Microsoft employee says here (in a comment):




    We only “mount” fixed drives at this time. USB/removable/network drives are not handled at this time. This capability is on our backlog, but it’s not on the cards anytime soon.




    So don't hold your breath.



    I attempted to work around it by using a symbolic link, like this:



    c:> mklink /d \some_serversome_share c:somedirectory


    The link works just fine in "normal" Windows (cmd.exe, PowerShell, file explorer, etc.), but is invisible to WSL:



    $ ls -ld /mnt/c/some/directory
    /mnt/c/some/directory not found


    For my own use, this limitation is a show-stopper. I have things on network drives that I'm not willing to move. There are alternatives; I'm using Cygwin.






    share|improve this answer














    [Update -- apparently this feature is available in build 16176. I haven't tried it yet.]



    No, though there may be some trick I haven't discovered. Windows Subsystem for Linux does not mount network drives. A Microsoft employee says here (in a comment):




    We only “mount” fixed drives at this time. USB/removable/network drives are not handled at this time. This capability is on our backlog, but it’s not on the cards anytime soon.




    So don't hold your breath.



    I attempted to work around it by using a symbolic link, like this:



    c:> mklink /d \some_serversome_share c:somedirectory


    The link works just fine in "normal" Windows (cmd.exe, PowerShell, file explorer, etc.), but is invisible to WSL:



    $ ls -ld /mnt/c/some/directory
    /mnt/c/some/directory not found


    For my own use, this limitation is a show-stopper. I have things on network drives that I'm not willing to move. There are alternatives; I'm using Cygwin.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 28 '17 at 15:09

























    answered Oct 18 '16 at 21:43









    Joseph Thvedt

    40735




    40735












    • Agreed, this is a showstopper for me too - I just installed msys2 for this.
      – Ela782
      Apr 7 '17 at 17:55






    • 3




      Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
      – bleater
      May 3 '17 at 0:34










    • the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
      – masterxilo
      Dec 5 at 22:10


















    • Agreed, this is a showstopper for me too - I just installed msys2 for this.
      – Ela782
      Apr 7 '17 at 17:55






    • 3




      Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
      – bleater
      May 3 '17 at 0:34










    • the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
      – masterxilo
      Dec 5 at 22:10
















    Agreed, this is a showstopper for me too - I just installed msys2 for this.
    – Ela782
    Apr 7 '17 at 17:55




    Agreed, this is a showstopper for me too - I just installed msys2 for this.
    – Ela782
    Apr 7 '17 at 17:55




    3




    3




    Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
    – bleater
    May 3 '17 at 0:34




    Details: blogs.msdn.microsoft.com/wsl/2017/04/18/…
    – bleater
    May 3 '17 at 0:34












    the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
    – masterxilo
    Dec 5 at 22:10




    the order of your arguments to mklink is wrong - it should be linkname target, not target linkname
    – masterxilo
    Dec 5 at 22:10













    50














    from the link bleater posted




    Mounting DrvFs



    In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:



    $ sudo mkdir /mnt/d
    $ sudo mount -t drvfs D: /mnt/d


    Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:



    $ sudo umount /mnt/d


    Mounting network locations



    When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it's also possible to mount them directly using a UNC path:



    $ sudo mkdir /mnt/share
    $ sudo mount -t drvfs '\servershare' /mnt/share


    Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don't surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\server\share).



    WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.







    share|improve this answer























    • totally worked for my "bash for windows 10"! Thank you so much!
      – Ying Zhang
      Jan 26 at 0:55










    • The correct answer should be changed to this one as it directly answers the question.
      – Tomek
      Jan 31 at 2:43










    • You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
      – FractalSpace
      Feb 27 at 21:39








    • 2




      I don't have windows insider build and it's working for me
      – gman
      Feb 28 at 1:14










    • That is completely awesome.
      – Erik
      Mar 24 at 2:41
















    50














    from the link bleater posted




    Mounting DrvFs



    In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:



    $ sudo mkdir /mnt/d
    $ sudo mount -t drvfs D: /mnt/d


    Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:



    $ sudo umount /mnt/d


    Mounting network locations



    When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it's also possible to mount them directly using a UNC path:



    $ sudo mkdir /mnt/share
    $ sudo mount -t drvfs '\servershare' /mnt/share


    Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don't surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\server\share).



    WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.







    share|improve this answer























    • totally worked for my "bash for windows 10"! Thank you so much!
      – Ying Zhang
      Jan 26 at 0:55










    • The correct answer should be changed to this one as it directly answers the question.
      – Tomek
      Jan 31 at 2:43










    • You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
      – FractalSpace
      Feb 27 at 21:39








    • 2




      I don't have windows insider build and it's working for me
      – gman
      Feb 28 at 1:14










    • That is completely awesome.
      – Erik
      Mar 24 at 2:41














    50












    50








    50






    from the link bleater posted




    Mounting DrvFs



    In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:



    $ sudo mkdir /mnt/d
    $ sudo mount -t drvfs D: /mnt/d


    Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:



    $ sudo umount /mnt/d


    Mounting network locations



    When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it's also possible to mount them directly using a UNC path:



    $ sudo mkdir /mnt/share
    $ sudo mount -t drvfs '\servershare' /mnt/share


    Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don't surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\server\share).



    WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.







    share|improve this answer














    from the link bleater posted




    Mounting DrvFs



    In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:



    $ sudo mkdir /mnt/d
    $ sudo mount -t drvfs D: /mnt/d


    Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:



    $ sudo umount /mnt/d


    Mounting network locations



    When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it's also possible to mount them directly using a UNC path:



    $ sudo mkdir /mnt/share
    $ sudo mount -t drvfs '\servershare' /mnt/share


    Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don't surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\server\share).



    WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.








    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 23 '17 at 10:47









    Bob

    45.4k20137172




    45.4k20137172










    answered Oct 23 '17 at 10:20









    gman

    1,21821217




    1,21821217












    • totally worked for my "bash for windows 10"! Thank you so much!
      – Ying Zhang
      Jan 26 at 0:55










    • The correct answer should be changed to this one as it directly answers the question.
      – Tomek
      Jan 31 at 2:43










    • You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
      – FractalSpace
      Feb 27 at 21:39








    • 2




      I don't have windows insider build and it's working for me
      – gman
      Feb 28 at 1:14










    • That is completely awesome.
      – Erik
      Mar 24 at 2:41


















    • totally worked for my "bash for windows 10"! Thank you so much!
      – Ying Zhang
      Jan 26 at 0:55










    • The correct answer should be changed to this one as it directly answers the question.
      – Tomek
      Jan 31 at 2:43










    • You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
      – FractalSpace
      Feb 27 at 21:39








    • 2




      I don't have windows insider build and it's working for me
      – gman
      Feb 28 at 1:14










    • That is completely awesome.
      – Erik
      Mar 24 at 2:41
















    totally worked for my "bash for windows 10"! Thank you so much!
    – Ying Zhang
    Jan 26 at 0:55




    totally worked for my "bash for windows 10"! Thank you so much!
    – Ying Zhang
    Jan 26 at 0:55












    The correct answer should be changed to this one as it directly answers the question.
    – Tomek
    Jan 31 at 2:43




    The correct answer should be changed to this one as it directly answers the question.
    – Tomek
    Jan 31 at 2:43












    You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
    – FractalSpace
    Feb 27 at 21:39






    You need "Windows Insider build" to get DrvFs. -1 (not actually down voting)
    – FractalSpace
    Feb 27 at 21:39






    2




    2




    I don't have windows insider build and it's working for me
    – gman
    Feb 28 at 1:14




    I don't have windows insider build and it's working for me
    – gman
    Feb 28 at 1:14












    That is completely awesome.
    – Erik
    Mar 24 at 2:41




    That is completely awesome.
    – Erik
    Mar 24 at 2:41











    0














    There are (at least) two ways to use Bash in Windows:




    1. The Bash that comes with WLS (when installing Linux on Windows 10 from Windows Store or other sources)


    2. Git-Bash on Windows


    Git-Bash has access to network folders (install git-bash > go to the network folder > right-click > "Git Bash Here" > run pwd to see the path).



    If you have to use the WLS version of bash, then you can call Git-Bash from WLS bash as follows:



    WLS_Bash_Shell:$ /mnt/c/Program Files/Git/bin/bash.exe ScriptThatUsesNetworkFolders.sh





    share|improve this answer




























      0














      There are (at least) two ways to use Bash in Windows:




      1. The Bash that comes with WLS (when installing Linux on Windows 10 from Windows Store or other sources)


      2. Git-Bash on Windows


      Git-Bash has access to network folders (install git-bash > go to the network folder > right-click > "Git Bash Here" > run pwd to see the path).



      If you have to use the WLS version of bash, then you can call Git-Bash from WLS bash as follows:



      WLS_Bash_Shell:$ /mnt/c/Program Files/Git/bin/bash.exe ScriptThatUsesNetworkFolders.sh





      share|improve this answer


























        0












        0








        0






        There are (at least) two ways to use Bash in Windows:




        1. The Bash that comes with WLS (when installing Linux on Windows 10 from Windows Store or other sources)


        2. Git-Bash on Windows


        Git-Bash has access to network folders (install git-bash > go to the network folder > right-click > "Git Bash Here" > run pwd to see the path).



        If you have to use the WLS version of bash, then you can call Git-Bash from WLS bash as follows:



        WLS_Bash_Shell:$ /mnt/c/Program Files/Git/bin/bash.exe ScriptThatUsesNetworkFolders.sh





        share|improve this answer














        There are (at least) two ways to use Bash in Windows:




        1. The Bash that comes with WLS (when installing Linux on Windows 10 from Windows Store or other sources)


        2. Git-Bash on Windows


        Git-Bash has access to network folders (install git-bash > go to the network folder > right-click > "Git Bash Here" > run pwd to see the path).



        If you have to use the WLS version of bash, then you can call Git-Bash from WLS bash as follows:



        WLS_Bash_Shell:$ /mnt/c/Program Files/Git/bin/bash.exe ScriptThatUsesNetworkFolders.sh






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 11 at 1:27

























        answered Dec 11 at 0:21









        LoMaPh

        1094




        1094






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1128634%2fhow-to-access-network-mounted-drive-on-windows-linux-subsystem%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?