Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Fail to connect to Windows shares: "failed to retrieve share list from server"

  1. #1
    Join Date
    Feb 2017
    Beans
    3

    Fail to connect to Windows shares: "failed to retrieve share list from server"

    I thought that problems connecting with Windows shares had been solved previously (much editing of config files, etc). But Samba seems temperamental.

    Error message is: "failed to retrieve share list from server: No route to host"

    or "failed to retrieve share list from server: Connection timed out"

    This depends on setting of 'name resolve order' in smb.conf
    (Perhaps a clue?)

    Is there a recommended procedure for debugging this?

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    ooops. dbl post. Don't know how that happened.
    Last edited by TheFu; January 19th, 2020 at 05:12 AM.

  3. #3
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    It isn't samba. It is your name resolution or a failed routing table. If the machines are on the same subnet, try connecting using the IP address. Does that work? If so, then it is that the client doesn't know where to find the server on the network. There are many different ways to solve that. The best solution depends on how well managed your LAN is. If it isn't well-managed, then some sort of zero-conf is probably easiest.

    About 3 times a year, my only remaining Windows box will stop sharing to anyone. The machine hasn't had any new programs installed in years - including patches. But it will just stop sharing.

    I didn't think smb.conf had anything to do with client access. That is just for running a samba server, right?

    First, perhaps if you would be extremely clear about which is the client machine and which is the server, then someone smarter than me could help? Or are you truly using smbclient from Ubuntu to connect to a Windows share?

  4. #4
    Join Date
    Dec 2009
    Beans
    6,576

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    What version of Windows are you running?

    Accessing a Windows machine depends of which version of Windows is being accessed I'm afraid.

    First: I would access the Windows machine by ip address just to make sure it can connect without using netbios names. In your file manager:
    smb://192.168.0.100

    If it is a legacy Windows system ( anything before Win10 ) and you want to access the server via discovery in your Linux file manager NetBIOS rules and yes the name resolution order does make a difference. If you haven't already done so install samba:
    Code:
    sudo apt install samba
    And right under the workgroup = WORKGROUP line add this one:
    Code:
    name resolve order = bcast host lmhosts wins
    Then restart samba in this order:
    Code:
    sudo service smbd restart
    sudo service nmbd restart
    NetBIOS is a flaky thing and seems to be dependent on humidity levels, barometric presure, and sun spot activity. It's the reason Microsoft pretty much removed it in Win10.

    Speaking of Win10, if you have kept your Win10 machine up to date every time a Linux machine attempts access through the file manager it will always result in Failed to retrieve share list from server: Connection timed out. Win10 disables the smb1 dialect ( effectively disabling NetBIOS ) yet because of a bug induced by gnome the file manager can only access by smb1. Your best bet here is a CIFS mount.

    For example to temporarily access my Win10 machine I can mount it with:
    Code:
    sudo mount -t cifs //win10.local/shared /mnt/Win10Shared -o username=smbuser,password=smbuserpw,uid=morbius
    This will access the Win10 machine with smb3 instead of smb1. Also note that I'm using the mDNS host name ( win10.local ) not the NetBIOS name for the server.
    Last edited by Morbius1; January 19th, 2020 at 02:44 PM.

  5. #5
    Join Date
    Apr 2020
    Beans
    3

    Question Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    Please help - I suddenly got into this problem but the listed here solutions didn't seem to work for me
    It certainly looks like the Windows 10 system is a culprit, but I cannot figure out what happened.
    I have 4 PC's in my network ( 2 Win10, 1 Win7, 1 Ubuntu 18.04) - and I was able to transfer files between all of them for 4 months no issues until last week Wednesday (Apr15,2020).
    Suddenly, I cannot access shared folders on only one Win10 from Ubuntu - it gives the message
    "Failed to retrieve share list from server:Connection timed out"

    What is puzzling - I can access other Win10 and Win7 from Ubuntu, I can access Ubuntu from all other (both 2 Win10 and Win7) workstations, as well as I can access the Win10 in question from other Win10 and Win7.
    I neither change any settings nor installed new software - only can think of some system update, but why it affected only one specific directional combination?

    Thank you very much in advance for any help and suggestions

  6. #6
    Join Date
    Dec 2009
    Beans
    6,576

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    "Failed to retrieve share list from server: Connection timed out"

    You can get that error message from trying to access from your file manager any server that has disabled smb1. It's becasue of a bug in a sub-componenet of gvfs.

    Access it this way in your file managers location bar:
    Code:
    smb://win10-host-name.local/share-name
    You have to specify the windows host name and share name explicitly. You can't use smb://win10-host-name.local by itself to see the list of shares.

  7. #7
    Join Date
    Apr 2020
    Beans
    5

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    if it doesn't work with the host name, try with the IP address

    smb://IPAddress.local/share-name

  8. #8
    Join Date
    Dec 2009
    Beans
    6,576

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    smb://IPAddress.local/share-name
    Get rid of the .local at the end.

    win10-host-name.local is the mDNS host name ( Windows host name with a .local attached to the end ) of the Windows box. IPAddress.local isn't really anything.

  9. #9
    Join Date
    Apr 2020
    Beans
    3

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    Thank you very much everyone
    this way it connects nicely

  10. #10
    Join Date
    Apr 2020
    Beans
    3

    Re: Fail to connect to Windows shares: "failed to retrieve share list from server"

    Thanks a lot again for your help - as it solved my problem truly effectively
    Yet, still a question (rather out of sheer curiosity) remains - why I am having this issue with one Win10 system, but other Win10 and Win7 I can reach and see the share lists, i.e. without explicitly adding /share-name?

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •