Mount cifs of shared windows folder problem












0















I've some issues with a windows share on Ubuntu 14.04 LTS.





  1. Installed cifsutils`:



    sudo apt-get install cifs-utils



  2. Created mountpoint



    sudo mkdir /mnt/temp



  3. Trying to mount a shared folder



    sudo mount -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx



My problem is that the console hangs forever. I've waiting several minutes. If I enter wrong user/password it tells me Permission denied.



Update:



Response from Ubuntu Host computer:



nmap -p -v 445 fileserver -P0


host seems down / Filesharing seems to work though!



Ubuntu client computer (Inside vmware):



nmap -p -v 445 fileserver -P0


Host seems down / Filesharing doesn't work!



Maybe a lead: To autorize the fileshare I have to login on the domain.



Any suggestions?










share|improve this question
















bumped to the homepage by Community 21 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Does dmesg | tail show anything interesting at that point?

    – Jos
    Nov 12 '15 at 14:05











  • CIFS VFS: cifs_mount failed w/return code = -112

    – Fam Wired
    Nov 12 '15 at 14:50











  • I'm not sure about this, because I have to ctrl-break the action to be able to continue.

    – Fam Wired
    Nov 12 '15 at 14:51











  • Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

    – David Foerster
    Nov 13 '15 at 7:35
















0















I've some issues with a windows share on Ubuntu 14.04 LTS.





  1. Installed cifsutils`:



    sudo apt-get install cifs-utils



  2. Created mountpoint



    sudo mkdir /mnt/temp



  3. Trying to mount a shared folder



    sudo mount -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx



My problem is that the console hangs forever. I've waiting several minutes. If I enter wrong user/password it tells me Permission denied.



Update:



Response from Ubuntu Host computer:



nmap -p -v 445 fileserver -P0


host seems down / Filesharing seems to work though!



Ubuntu client computer (Inside vmware):



nmap -p -v 445 fileserver -P0


Host seems down / Filesharing doesn't work!



Maybe a lead: To autorize the fileshare I have to login on the domain.



Any suggestions?










share|improve this question
















bumped to the homepage by Community 21 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Does dmesg | tail show anything interesting at that point?

    – Jos
    Nov 12 '15 at 14:05











  • CIFS VFS: cifs_mount failed w/return code = -112

    – Fam Wired
    Nov 12 '15 at 14:50











  • I'm not sure about this, because I have to ctrl-break the action to be able to continue.

    – Fam Wired
    Nov 12 '15 at 14:51











  • Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

    – David Foerster
    Nov 13 '15 at 7:35














0












0








0








I've some issues with a windows share on Ubuntu 14.04 LTS.





  1. Installed cifsutils`:



    sudo apt-get install cifs-utils



  2. Created mountpoint



    sudo mkdir /mnt/temp



  3. Trying to mount a shared folder



    sudo mount -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx



My problem is that the console hangs forever. I've waiting several minutes. If I enter wrong user/password it tells me Permission denied.



Update:



Response from Ubuntu Host computer:



nmap -p -v 445 fileserver -P0


host seems down / Filesharing seems to work though!



Ubuntu client computer (Inside vmware):



nmap -p -v 445 fileserver -P0


Host seems down / Filesharing doesn't work!



Maybe a lead: To autorize the fileshare I have to login on the domain.



Any suggestions?










share|improve this question
















I've some issues with a windows share on Ubuntu 14.04 LTS.





  1. Installed cifsutils`:



    sudo apt-get install cifs-utils



  2. Created mountpoint



    sudo mkdir /mnt/temp



  3. Trying to mount a shared folder



    sudo mount -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx



My problem is that the console hangs forever. I've waiting several minutes. If I enter wrong user/password it tells me Permission denied.



Update:



Response from Ubuntu Host computer:



nmap -p -v 445 fileserver -P0


host seems down / Filesharing seems to work though!



Ubuntu client computer (Inside vmware):



nmap -p -v 445 fileserver -P0


Host seems down / Filesharing doesn't work!



Maybe a lead: To autorize the fileshare I have to login on the domain.



Any suggestions?







mount shared-folders cifs smb






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 16 '15 at 8:33







Fam Wired

















asked Nov 12 '15 at 13:56









Fam WiredFam Wired

113




113





