<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>I'm trying to set up a samba server on lucid (kubuntu) and connect to it (mostly) from a win7 machine. The win7 machine and server are both in the same workgroup.<div><br></div><div>The problem is that the server is not displayed in the win7 networking page. As a matter of fact, when I attach another kubuntu machine to the network, smbclient doesn't see the server either. So I assume something is wrong with the server config.<div><br></div><div><div>The smb.conf file is below.</div><div><div><br></div><div>Any ideas what's wrong?</div><div><br></div><div>TIA</div><div>Paul</div><div><br></div><div><div>[global]</div><div><br></div><div>## Browsing/Identification ###</div><div><br></div><div># Change this to the workgroup/NT-domain name your Samba server will part of</div><div>workgroup = KAPPA_NET</div><div><br></div><div># server string is the equivalent of the NT Description field</div><div>server string = %h server (Samba, Ubuntu)</div><div><br></div><div># Windows Internet Name Serving Support Section:</div><div># WINS Support - Tells the NMBD component of Samba to enable its WINS Server</div><div># wins support = no</div><div><br></div><div># WINS Server - Tells the NMBD components of Samba to be a WINS Client</div><div># Note: Samba can be either a WINS Server, or a WINS Client, but NOT both</div><div>; wins server = w.x.y.z</div><div><br></div><div># This will prevent nmbd to search for NetBIOS names through DNS.</div><div>dns proxy = no</div><div><br></div><div># What naming service and in what order should we use to resolve host names</div><div># to IP addresses</div><div>; name resolve order = lmhosts host wins bcast</div><div><br></div><div>#### Networking ####</div><div><br></div><div># The specific set of interfaces / networks to bind to</div><div># This can be either the interface name or an IP address/netmask;</div><div># interface names are normally preferred</div><div>; interfaces = 127.0.0.0/8 eth0</div><div><br></div><div># Only bind to the named interfaces and/or networks; you must use the</div><div># 'interfaces' option above to use this.</div><div># It is recommended that you enable this feature if your Samba machine is</div><div># not protected by a firewall or is a firewall itself. However, this</div><div># option cannot handle dynamic or non-broadcast interfaces correctly.</div><div>; bind interfaces only = yes</div><div><br></div><div><br></div><div><br></div><div>#### Debugging/Accounting ####</div><div><br></div><div># This tells Samba to use a separate log file for each machine</div><div># that connects</div><div>log file = /var/log/samba/log.%m</div><div><br></div><div># Cap the size of the individual log files (in KiB).</div><div>max log size = 1000</div><div><br></div><div># If you want Samba to only log through syslog then set the following</div><div># parameter to 'yes'.</div><div># syslog only = no</div><div><br></div><div># We want Samba to log a minimum amount of information to syslog. Everything</div><div># should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log</div><div># through syslog you should set the following parameter to something higher.</div><div>syslog = 0</div><div><br></div><div># Do something sensible when Samba crashes: mail the admin a backtrace</div><div>panic action = /usr/share/samba/panic-action %d</div><div><br></div><div><br></div><div>####### Authentication #######</div><div><br></div><div># "security = user" is always a good idea. This will require a Unix account</div><div># in this server for every user accessing the server. See</div><div># /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html</div><div># in the samba-doc package for details.</div><div># security = user</div><div><br></div><div># You may wish to use password encryption. See the section on</div><div># 'encrypt passwords' in the smb.conf(5) manpage before enabling.</div><div>encrypt passwords = no</div><div><br></div><div># If you are using encrypted passwords, Samba will need to know what</div><div># password database type you are using.</div><div>passdb backend = tdbsam</div><div><br></div><div>obey pam restrictions = yes</div><div><br></div><div># This boolean parameter controls whether Samba attempts to sync the Unix</div><div># password with the SMB password when the encrypted SMB password in the</div><div># passdb is changed.</div><div>unix password sync = yes</div><div><br></div><div># For Unix password sync to work on a Debian GNU/Linux system, the following</div><div># parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for</div><div># sending the correct chat script for the passwd program in Debian Sarge).</div><div>passwd program = /usr/bin/passwd %u</div><div>passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .</div><div><br></div><div># This boolean controls whether PAM will be used for password changes</div><div># when requested by an SMB client instead of the program listed in</div><div># 'passwd program'. The default is 'no'.</div><div>pam password change = yes</div><div><br></div><div># This option controls how unsuccessful authentication attempts are mapped</div><div># to anonymous connections</div><div>map to guest = Bad User</div><div><br></div><div>########## Domains ###########</div><div><br></div><div># Is this machine able to authenticate users. Both PDC and BDC</div><div># must have this setting enabled. If you are the BDC you must</div><div># change the 'domain master' setting to no</div><div>#</div><div>; domain logons = yes</div><div>#</div><div># The following setting only takes effect if 'domain logons' is set</div><div># It specifies the location of the user's profile directory</div><div># from the client point of view)</div><div># The following required a [profiles] share to be setup on the</div><div># samba server (see below)</div><div>; logon path = \\%N\profiles\%U</div><div># Another common choice is storing the profile in the user's home directory</div><div># (this is Samba's default)</div><div># logon path = \\%N\%U\profile</div><div><br></div><div># The following setting only takes effect if 'domain logons' is set</div><div># It specifies the location of a user's home directory (from the client</div><div># point of view)</div><div>; logon drive = H:</div><div># logon home = \\%N\%U</div><div><br></div><div># The following setting only takes effect if 'domain logons' is set</div><div># It specifies the script to run during logon. The script must be stored</div><div># in the [netlogon] share</div><div># NOTE: Must be store in 'DOS' file format convention</div><div>; logon script = logon.cmd</div><div><br></div><div># This allows Unix users to be created on the domain controller via the SAMR</div><div># RPC pipe. The example command creates a user account with a disabled Unix</div><div># password; please adapt to your needs</div><div>; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u</div><div><br></div><div># This allows machine accounts to be created on the domain controller via the</div><div># SAMR RPC pipe.</div><div># The following assumes a "machines" group exists on the system</div><div>; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u</div><div><br></div><div># This allows Unix groups to be created on the domain controller via the SAMR</div><div># RPC pipe.</div><div>; add group script = /usr/sbin/addgroup --force-badname %g</div><div><br></div><div>########## Printing ##########</div><div><br></div><div># If you want to automatically load your printer list rather</div><div># than setting them up individually then you'll need this</div><div># load printers = yes</div><div><br></div><div># lpr(ng) printing. You may wish to override the location of the</div><div># printcap file</div><div>; printing = bsd</div><div>; printcap name = /etc/printcap</div><div><br></div><div># CUPS printing. See also the cupsaddsmb(8) manpage in the</div><div># cupsys-client package.</div><div>; printing = cups</div><div>; printcap name = cups</div><div><br></div><div>############ Misc ############</div><div><br></div><div># Using the following line enables you to customise your configuration</div><div># on a per machine basis. The %m gets replaced with the netbios name</div><div># of the machine that is connecting</div><div>; include = /home/samba/etc/smb.conf.%m</div><div><br></div><div># Most people will find that this option gives better performance.</div><div># See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html</div><div># for details</div><div># You may want to add the following on a Linux system:</div><div># SO_RCVBUF=8192 SO_SNDBUF=8192</div><div># socket options = TCP_NODELAY</div><div><br></div><div># The following parameter is useful only if you have the linpopup package</div><div># installed. The samba maintainer and the linpopup maintainer are</div><div># working to ease installation and configuration of linpopup and samba.</div><div>; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &</div><div><br></div><div># Domain Master specifies Samba to be the Domain Master Browser. If this</div><div># machine will be configured as a BDC (a secondary logon server), you</div><div># must set this to 'no'; otherwise, the default behavior is recommended.</div><div># domain master = auto</div><div><br></div><div># Some defaults for winbind (make sure you're not using the ranges</div><div># for something else.)</div><div>; idmap uid = 10000-20000</div><div>; idmap gid = 10000-20000</div><div>; template shell = /bin/bash</div><div><br></div><div># The following was the default behaviour in sarge,</div><div># but samba upstream reverted the default because it might induce</div><div># performance issues in large organizations.</div><div># See Debian bug #368251 for some of the consequences of *not*</div><div># having this setting and smb.conf(5) for details.</div><div>; winbind enum groups = yes</div><div>; winbind enum users = yes</div><div><br></div><div># Setup usershare options to enable non-root users to share folders</div><div># with the net usershare command.</div><div><br></div><div># Maximum number of usershare. 0 (default) means that usershare is disabled.</div><div>; usershare max shares = 100</div><div><br></div><div># Allow users who've been granted usershare privileges to create</div><div># public shares, not just authenticated ones</div><div>usershare allow guests = yes</div><div>restrict anonymous = no</div><div>domain master = no</div><div>logon home = \\%25N\%25U</div><div>logon path = \\%25N\%25U\profile</div><div><br></div><div>#======================= Share Definitions =======================</div><div><br></div><div># Un-comment the following (and tweak the other settings below to suit)</div><div># to enable the default home directory shares. This will share each</div><div># user's home directory as \\server\username</div><div>;[homes]</div><div>; comment = Home Directories</div><div>; browseable = no</div><div><br></div><div># By default, the home directories are exported read-only. Change the</div><div># next parameter to 'no' if you want to be able to write to them.</div><div>; read only = yes</div><div><br></div><div># File creation mask is set to 0700 for security reasons. If you want to</div><div># create files with group=rw permissions, set next parameter to 0775.</div><div>; create mask = 0700</div><div><br></div><div># Directory creation mask is set to 0700 for security reasons. If you want to</div><div># create dirs. with group=rw permissions, set next parameter to 0775.</div><div>; directory mask = 0700</div><div><br></div><div># By default, \\server\username shares can be connected to by anyone</div><div># with access to the samba server. Un-comment the following parameter</div><div># to make sure that only "username" can connect to \\server\username</div><div># This might need tweaking when using external authentication schemes</div><div>; valid users = %S</div><div><br></div><div># Un-comment the following and create the netlogon directory for Domain Logons</div><div># (you need to configure Samba to act as a domain controller too.)</div><div>;[netlogon]</div><div>; comment = Network Logon Service</div><div>; path = /home/samba/netlogon</div><div>; guest ok = yes</div><div>; read only = yes</div><div>; share modes = no</div><div><br></div><div># Un-comment the following and create the profiles directory to store</div><div># users profiles (see the "logon path" option above)</div><div># (you need to configure Samba to act as a domain controller too.)</div><div># The path below should be writable by all users so that their</div><div># profile directory may be created the first time they log on</div><div>;[profiles]</div><div>; comment = Users profiles</div><div>; path = /home/samba/profiles</div><div>; guest ok = no</div><div>; browseable = no</div><div>; create mask = 0600</div><div>; directory mask = 0700</div><div><br></div><div>[printers]</div><div>comment = All Printers</div><div>browseable = no</div><div>path = /var/spool/samba</div><div>printable = yes</div><div>create mask = 0700</div><div><br></div><div># Windows clients look for this share name as a source of downloadable</div><div># printer drivers</div><div>[print$]</div><div>comment = Printer Drivers</div><div>path = /var/lib/samba/printers</div><div><br></div><div>[Dumbledore-share]</div><div>read only = no</div><div>path = /home/pkaplan/share</div></div></div><div><br></div></div></div></div></body></html>