After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582612 - smb:/// for "Windows Network" provides an empty list
smb:/// for "Windows Network" provides an empty list
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: smb backend
1.2.x
Other All
: Normal normal
: ---
Assigned To: Tomas Bzatek
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-14 13:09 UTC by Reid Thompson
Modified: 2018-09-21 16:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
gvfsd debug output (28.74 KB, text/plain)
2009-05-22 11:48 UTC, Reid Thompson
Details

Description Reid Thompson 2009-05-14 13:09:28 UTC
Please describe the problem:
trying to view windows network yields an empty list

Steps to reproduce:
1. start nautilus network view
2. select Windows Network to view hosts
3. result is empty 


Actual results:
see 1.2.3 above

Expected results:
ability to drill down to windows hosts

Does this happen every time?
yes

Other information:
Comment 1 Tomas Bzatek 2009-05-21 13:50:43 UTC
OK, can you please specify what version exactly do you use?

Does smbtree print something?

Another useful information would be output of `GVFS_DEBUG=1 /usr/libexec/gvfsd -r` when opening smb:///

Last question: have you turned your firewall off or at least made a hole for SMB protocol broadcasts into it?
Comment 2 Reid Thompson 2009-05-22 11:47:08 UTC
(In reply to comment #1)
> OK, can you please specify what version exactly do you use?
> 
> Does smbtree print something?
> 
> Another useful information would be output of `GVFS_DEBUG=1 /usr/libexec/gvfsd
> -r` when opening smb:///
> 
> Last question: have you turned your firewall off or at least made a hole for
> SMB protocol broadcasts into it?
> 
Will post gvfsd debug info in a following attachment
smbtree appears to work???

$ smbtree
Password: 
WORKGROUP
	\\VM002-XPSHIELD 		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine VM002-XPSHIELD.  Error was NT_STATUS_ACCESS_DENIED
	\\UBUNTU-4959    		UBUNTU-4959 server (Samba, Ubuntu)
		\\UBUNTU-4959\HP-LaserJet-P4014	HP-LaserJet-P4014
		\\UBUNTU-4959\HP8550         	Development
		\\UBUNTU-4959\print$         	Printer Drivers
		\\UBUNTU-4959\IPC$           	IPC Service (UBUNTU-4959 server (Samba, Ubuntu))
	\\TEST-D498FE5317		
timeout connecting to 172.16.48.93:445
timeout connecting to 172.16.48.93:139
Error connecting to 172.16.48.93 (Operation already in progress)
cli_start_connection: failed to connect to TEST-D498FE5317<20> (172.16.48.93). Error NT_STATUS_ACCESS_DENIED
	\\MME-DESKTOP    		mme-desktop server (Samba, Ubuntu)
		\\MME-DESKTOP\Canon3300      	Canon ImageRunner 3300i
		\\MME-DESKTOP\HP-LaserJet-P4014	HP LaserJet P4010
		\\MME-DESKTOP\HP8550-Color   	HP 8550 GN Color Printer
		\\MME-DESKTOP\T640-Sales     	Lexmark T640 located in Sales
		\\MME-DESKTOP\print$         	Printer Drivers
		\\MME-DESKTOP\IPC$           	IPC Service (mme-desktop server (Samba, Ubuntu))
	\\MEGADOTNET     		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine MEGADOTNET.  Error was NT_STATUS_ACCESS_DENIED
	\\INSTALLTEST    		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine INSTALLTEST.  Error was NT_STATUS_ACCESS_DENIED
	\\H5540          		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine H5540.  Error was NT_STATUS_ACCESS_DENIED
	\\DEV2K3TEST     		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine DEV2K3TEST.  Error was NT_STATUS_ACCESS_DENIED
	\\CENTRALIVRTEST2		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine CENTRALIVRTEST2.  Error was NT_STATUS_ACCESS_DENIED
	\\CENTADMIN2     		
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine CENTADMIN2.  Error was NT_STATUS_ACCESS_DENIED
	\\CENTADMIN1     		
		\\CENTADMIN1\C$             	Default share
		\\CENTADMIN1\ADMIN$         	Remote Admin
		\\CENTADMIN1\C              	
		\\CENTADMIN1\IPC$           	Remote IPC
	\\CADEVDB        		
		\\CADEVDB\C$             	Default share
		\\CADEVDB\ADMIN$         	Remote Admin
		\\CADEVDB\My Pictures    	
		\\CADEVDB\IPC$           	Remote IPC
	\\ATEBTEST3      		
		\\ATEBTEST3\C$             	Default share
		\\ATEBTEST3\ADMIN$         	Remote Admin
		\\ATEBTEST3\test           	
		\\ATEBTEST3\IPC$           	Remote IPC
	\\ATEBTEST2      		
... lots more output related to hosts on the network.

Comment 3 Reid Thompson 2009-05-22 11:48:26 UTC
Created attachment 135167 [details]
gvfsd debug output
Comment 4 Reid Thompson 2009-05-22 11:59:51 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > OK, can you please specify what version exactly do you use?
> > 
> > Does smbtree print something?
> > 
> > Another useful information would be output of `GVFS_DEBUG=1 /usr/libexec/gvfsd
> > -r` when opening smb:///
> > 
> > Last question: have you turned your firewall off or at least made a hole for
> > SMB protocol broadcasts into it?
> > 
> Will post gvfsd debug info in a following attachment
> smbtree appears to work???
> 
> $ smbtree
> Password: 
> WORKGROUP
>         \\VM002-XPSHIELD                
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine
> VM002-XPSHIELD.  Error was NT_STATUS_ACCESS_DENIED
>         \\UBUNTU-4959                   UBUNTU-4959 server (Samba, Ubuntu)
>                 \\UBUNTU-4959\HP-LaserJet-P4014 HP-LaserJet-P4014
>                 \\UBUNTU-4959\HP8550            Development
>                 \\UBUNTU-4959\print$            Printer Drivers
>                 \\UBUNTU-4959\IPC$              IPC Service (UBUNTU-4959 server
> (Samba, Ubuntu))
>         \\TEST-D498FE5317               
> timeout connecting to 172.16.48.93:445
> timeout connecting to 172.16.48.93:139
> Error connecting to 172.16.48.93 (Operation already in progress)
> cli_start_connection: failed to connect to TEST-D498FE5317<20> (172.16.48.93).
> Error NT_STATUS_ACCESS_DENIED
>         \\MME-DESKTOP                   mme-desktop server (Samba, Ubuntu)
>                 \\MME-DESKTOP\Canon3300         Canon ImageRunner 3300i
>                 \\MME-DESKTOP\HP-LaserJet-P4014 HP LaserJet P4010
>                 \\MME-DESKTOP\HP8550-Color      HP 8550 GN Color Printer
>                 \\MME-DESKTOP\T640-Sales        Lexmark T640 located in Sales
>                 \\MME-DESKTOP\print$            Printer Drivers
>                 \\MME-DESKTOP\IPC$              IPC Service (mme-desktop server
> (Samba, Ubuntu))
>         \\MEGADOTNET                    
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine MEGADOTNET. 
> Error was NT_STATUS_ACCESS_DENIED
>         \\INSTALLTEST                   
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine INSTALLTEST.
>  Error was NT_STATUS_ACCESS_DENIED
>         \\H5540                         
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine H5540. 
> Error was NT_STATUS_ACCESS_DENIED
>         \\DEV2K3TEST                    
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine DEV2K3TEST. 
> Error was NT_STATUS_ACCESS_DENIED
>         \\CENTRALIVRTEST2               
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine
> CENTRALIVRTEST2.  Error was NT_STATUS_ACCESS_DENIED
>         \\CENTADMIN2                    
> cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine CENTADMIN2. 
> Error was NT_STATUS_ACCESS_DENIED
>         \\CENTADMIN1                    
>                 \\CENTADMIN1\C$                 Default share
>                 \\CENTADMIN1\ADMIN$             Remote Admin
>                 \\CENTADMIN1\C                  
>                 \\CENTADMIN1\IPC$               Remote IPC
>         \\CADEVDB                       
>                 \\CADEVDB\C$                    Default share
>                 \\CADEVDB\ADMIN$                Remote Admin
>                 \\CADEVDB\My Pictures           
>                 \\CADEVDB\IPC$                  Remote IPC
>         \\ATEBTEST3                     
>                 \\ATEBTEST3\C$                  Default share
>                 \\ATEBTEST3\ADMIN$              Remote Admin
>                 \\ATEBTEST3\test                
>                 \\ATEBTEST3\IPC$                Remote IPC
>         \\ATEBTEST2                     
> ... lots more output related to hosts on the network.
> 

Sorry --- forgot version info...
from the About tab -> Nautilus 2.26.3
Gentoo -> Linux raker 2.6.28-gentoo-r5 #1 SMP PREEMPT Fri Apr 24 11:25:12 EDT 2009 i686 Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz GenuineIntel GNU/Linux

[I] dev-python/nautilus-cd-burner-python
     Available versions:  2.24.1!t (~)2.26.0!t {debug examples}
     Installed versions:  2.26.0!t(03:24:44 PM 05/11/2009)(-debug -examples)
     Homepage:            http://pygtk.org/
     Description:         Python bindings for Nautilus CD/DVD burning

[I] gnome-base/nautilus
     Available versions:  2.24.2 2.24.2-r3 (~)2.26.2-r1 (~)2.26.3 {X beagle debug doc gnome tracker xmp}
     Installed versions:  2.26.3(11:17:55 AM 05/20/2009)(X beagle gnome -debug -doc -tracker -xmp)
     Homepage:            http://www.gnome.org/projects/nautilus/
     Description:         A file manager for the GNOME desktop
                                                                 [172.16.48.3]
[I] gnome-extra/nautilus-cd-burner
     Available versions:  *2.20.0 2.24.0 {cdr debug dvdr}
     Installed versions:  2.24.0(10:01:29 AM 02/02/2009)(cdr dvdr -debug)
     Homepage:            http://www.gnome.org/
     Description:         CD and DVD writer plugin for Nautilus

[I] gnome-extra/nautilus-open-terminal
     Available versions:  0.9 (~)0.9-r2 (~)0.11 (~)0.12 {debug}
     Installed versions:  0.12(11:23:55 AM 05/20/2009)
     Homepage:            http://manny.cluecoder.org/packages/nautilus-open-terminal/
     Description:         Nautilus Plugin for Opening Terminals

[I] gnome-extra/nautilus-sendto
     Available versions:  (~)0.12-r1 (~)0.14.0 (~)1.1.2 (~)1.1.5 {balsa bluetooth cdr claws debug eds empathy gajim mail pidgin sylpheed thunderbird upnp}
     Installed versions:  1.1.5(03:09:59 PM 05/11/2009)(cdr mail -bluetooth -debug -empathy -gajim -pidgin -upnp)
     Homepage:            http://www.gnome.org
     Description:         A nautilus extension for sending files to locations



[I] gnome-base/gvfs
     Available versions:  1.0.3-r2 (~)1.0.3-r13 (~)1.2.2 (~)1.2.3 {archive avahi bash-completion bluetooth cdda debug doc fuse gnome gnome-keyring gphoto2 hal samba}
     Installed versions:  1.2.3(11:13:42 AM 05/20/2009)(avahi bluetooth cdda gnome gphoto2 hal samba -archive -bash-completion -debug -doc -fuse -gnome-keyring)
     Homepage:            http://www.gnome.org
     Description:         GNOME Virtual Filesystem Layer


Comment 5 Reid Thompson 2009-05-22 13:03:27 UTC
as info, a bookmark to a network shared directory works fine.
also
  nautilus --no-desktop smb://a_network_host/a_shared_directory
works fine.  All files/directories on the share are accessible
Comment 6 Tomas Bzatek 2009-06-03 15:16:40 UTC
Thanks for the debug output. I found that it finds workgroups in the network (and even master browser) but fails to complete the auth process. Looks like smbclient doesn't do another pass after SPNEGO failure.

While your log says
   SPNEGO login failed: Logon failure
it should be something like
   SPNEGO login failed: Logon failure
   Server connect ok: //10.34.33.44/IPC$: 0x7f8dd800c360
and trying different ports (445, 139)

Can you post your /etc/samba/smb.conf file here and system samba version? I expect you don't have particular ~/.smb/smb.conf config file.

I suppose that 172.16.50.162 (MSHOME workgroup) and 172.16.48.213 (ATEB workgroup) are Windows machines, right?
Comment 7 Reid Thompson 2009-06-03 16:57:58 UTC
[I] net-fs/samba
     Available versions:  3.0.28 3.0.28a-r1!t ~3.0.30!t ~3.0.31!t 3.0.32!t 3.0.33!t ~3.0.34!t [M]~3.2.0_rc2!t [M]~3.2.11!t {acl ads async automount caps cups debug doc examples fam ipv6 kernel_linux ldap linguas_ja linguas_pl oav pam python quotas readline selinux swat syslog winbind}
     Installed versions:  3.0.33!t(12:38:52 PM 05/12/2009)(acl cups ipv6 kernel_linux pam python quotas readline winbind -ads -async -automount -caps -debug -doc -examples -fam -ldap -oav -selinux -swat -syslog)
     Homepage:            http://www.samba.org/
     Description:         A suite of SMB and CIFS client/server programs for UNIX

so -- 3.0.33 installed using acl cups ipv6 kernel_linux pam python quotas readline winbind config flags

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = ATEB

# netbios name is the name you will see in "Network Neighbourhood",
# but defaults to your hostname
;  netbios name = <name_of_this_server>
   netbios name = raker
# server string is the equivalent of the NT Description field
   server string = rthompso desktop %v

# 2. Printing Options:
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   printcap name = cups
   load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
   printing = cups

# 3. Logging Options:
# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Set the log (verbosity) level (0 <= log level <= 10)
; log level = 3

# 4. Security and Domain Membership Options:
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
# not work for all the hosts in your network.
;   hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest
# Allow users to map to guest:
  map to guest = bad user

# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = user
# Use password server option only with security = server or security = domain
# When using security = domain, you should use password server = *
;   password server = <NT-Server-Name>
;   password server = *

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
# Encrypted passwords are required for any use of samba in a Windows NT domain
# The smbpasswd file is only required by a server doing authentication, thus
# members of a domain do not need one.
  encrypt passwords = yes

# The following are needed to allow password changing from Windows to
# also update the Linux system password.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
;  unix password sync = Yes
# You either need to setup a passwd program and passwd chat, or
# enable pam password change
;  pam password change = yes
;  passwd program = /usr/bin/passwd %u
;  passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n ;*passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
;  username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/samba/smb.conf.%m

# Options for using winbind. Winbind allows you to do all account and
# authentication from a Windows or samba domain controller, creating
# accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
# and gid's. idmap uid and idmap gid are the only required parameters.
#
# winbind separator is the character a user must use between their domain
# name and username, defaults to "\"
;  winbind separator = +
#
# winbind use default domain allows you to have winbind return usernames
# in the form user instead of DOMAIN+user for the domain listed in the
# workgroup parameter.
;  winbind use default domain = yes
#
# template homedir determines the home directory for winbind users, with
# %D expanding to their domain name and %U expanding to their username:
;  template homedir = /home/%D/%U

# When using winbind, you may want to have samba create home directories
# on the fly for authenticated users. Ensure that /etc/pam.d/samba is
# using 'service=system-auth-winbind' in pam_stack modules, and then
# enable obedience of pam restrictions below:
;  obey pam restrictions = yes

#
# template shell determines the shell users authenticated by winbind get
;  template shell = /bin/bash

# 5. Browser Control and Networking Options:
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#       a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
   domain master = no

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# 6. Domain Control Options:
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations or Primary Domain Controller for WinNT and Win2k
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roaming profiles for WinNT and Win2k
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Where to store roaming profiles for Win9x. Be careful with this as it also
# impacts where Win2k finds it's /HOME share
; logon home = \\%L\%U\.profile


# The add user script is used by a domain member to add local user accounts
# that have been authenticated by the domain controller, or when adding
# users via the Windows NT Tools (ie User Manager for Domains).

# Scripts for file (passwd, smbpasswd) backend:
; add user script = /usr/sbin/useradd -s /bin/false '%u'
; delete user script = /usr/sbin/userdel '%s'
; add user to group script = /usr/bin/gpasswd -a '%u' '%g'
; delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
; set primary group script = /usr/sbin/usermod -g '%g' '%u'
; add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
; delete group script = /usr/sbin/groupdel '%g'

# Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller.
# Needs IDEALX scripts, and configuration in smbldap_conf.pm.
# This assumes you've installed the IDEALX scripts into /usr/share/samba/scripts...
; add user script = /usr/share/samba/scripts/smbldap-useradd.pl '%u'
; delete user script = /usr/share/samba/scripts/smbldap-userdel.pl '%u'
; add user to group script = /usr/share/samba/scripts/smbldap-groupmod.pl -m '%u' '%g'
; delete user from group script = /usr/share/samba/scripts/smbldap-groupmod.pl -x '%u' '%g'
; set primary group script = /usr/share/samba/scripts/smbldap-usermod.pl -g '%g' '%u'
; add group script = /usr/share/samba/scripts/smbldap-groupadd.pl '%g' && /usr/share/samba/scripts/smbldap-groupshow.pl %g|awk '/^gidNumber:/ {print $2}'
; delete group script = /usr/share/samba/scripts/smbldap-userdel.pl '%g'


# The add machine script is use by a samba server configured as a domain
# controller to add local machine accounts when adding machines to the domain.
# The script must work from the command line when replacing the macros,
# or the operation will fail. Check that groups exist if forcing a group.
# Script for domain controller for adding machines:
; add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false '%u'
# Script for domain controller with LDAP backend for adding machines (You need
# the IDEALX scripts, and to configure the smbldap_conf.pm first):
; add machine script = /usr/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false '%u'

# Domain groups:
# Domain groups are now configured by using the 'net groupmap' tool

# Samba Password Database configuration:
# Samba now has runtime-configurable password database backends.
# smbpasswd is for backwards compatibility only Default (not recommended),
# new installations should use tdbsam or ldap.
; passdb backend = smbpasswd
# TDB backend
; passdb backend = tdbsam
# LDAP with fallback to smbpasswd guest
# Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
; passdb backend = ldapsam:ldaps://ldap.mydomain.com
# Use the samba2 LDAP schema:
; passdb backend = ldapsam_compat:ldaps://ldap.mydomain.com

# idmap uid account range:
# This is a range of unix user-id's that samba will map non-unix RIDs to,
# such as when using Winbind
; idmap uid = 10000-20000
; idmap gid = 10000-20000

# LDAP configuration for Domain Controlling:
# The account (dn) that samba uses to access the LDAP server
# This account needs to have write access to the LDAP tree
# You will need to give samba the password for this dn, by
# running 'smbpasswd -w mypassword'
; ldap admin dn = cn=root,dc=mydomain,dc=com
; ldap ssl = start_tls
# start_tls should run on 389, but samba defaults incorrectly to 636
; ldap port = 389
; ldap suffix = dc=mydomain,dc=com
; ldap server = ldap.mydomain.com
# Seperate suffixes are available for machines, users, groups, and idmap, if
# ldap suffix appears first, it is appended to the specific suffix.
# Example for a unix-ish directory layout:
; ldap machine suffix = ou=Hosts
; ldap user suffix = ou=People
; ldap group suffix = ou=Group
; ldap idmap suffix = ou=Idmap
# Example for AD-ish layout:
; ldap machine suffix = cn=Computers
; ldap user suffix = cn=Users
; ldap group suffix = cn=Groups
; ldap idmap suffix = cn=Idmap


# 7. Name Resolution Options:
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins host lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one  WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no

# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Czech), 861 (???), 932 (Japanese),
# 936 (Simplified Chin.), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# More detail about code page is in
# "http://www.microsoft.com/globaldev/reference/oslocversion.mspx"
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
;   dos charset = 850
;   unix charset = ISO8859-1


#============================ Share Definitions ==============================
wins support = no
[homes]
   comment = Home Directories
   browseable = no
   writable = yes
# You can enable VFS recycle bin on a per share basis:
# Uncomment the next 2 lines (make sure you create a
# .recycle folder in the base of the share and ensure
# all users will have write access to it. See
# examples/VFS/recycle/REAME in the samba docs for details
;   vfs object = /usr/lib/samba/vfs/recycle.so

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /var/lib/samba/netlogon
;   guest ok = yes
;   writable = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /var/lib/samba/profiles
;    browseable = no
;    guest ok = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
;root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; ;                then mkdir -pm700 $PROFILE; chown %u:%g $PROFILE;fi

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients. On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to swap the 'print command' line below with the commented one.
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# set to yes to allow user 'guest account' to print.
   guest ok = no
   writable = no
   printable = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/Samba-HOWTO-Collection.pdf
[print$]
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   write list = @adm root
   guest ok = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba/public
;   public = yes
;   writable = no
;   write list = @staff
# Audited directory through experimental VFS audit.so module:
# Uncomment next line.
;   vfs object = /usr/lib/samba/vfs/audit.so

# Other examples.
#
# A private printer, usable only by Fred. Spool data will be placed in Fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by Fred. Note that Fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765


[SHARED]
path = /SHARED
available = yes
browseable = yes
public = yes
writable = yes
Comment 8 Reid Thompson 2009-06-03 17:02:10 UTC
> I suppose that 172.16.50.162 (MSHOME workgroup) and 172.16.48.213 (ATEB
workgroup) are Windows machines, right?


172.16.50.162 --> unsure of OS -- this box is not on the network right now, and we have a mixture of platforms

172.16.48.213 -->  yes windows
Comment 9 Tomas Bzatek 2009-06-04 12:29:39 UTC
Your setup looks pretty default. The only advice I can give you for the moment is to emerge newer 3.2 series samba. It's been stable for a while, though you will need to unmask it in your system. You'll also need to re-emerge gvfs to link against new libsmbclient.
Comment 10 Mehmet Giritli 2010-02-21 20:38:56 UTC
I got the same problem of having empty list of windows network. I was able to track this down to being an authentication error (all machines in the network are running samba, including the browser master) returned by the samba server. In the samba server, setting security=share resolves the problem for me.

Also, everything works ok when done manually: If you enter smb://workgroup/ and the browser master is set to security=user, a password input dialogue is displayed and all works fine with the login. But you will see an empty list if you just simply click on the windows network.

From what I gather, gvfs tries to login to the samba server but login fails. I have no idea which username and password the gvfs sends over to samba when the windows network is clicked, because it does not ask despite it tries to login (according to the samba log) and it fails!
Comment 11 GNOME Infrastructure Team 2018-09-21 16:45:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/96.