bumped to the homepage by Community 21 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 21 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Does dmesg | tail show anything interesting at that point?

    – Jos
    Nov 12 '15 at 14:05











  • CIFS VFS: cifs_mount failed w/return code = -112

    – Fam Wired
    Nov 12 '15 at 14:50











  • I'm not sure about this, because I have to ctrl-break the action to be able to continue.

    – Fam Wired
    Nov 12 '15 at 14:51











  • Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

    – David Foerster
    Nov 13 '15 at 7:35



















  • Does dmesg | tail show anything interesting at that point?

    – Jos
    Nov 12 '15 at 14:05











  • CIFS VFS: cifs_mount failed w/return code = -112

    – Fam Wired
    Nov 12 '15 at 14:50











  • I'm not sure about this, because I have to ctrl-break the action to be able to continue.

    – Fam Wired
    Nov 12 '15 at 14:51











  • Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

    – David Foerster
    Nov 13 '15 at 7:35

















Does dmesg | tail show anything interesting at that point?

– Jos
Nov 12 '15 at 14:05





Does dmesg | tail show anything interesting at that point?

– Jos
Nov 12 '15 at 14:05













CIFS VFS: cifs_mount failed w/return code = -112

– Fam Wired
Nov 12 '15 at 14:50





CIFS VFS: cifs_mount failed w/return code = -112

– Fam Wired
Nov 12 '15 at 14:50













I'm not sure about this, because I have to ctrl-break the action to be able to continue.

– Fam Wired
Nov 12 '15 at 14:51





I'm not sure about this, because I have to ctrl-break the action to be able to continue.

– Fam Wired
Nov 12 '15 at 14:51













Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

– David Foerster
Nov 13 '15 at 7:35





Please edit your question, if you want to add information. Especially file or program output listings (with the help of the {} button in the editor toolbar) are much more readable there and overall it's best to have everything relevant in one place. Also, comments may be deleted for various reasons.

– David Foerster
Nov 13 '15 at 7:35










3 Answers
3






active

oldest

votes


















0














This is firewall issue for me . Install nmap on your ubuntu box with apt-get install nmap and run nmap -p 445 fileserver to see if the samba port is blocked by firewall or not.



Other way is to put -v sudo mount -v -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx
to see the verbose message from the mounting.



Hope it helps






share|improve this answer
























  • Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

    – Fam Wired
    Nov 12 '15 at 14:37











  • I think you have right about the firewall. Do you know how to open the port?

    – Fam Wired
    Nov 12 '15 at 14:38











  • So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

    – Nikolay Nikolov
    Nov 12 '15 at 14:39











  • If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

    – Nikolay Nikolov
    Nov 12 '15 at 14:40











  • It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

    – Fam Wired
    Nov 12 '15 at 14:53



















0














Another possibility:



If you are using a standard VMWare Network-Configuration for that Virtual machine and following the documentation at http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-4B9B4A82-D0F7-4939-BD7B-B6BF92FF7350.html




In a typical configuration, the New Virtual Machine wizard sets up NAT
for the virtual machine. You must select the custom configuration
option to configure bridged networking or host-only networking. The
wizard connects the virtual machine to the appropriate virtual
network.




Check out the VM's Network-Configuration and switch to bridged networking so that the VM has access to the same network-resources as your host machine.



Hope it helps.



NOTE: It was intended to be a comment, but I cannot do that yet :)






share|improve this answer
























  • Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

    – Fam Wired
    Nov 16 '15 at 9:04











  • Your solution was going to be my next answer :-D Glad you sorted this out.

    – Eduardo López
    Nov 16 '15 at 9:39



















0














Finally I got it to work.



I used the ip-address (192.168.1.11) instead of fileserver.



When ping:ing the fileserver name on the client I got ping response from another ip/computer (192.168.1.16) than I got from the host computer (192.168.1.11) !



