Samba Network Path not found












1















I am trying to set up a Samba-Connection between my linux server and my home computer. However, when I try to add the Samba share as a network drive using



net use k: \ip.ip.ip.ipshared password /user:username


I get the following error message:



System Error 53 has occured.
The network path was not found.


I just set the Samba server up using



sudo smbpasswd -a username
sudo net usershare add shared /home/user/shared "Shared Files" username:f


That is all I did with the configs, everything else is freshly installed.



sudo smbclient -L ip.ip.ip.ip


Does in fact print out the shares I am looking for when executed in the linux shell.



Any ideas on how to resolve the problem?



Edit: My Windows Firewall and my AVG Firewall are both disabled. I'm running Windows 8.1



Edit: testparm -s



Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb

[homes]
comment = Home Directories
valid users = %S
create mask = 0700
directory mask = 0700
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers


Edit: sudo net usershare info



[shared]
path=/home/username/shared
comment=Shared Files
usershare_acl=V220110897556081username:F,
guest_ok=n









share|improve this question

























  • that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

    – Frank Thomas
    Mar 14 '15 at 4:35











  • I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

    – Freeman
    Mar 14 '15 at 4:42











  • what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

    – Frank Thomas
    Mar 14 '15 at 4:55











  • Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

    – Freeman
    Mar 14 '15 at 5:09


















1















I am trying to set up a Samba-Connection between my linux server and my home computer. However, when I try to add the Samba share as a network drive using



net use k: \ip.ip.ip.ipshared password /user:username


I get the following error message:



System Error 53 has occured.
The network path was not found.


I just set the Samba server up using



sudo smbpasswd -a username
sudo net usershare add shared /home/user/shared "Shared Files" username:f


That is all I did with the configs, everything else is freshly installed.



sudo smbclient -L ip.ip.ip.ip


Does in fact print out the shares I am looking for when executed in the linux shell.



Any ideas on how to resolve the problem?



Edit: My Windows Firewall and my AVG Firewall are both disabled. I'm running Windows 8.1



Edit: testparm -s



Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb

[homes]
comment = Home Directories
valid users = %S
create mask = 0700
directory mask = 0700
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers


Edit: sudo net usershare info



[shared]
path=/home/username/shared
comment=Shared Files
usershare_acl=V220110897556081username:F,
guest_ok=n









share|improve this question

























  • that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

    – Frank Thomas
    Mar 14 '15 at 4:35











  • I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

    – Freeman
    Mar 14 '15 at 4:42











  • what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

    – Frank Thomas
    Mar 14 '15 at 4:55











  • Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

    – Freeman
    Mar 14 '15 at 5:09
















1












1








1








I am trying to set up a Samba-Connection between my linux server and my home computer. However, when I try to add the Samba share as a network drive using



net use k: \ip.ip.ip.ipshared password /user:username


I get the following error message:



System Error 53 has occured.
The network path was not found.


I just set the Samba server up using



sudo smbpasswd -a username
sudo net usershare add shared /home/user/shared "Shared Files" username:f


That is all I did with the configs, everything else is freshly installed.



sudo smbclient -L ip.ip.ip.ip


Does in fact print out the shares I am looking for when executed in the linux shell.



Any ideas on how to resolve the problem?



Edit: My Windows Firewall and my AVG Firewall are both disabled. I'm running Windows 8.1



Edit: testparm -s



Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb

[homes]
comment = Home Directories
valid users = %S
create mask = 0700
directory mask = 0700
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers


Edit: sudo net usershare info



[shared]
path=/home/username/shared
comment=Shared Files
usershare_acl=V220110897556081username:F,
guest_ok=n









share|improve this question
















I am trying to set up a Samba-Connection between my linux server and my home computer. However, when I try to add the Samba share as a network drive using



net use k: \ip.ip.ip.ipshared password /user:username


I get the following error message:



System Error 53 has occured.
The network path was not found.


I just set the Samba server up using



sudo smbpasswd -a username
sudo net usershare add shared /home/user/shared "Shared Files" username:f


That is all I did with the configs, everything else is freshly installed.



sudo smbclient -L ip.ip.ip.ip


