FedoraForum.org - Fedora Support Forums and Community
Results 1 to 10 of 10
  1. #1
    Join Date
    Mar 2007
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    FC17, Samba, Browsing Windows Shares not accessible

    I installed Fedora 17 including all updates. I need to browse the Windows network where I can access and/or view the available shares (folders and printers). I cannot browse the Windows computers on the network. When I open Files from the Favorites bar and click on Browse Network, I see the "Windows Network" icon. I double-click the "Windows Network" icon where it takes about 10 seconds to show the "Workgroup" icon. I double-click on the "Workgroup" icon, I see the 'Opening "Workgroup"' window for a while, and then it shows the computers names on the network. When I double-click on one of the computer names, it shows Opening the computer name for some time and then "Unable to mount location", "Failed to retrieve share list from server" with an OK button. I cannot get past this point. I never had this problem in the past when I installed Fedora and accessing network shares.

    There are there (3) different Windows computers where each of the Windows computers can access the folder shares and shared printers: Windows 8 Pro x64, Windows 7 Home Premium x64, and Windows XP SP3.

    I have also reloaded Fedora 17 x64 several times with running updates with the same result. I also ran many Google searches along with searches in the Fedora Forum. Both with never finding a solution (obviously) to this problem.

    Here is the info that may be needed to help me correct this problem.

    Fedora Core 17, Linux kernel: 3.6.7-4.fc17.x86_64.

    Code:
    cifs-utils.x86_64                    5.8-1.fc17
    samba.x86_64                         2:3.6.9-96.fc17.1
    samba-common.x86_64                  2:3.6.9-96.fc17.1
    Note - I tried with the Firewall disabled and Firewall enabled with Samba and Samba Client selected to open those ports with the same result above. I also disabled the Windows Firewalls in Windows with the same result.

    Code:
    # cat /etc/selinux/config 
    
    # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    #     enforcing - SELinux security policy is enforced.
    #     permissive - SELinux prints warnings instead of enforcing.
    #     disabled - No SELinux policy is loaded.
    SELINUX=disabled   # enforcing
    # SELINUXTYPE= can take one of these two values:
    #     targeted - Targeted processes are protected,
    #     minimum - Modification of targeted policy. Only selected processes are protected. 
    #     mls - Multi Level Security protection.
    SELINUXTYPE=targeted 
    
    
    # cat /etc/samba/smb.conf
    [global]
    	workgroup = WORKGROUP
    	server string = Samba Server Version %v
    	# log files split per-machine:
    	log file = /var/log/samba/log.%m
    	# maximum size of 50KB per log file, then rotate:
    	max log size = 50
    	security = user
    	passdb backend = tdbsam
    	wins support = yes
    	load printers = yes
    	cups options = raw
    [homes]
    	comment = Home Directories
    	browseable = no
    	writable = yes
    ;	valid users = %S
    ;	valid users = MYDOMAIN\%S
    [printers]
    	comment = All Printers
    	path = /var/spool/samba
    	browseable = no
    	guest ok = no
    	writable = no
    	printable = yes
    
    # systemctl status smb
    smb.service - Samba SMB Daemon
    	  Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled)
    	  Active: active (running) since Tue, 27 Nov 2012 18:21:07 -0500; 11min ago
    	 Process: 744 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS)
    	Main PID: 747 (smbd)
    	  CGroup: name=systemd:/system/smb.service
    		  ├ 747 /usr/sbin/smbd
    		  └ 756 /usr/sbin/smbd
    
    # systemctl status nmb
    nmb.service - Samba NMB Daemon
    	  Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
    	  Active: active (running) since Tue, 27 Nov 2012 18:21:07 -0500; 11min ago
    	 Process: 716 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=0/SUCCESS)
    	Main PID: 719 (nmbd)
    	  CGroup: name=systemd:/system/nmb.service
    		  ├ 719 /usr/sbin/nmbd
    		  └ 720 /usr/sbin/nmbd
    
    # systemctl status iptables.service
    iptables.service - IPv4 firewall with iptables
    	  Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled)
    	  Active: inactive (dead)
    	  CGroup: name=systemd:/system/iptables.service
    
    # getenforce
    Disabled
    Thank you for any feedback, help, etc. you may be able to provide.

  2. #2
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    15,366
    Mentioned
    186 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    I think you might need to install the samba-winbind package

  3. #3
    Join Date
    Mar 2007
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Quote Originally Posted by marko
    I think you might need to install the samba-winbind package
    Package was not installed. Installed the package, same problem. I even restarted Fedora 17 with the same result.

  4. #4
    Join Date
    Nov 2008
    Location
    Canada
    Posts
    2,729
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Well the first big hint goolge should give you is that linux does not use netbios/wins name resolution by default. And you don't say if you're using nautilus or dolphine so I'll assume your browser needs or want netbios name resolution. Try adding wins to the host parameter in nsswitch.conf. Yeah order does matter..., a little, and you might want to restart just to be sure.

  5. #5
    Join Date
    Mar 2007
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Quote Originally Posted by beaker_
    Well the first big hint goolge should give you is that linux does not use netbios/wins name resolution by default. And you don't say if you're using nautilus or dolphine so I'll assume your browser needs or want netbios name resolution. Try adding wins to the host parameter in nsswitch.conf. Yeah order does matter..., a little, and you might want to restart just to be sure.
    I changed the hosts order in the nsswitch.conf file:

    Code:
    # vi /etc/nsswitch.conf
    
    #hosts:     db files nisplus nis dns
    hosts:      files dns wins #myhostname
    Then I ran:

    Code:
    # systemctl enable smb.service
    # systemctl enable nmb.service
    # systemctl start smb.service
    # systemctl start nmb.service
    I tried to access the Windows network shares and had the same problem.

    I then installed:

    Code:
    # yum install system-config-samba
    to verify the samba setup, looks good. Same problem of accessing Windows networking shares. I restarted the smb and nmb services:

    Code:
    # systemctl restart smb.service
    # systemctl restart nmb.service
    and had no success again, same problems of trying to access network shares.

    I remember seeing in this thread that samba got reinstalled, which I do not remember seeing in other threads:

    Code:
    # yum reinstall samba
    After reinstall samba, when I access one of the Windows 8 and Windows 7 network shares, I receive the prompt for entering the username and password (which I expected). After entering the Windows username and password for the computer, I was able to access (or browse) the available Windows shares.

  6. #6
    Join Date
    Jun 2008
    Posts
    8
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Reinstall worked for me too.
    Interesting..

  7. #7
    Join Date
    Jan 2010
    Location
    behind that screen...
    Posts
    971
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    i ussually have to allow samba in the firewall...

  8. #8
    Join Date
    Nov 2008
    Location
    Canada
    Posts
    2,729
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Funny because samba has little - nothing to do with network browsing.

  9. #9
    Join Date
    Jan 2010
    Location
    behind that screen...
    Posts
    971
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    nmbd..........

  10. #10
    Join Date
    Nov 2008
    Location
    Canada
    Posts
    2,729
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC17, Samba, Browsing Windows Shares not accessible

    Oh I'm sorry, I should have said samba and winbind have zero - nothing todo with browsing a network.
    Attached Images Attached Images

Similar Threads

  1. [SOLVED] SAMBA - no access on samba shares (FC17)
    By Otchum in forum Servers & Networking
    Replies: 0
    Last Post: 17th November 2012, 02:48 PM
  2. Samba Shares not accessible
    By Tekno_Cowboy in forum Servers & Networking
    Replies: 8
    Last Post: 20th January 2009, 12:58 AM
  3. Samba shares not accessible after reboot in FC9
    By AndrejaKo in forum Servers & Networking
    Replies: 14
    Last Post: 6th January 2009, 05:13 PM
  4. Windows shares not accessible after standard configuration
    By rgaelzer in forum Servers & Networking
    Replies: 5
    Last Post: 23rd March 2008, 06:23 PM
  5. browsing windows shares with kde
    By mert in forum Using Fedora
    Replies: 6
    Last Post: 25th October 2004, 06:31 AM

Tags for this Thread

Posting Permissions

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