https://bugzilla.novell.com/show_bug.cgi?id=272041 Summary: Yast2-SMB server doesn't share drives ! Product: openSUSE 10.3 Version: Alpha 3plus Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: al4321@gmail.com QAContact: qa@suse.de I have seen that Yast2-SMB server module is basically useless, because it creates incorrect configuration that _prevents_ sharing of data ! This is true of both openSUSE 10.2 and 10.3 Alpha3 systems. To make anything useful, I had to use SWAT, and then hand-tune the result smb config files. Now a question: why we have a Yast-SMB module, if it doesn't works ? Let's compare that what was auto-generated by Yast-SMB with something hand-tuned: The SMB-Yast autogenerated thing: ============================================================================= # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the # samba-doc package is installed. # Date: 2007-04-06 [global] workgroup = WORKGROUP printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = Yes add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No security = user [homes] comment = Home Directories valid users = %S, %D%w%S browseable = No read only = Yes inherit acls = Yes [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [boot] inherit acls = Yes path = /boot read only = No ================================================================================= This is the SWAT-based, but hand tunes configuration: ================================================================================= # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2007/04/12 05:58:44 [global] workgroup = MSHOME server string = openSUSE security = SHARE map to guest = Bad User guest account = root printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile domain master = No usershare allow guests = Yes usershare max shares = 100 cups options = raw include = /etc/samba/dhcp.conf [homes] comment = Home Directories valid users = %S, %D%w%S read only = No inherit acls = Yes browseable = No [users] comment = All users path = /home/ read only = No inherit acls = Yes guest ok = Yes veto files = /aquota.user/groups/shares/ [E] path = /E/ guest ok = Yes store dos attributes = Yes [F] path = /F/ read only = No guest ok = Yes ================================================================================= Do you see the difference ? 1. security must be =SHARE I want to have a Desktop operating system, with easy sharing. 2. map to guest = Bad User guest account = root This means that RW shares are really RW. By default Yast, I can *not* make RW shares. They look like RW in Yast, but in reality they are RO or nothing at all. 3. server string = openSUSE This is something every Windows user will see when accessing openSUSE server. giving something short like "openSUSE" is much better than something like: samba-1.2.3.4-xx-yy-zz-endlessstring that Yast gives by default. Totals: the default Yast-SMB module gives totally unusable results, that you can never connect to, from a real Windows system. This module must become easier to use, and build more basic config files, that _work_. -Alexey "Technologov" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.