Samba connectivity

Page 1 of 2 12 LastLast

  1. Posts : 28
    win 10
       #1

    Samba connectivity


    I'm still working with a problem I've mentioned here before: my Windows boxes have lost connectivity to my Samba box since adopting Win 10. There are dozens of flavors of this problem discussed online, and dozens of solutions, none of which have worked for me.

    Describing what goes on in two of my hosts, GILGAMESH (Win 10 Pro) and ABELARD (Fedora Linux):

    GILGAMESH: Full Internet connectivity via router. Can SSH into ABELARD via PuTTY. Can FTP into ABELARD via WS-FTP. Host ABELARD appears in File Explorer->Network. Clicking on its icon produces error 80070035, network path not found. This PC->Add a Network Location gives same result.

    ABELARD: Has Samba 4.7.3 aboard, with two shares configured for access by the Win machines. Filesystem, including the shares, is accessible from GILGAMESH via FTP, but not via Samba.

    Samba access was normal until the Windows machines were switched from Win 7 to Win 10.

    smb.conf file attached. Suggestions?
    rj
    Samba connectivity Attached Files
      My Computer


  2. Posts : 668
    Win 10 pro
       #2

    Did you change smb.conf after installing win 10?

    Why you have:

    hosts allow = 127. 192.168.1. ? <- seems wrong anyway this can surely cause problems try to comment it it may work then

    Does a folder named /buraid exists in fedora?

    ; browseable = yes <- why commented ?

    It seems you're playing a bit with smb.conf maybe without knowing what you're touching,

    is smb1 enabled or disable in win 10?
      My Computer


  3. Posts : 28
    win 10
    Thread Starter
       #3

    I've made numerous changes in trying out the various "solutions" I've found online.
    "hosts allow = 127." dates back to when the system was working. "192.168.1." was a recent attempt to enable all the hosts on my network.
    Yes, /buraid is the share that I've been using all along for backups, and it was accessible before this problem arose. It is still accessible from Windows via PuTTY or FTP.
    The browseable line has been commented out since before the problem: no change there.
    SMB 1 is turned on in Windows, with its automatic removal turned off.
      My Computer


  4. Posts : 668
    Win 10 pro
       #4

    Have you tried to connect with file explorer from windows with:

    smb://192.168.xxx.xxx <- in linux

    //192.168.xxx.xxx <- what is fedora's lan address ?
      My Computer


  5. Posts : 28
    win 10
    Thread Starter
       #5

    Yes: no response if I do that in the filename ribbon. If I go to This PC->Add a network location and enter that, I get "The folder you entered does not appear to be valid." If i double-click on host Abelard's icon in the "Computer" block I get error 80070035, network path not found.
      My Computer


  6. Posts : 668
    Win 10 pro
       #6

    have you removed 192.168.1. ?

    what is fedora's lan address ?
      My Computer


  7. Posts : 28
    win 10
    Thread Starter
       #7

    Yes, I've removed 192.168.1.
    Abelard, the Fedora host, is 192.168.1.13. Gilgamesh the Win 10 host, is 192.168.1.111.
      My Computer


  8. Posts : 668
    Win 10 pro
       #8

    Ok can only give you some advices at this point

    commend all "host allow"
    make sure the shared folder have right permissions youre using a folder in root would try something in your home folder
    make sure the windows user is also a smb user in linux
      My Computer


  9. Posts : 28
    win 10
    Thread Starter
       #9

    OK, I've commented out the host lines. Full permissions are present in the shares, and the user is the same in both machines. Bear in mind this system was working perfectly until the switch from Win7 to Win10.
    I've stripped most of the boilerplate comments out of smb.conf and attached the current version.
    Samba connectivity Attached Files
      My Computer


  10. Posts : 668
    Win 10 pro
       #10

    [buraid]
    path = /buraid
    read only = no
    browseable = yes
    guest ok = yes
    create mask = 0664
    valid users = youruser

    and to try simple case:

    [sharedir]
    path =/home/youruser/sharedir
    read only = No
    valid users = youruser


    of course you have to restart smb or the sytem after saving the file.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:52.
Find Us




Windows 10 Forums