Does in fact print out the shares I am looking for when executed in the linux shell.



Any ideas on how to resolve the problem?



Edit: My Windows Firewall and my AVG Firewall are both disabled. I'm running Windows 8.1



Edit: testparm -s



Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb

[homes]
comment = Home Directories
valid users = %S
create mask = 0700
directory mask = 0700
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers


Edit: sudo net usershare info



[shared]
path=/home/username/shared
comment=Shared Files
usershare_acl=V220110897556081username:F,
guest_ok=n






linux windows network-shares samba






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 14 '15 at 5:07







Freeman

















asked Mar 14 '15 at 4:25









FreemanFreeman

613




613













  • that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

    – Frank Thomas
    Mar 14 '15 at 4:35











  • I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

    – Freeman
    Mar 14 '15 at 4:42











  • what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

    – Frank Thomas
    Mar 14 '15 at 4:55











  • Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

    – Freeman
    Mar 14 '15 at 5:09





















  • that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

    – Frank Thomas
    Mar 14 '15 at 4:35











  • I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

    – Freeman
    Mar 14 '15 at 4:42











  • what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

    – Frank Thomas
    Mar 14 '15 at 4:55











  • Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

    – Freeman
    Mar 14 '15 at 5:09



















that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

– Frank Thomas
Mar 14 '15 at 4:35





that particular message should indicate that the IP is bad, or the service cannot be found, or there is an error in its expression. can you ping the IP? check testparm -s on the server, to check for config issues. confirm that the ~shared directory allows at least read priv for the user you are using. on the server, make sure samba is started, and run netstat -ntlup and confirm 139 and 445 are listening.

– Frank Thomas
Mar 14 '15 at 4:35













I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

– Freeman
Mar 14 '15 at 4:42





I actually resolved the IP out of the ping domain.com command. The testparm -s output has been added to the post. I'm giving ~/shared the permissions of 755 temporarily. Samba is up and running and listening on 139 and 445.

– Freeman
Mar 14 '15 at 4:42













what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

– Frank Thomas
Mar 14 '15 at 4:55





what does sudo net usershare shared show? from samba.org/samba/docs/man/manpages/net.8.html the permission letter should be capital, so you may want to use the usershare add command again with a capital F. Personally I kind of hate usershares, since their config is so limited, but I'm turning into an old fart....

– Frank Thomas
Mar 14 '15 at 4:55













Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

– Freeman
Mar 14 '15 at 5:09







Deleted and re-added the share with a capital F, doesn't seem to make a difference sadly. Added the information outputted by sudo net usershare info to the post. If you have any suggestions on how to solve this without using usershares, I'll be happy to try and test them out.

– Freeman
Mar 14 '15 at 5:09












1 Answer
1






active

oldest

votes


















0














I had this same issue with my Samba server. I fixed it by forcing the Samba server's NetBIOS name to resolve to it's local IP in the hosts file. To be clear, I made this modification to the hosts file on the Windows machine I use to access the Samba share.






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%2f889448%2fsamba-network-path-not-found%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I had this same issue with my Samba server. I fixed it by forcing the Samba server's NetBIOS name to resolve to it's local IP in the hosts file. To be clear, I made this modification to the hosts file on the Windows machine I use to access the Samba share.






    share|improve this answer




























      0














      I had this same issue with my Samba server. I fixed it by forcing the Samba server's NetBIOS name to resolve to it's local IP in the hosts file. To be clear, I made this modification to the hosts file on the Windows machine I use to access the Samba share.






      share|improve this answer


























        0












        0








        0







        I had this same issue with my Samba server. I fixed it by forcing the Samba server's NetBIOS name to resolve to it's local IP in the hosts file. To be clear, I made this modification to the hosts file on the Windows machine I use to access the Samba share.






        share|improve this answer













        I had this same issue with my Samba server. I fixed it by forcing the Samba server's NetBIOS name to resolve to it's local IP in the hosts file. To be clear, I made this modification to the hosts file on the Windows machine I use to access the Samba share.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 3 '16 at 19:28









        AngelAngel

        1




        1






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f889448%2fsamba-network-path-not-found%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 to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