Don't know why the dns name was linked to wrong ip on the client computer?






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f697193%2fmount-cifs-of-shared-windows-folder-problem%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









    0














    This is firewall issue for me . Install nmap on your ubuntu box with apt-get install nmap and run nmap -p 445 fileserver to see if the samba port is blocked by firewall or not.



    Other way is to put -v sudo mount -v -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx
    to see the verbose message from the mounting.



    Hope it helps






    share|improve this answer
























    • Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

      – Fam Wired
      Nov 12 '15 at 14:37











    • I think you have right about the firewall. Do you know how to open the port?

      – Fam Wired
      Nov 12 '15 at 14:38











    • So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

      – Nikolay Nikolov
      Nov 12 '15 at 14:39











    • If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

      – Nikolay Nikolov
      Nov 12 '15 at 14:40











    • It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

      – Fam Wired
      Nov 12 '15 at 14:53
















    0














    This is firewall issue for me . Install nmap on your ubuntu box with apt-get install nmap and run nmap -p 445 fileserver to see if the samba port is blocked by firewall or not.



    Other way is to put -v sudo mount -v -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx
    to see the verbose message from the mounting.



    Hope it helps






    share|improve this answer
























    • Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

      – Fam Wired
      Nov 12 '15 at 14:37











    • I think you have right about the firewall. Do you know how to open the port?

      – Fam Wired
      Nov 12 '15 at 14:38











    • So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

      – Nikolay Nikolov
      Nov 12 '15 at 14:39











    • If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

      – Nikolay Nikolov
      Nov 12 '15 at 14:40











    • It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

      – Fam Wired
      Nov 12 '15 at 14:53














    0












    0








    0







    This is firewall issue for me . Install nmap on your ubuntu box with apt-get install nmap and run nmap -p 445 fileserver to see if the samba port is blocked by firewall or not.



    Other way is to put -v sudo mount -v -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx
    to see the verbose message from the mounting.



    Hope it helps






    share|improve this answer













    This is firewall issue for me . Install nmap on your ubuntu box with apt-get install nmap and run nmap -p 445 fileserver to see if the samba port is blocked by firewall or not.



    Other way is to put -v sudo mount -v -t cifs //fileserver/share /mnt/temp -o username=user,password=xxx
    to see the verbose message from the mounting.



    Hope it helps







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 12 '15 at 14:08









    Nikolay NikolovNikolay Nikolov

    2,9011512




    2,9011512













    • Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

      – Fam Wired
      Nov 12 '15 at 14:37











    • I think you have right about the firewall. Do you know how to open the port?

      – Fam Wired
      Nov 12 '15 at 14:38











    • So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

      – Nikolay Nikolov
      Nov 12 '15 at 14:39











    • If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

      – Nikolay Nikolov
      Nov 12 '15 at 14:40











    • It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

      – Fam Wired
      Nov 12 '15 at 14:53



















    • Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

      – Fam Wired
      Nov 12 '15 at 14:37











    • I think you have right about the firewall. Do you know how to open the port?

      – Fam Wired
      Nov 12 '15 at 14:38











    • So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

      – Nikolay Nikolov
      Nov 12 '15 at 14:39











    • If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

      – Nikolay Nikolov
      Nov 12 '15 at 14:40











    • It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

      – Fam Wired
      Nov 12 '15 at 14:53

















    Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

    – Fam Wired
    Nov 12 '15 at 14:37





    Thanks. I got nmap response: Host seems down. I'm running this ubuntu inside another ubuntu host (vmware)

    – Fam Wired
    Nov 12 '15 at 14:37













    I think you have right about the firewall. Do you know how to open the port?

    – Fam Wired
    Nov 12 '15 at 14:38





    I think you have right about the firewall. Do you know how to open the port?

    – Fam Wired
    Nov 12 '15 at 14:38













    So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

    – Nikolay Nikolov
    Nov 12 '15 at 14:39





    So, run nmap -p 445 fileserver -P0. 100% this is firewall issue!

    – Nikolay Nikolov
    Nov 12 '15 at 14:39













    If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

    – Nikolay Nikolov
    Nov 12 '15 at 14:40





    If the machine is windows , go to windows firewall settings. If it is ubuntu , maybe you should stop apparmor

    – Nikolay Nikolov
    Nov 12 '15 at 14:40













    It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

    – Fam Wired
    Nov 12 '15 at 14:53





    It works OK on the ubuntu host computer. It's the ubuntu inside the ubuntu that failes.

    – Fam Wired
    Nov 12 '15 at 14:53













    0














    Another possibility:



    If you are using a standard VMWare Network-Configuration for that Virtual machine and following the documentation at http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-4B9B4A82-D0F7-4939-BD7B-B6BF92FF7350.html




    In a typical configuration, the New Virtual Machine wizard sets up NAT
    for the virtual machine. You must select the custom configuration
    option to configure bridged networking or host-only networking. The
    wizard connects the virtual machine to the appropriate virtual
    network.




    Check out the VM's Network-Configuration and switch to bridged networking so that the VM has access to the same network-resources as your host machine.



    Hope it helps.



    NOTE: It was intended to be a comment, but I cannot do that yet :)






    share|improve this answer
























    • Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

      – Fam Wired
      Nov 16 '15 at 9:04











    • Your solution was going to be my next answer :-D Glad you sorted this out.

      – Eduardo López
      Nov 16 '15 at 9:39
















    0














    Another possibility:



    If you are using a standard VMWare Network-Configuration for that Virtual machine and following the documentation at http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-4B9B4A82-D0F7-4939-BD7B-B6BF92FF7350.html




    In a typical configuration, the New Virtual Machine wizard sets up NAT
    for the virtual machine. You must select the custom configuration
    option to configure bridged networking or host-only networking. The
    wizard connects the virtual machine to the appropriate virtual
    network.




    Check out the VM's Network-Configuration and switch to bridged networking so that the VM has access to the same network-resources as your host machine.



    Hope it helps.



    NOTE: It was intended to be a comment, but I cannot do that yet :)






    share|improve this answer
























    • Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

      – Fam Wired
      Nov 16 '15 at 9:04











    • Your solution was going to be my next answer :-D Glad you sorted this out.

      – Eduardo López
      Nov 16 '15 at 9:39














    0












    0








    0







    Another possibility:



    If you are using a standard VMWare Network-Configuration for that Virtual machine and following the documentation at http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-4B9B4A82-D0F7-4939-BD7B-B6BF92FF7350.html




    In a typical configuration, the New Virtual Machine wizard sets up NAT
    for the virtual machine. You must select the custom configuration
    option to configure bridged networking or host-only networking. The
    wizard connects the virtual machine to the appropriate virtual
    network.




    Check out the VM's Network-Configuration and switch to bridged networking so that the VM has access to the same network-resources as your host machine.



    Hope it helps.



    NOTE: It was intended to be a comment, but I cannot do that yet :)






    share|improve this answer













    Another possibility:



    If you are using a standard VMWare Network-Configuration for that Virtual machine and following the documentation at http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-4B9B4A82-D0F7-4939-BD7B-B6BF92FF7350.html




    In a typical configuration, the New Virtual Machine wizard sets up NAT
    for the virtual machine. You must select the custom configuration
    option to configure bridged networking or host-only networking. The
    wizard connects the virtual machine to the appropriate virtual
    network.




    Check out the VM's Network-Configuration and switch to bridged networking so that the VM has access to the same network-resources as your host machine.



    Hope it helps.



    NOTE: It was intended to be a comment, but I cannot do that yet :)







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 16 '15 at 8:44









    Eduardo LópezEduardo López

    72159




    72159













    • Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

      – Fam Wired
      Nov 16 '15 at 9:04











    • Your solution was going to be my next answer :-D Glad you sorted this out.

      – Eduardo López
      Nov 16 '15 at 9:39



















    • Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

      – Fam Wired
      Nov 16 '15 at 9:04











    • Your solution was going to be my next answer :-D Glad you sorted this out.

      – Eduardo López
      Nov 16 '15 at 9:39

















    Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

    – Fam Wired
    Nov 16 '15 at 9:04





    Thanks, the net on the virtual machine is bridge configured as you pointed out. It also got a ip-address in the same subnet as the fileserver. :)

    – Fam Wired
    Nov 16 '15 at 9:04













    Your solution was going to be my next answer :-D Glad you sorted this out.

    – Eduardo López
    Nov 16 '15 at 9:39





    Your solution was going to be my next answer :-D Glad you sorted this out.

    – Eduardo López
    Nov 16 '15 at 9:39











    0














    Finally I got it to work.



    I used the ip-address (192.168.1.11) instead of fileserver.



    When ping:ing the fileserver name on the client I got ping response from another ip/computer (192.168.1.16) than I got from the host computer (192.168.1.11) !



    Don't know why the dns name was linked to wrong ip on the client computer?






    share|improve this answer




























      0














      Finally I got it to work.



      I used the ip-address (192.168.1.11) instead of fileserver.



      When ping:ing the fileserver name on the client I got ping response from another ip/computer (192.168.1.16) than I got from the host computer (192.168.1.11) !



      Don't know why the dns name was linked to wrong ip on the client computer?






      share|improve this answer


























        0












        0








        0







        Finally I got it to work.



        I used the ip-address (192.168.1.11) instead of fileserver.



        When ping:ing the fileserver name on the client I got ping response from another ip/computer (192.168.1.16) than I got from the host computer (192.168.1.11) !



        Don't know why the dns name was linked to wrong ip on the client computer?






        share|improve this answer













        Finally I got it to work.



        I used the ip-address (192.168.1.11) instead of fileserver.



        When ping:ing the fileserver name on the client I got ping response from another ip/computer (192.168.1.16) than I got from the host computer (192.168.1.11) !



        Don't know why the dns name was linked to wrong ip on the client computer?







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 16 '15 at 8:50









        Fam WiredFam Wired

        113




        113






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f697193%2fmount-cifs-of-shared-windows-folder-problem%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

            How did Captain America manage to do this?

            迪纳利

            南乌拉尔铁路局