SAMBA keeps being a mistery

Hi all,

I have been working for a number of years now with Suse utilizing an
according number of different versions during this time.

Although I most times managed somehow to configure the respective SAMBA
versions coming along with these SUSE versions in a way that I eventually
could access my defined shares I never got rid of the gut feeling telling
me that I did not really have full control of my SAMBA installation.

This is because SAMBA configuration seems to be extremely difficult and
versatile. Although there are by far more than 900 pages of SAMBA docu
available there is no quick "getting started" chapter that guarantees a
successful sharing of a simple folder.


So this is another request for support:

I simply want to share 2 folders
/partitions/sda3/Transfer
/home/christian/Desktop/Transfer2Christian/

If I use the KDE network browser, my PC "anschux" and its shares...

groups ( created by the system )
netlong ( created by the system )
Transfer ( created by me )
Transfer2Christian ( created by me )


.... will be displayed. When clicking e.g. on the netlogon share symbol a
login dialog pops up asking me for the respective account data. So far, so
good.

But clicking on the share symbols "Transfer" and "Transfer2Christian"
respectively causes the following error messages ( but no login dialog )
showing up:
"File or folder smb://anschux/Transfer does not exist"
and
"File or folder smb://anschux/Transfer2Christian does not exist"


What goes wrong? What do I have to do to get the expected network access to
my shares "Transfer" and "Transfer2Christian" ?

Here is the content of smb.conf
#### Start smb.conf ####
# 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: 2006-11-27
[global]
workgroup = INTRANET
printcap name = cups
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 = Yes
domain master = Yes
os level = 65
preferred master = Yes
usershare max shares = 100
security = user
local master = Yes
netbios name = anschux

## Share disabled by YaST
# [homes]
# comment = Home Directories
# valid users = %S, %D%w%S
# browseable = No
# read only = No
# inherit acls = Yes
[transfer2christian]
comment = Network Profiles Service
path = /home/christian/Desktop/Transfer2Christian/
create mask = 0600
directory mask = 0744
valid users = christian,firma
write list = christian,firma
case sensitive = no
strict locking = no
msdfs proxy = no
guest ok = yes
max connections = 1
read only = no

## Share disabled by YaST
# [users]
# comment = All users
# path = /home
# read only = No
# inherit acls = Yes
# veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root

[transfer]
comment = Allgemeiner Transferordner auf sda3
inherit acls = yes
path = /partitions/sda3/Transfer
write list = christian,firma
case sensitive = no
strict locking = no
msdfs proxy = no


#### end smb.conf ###

Please note:
sda3 is a separate partion mounted at /partitions/sda3
home is a separate partion mounted at /home

What versions of opensuse and samba are you running?
--
bd
NSC Volunteer SysOp

> What versions of opensuse and samba are you running?
> --
> bd
> NSC Volunteer SysOp
>
Sorry, I forgot.

I have the latest 64-Bit version of OpenSUSE 10.2 with the latest patches.

It is a new installAtion - NO UPGRADE from a previous version! ( i.e. I
opted for formatting the root partition and for a brand new system.)

Christian@Anschuetz.de wrote:

> Sorry, I forgot.
>
> I have the latest 64-Bit version of OpenSUSE 10.2 with the latest patches.
>
> It is a new installAtion - NO UPGRADE from a previous version! ( i.e. I
> opted for formatting the root partition and for a brand new system.)
>
OK, I can duplicate the problem here, and seemingly solve it by removing the
'msdfs proxy = no' parameter from your smb.conf file. I'm not sure what
that line does -- hopefully it's not essential to your intended
configuration.
--
bd
NSC Volunteer SysOp

> Christian@Anschuetz.de wrote:
>
> > Sorry, I forgot.
> >
> > I have the latest 64-Bit version of OpenSUSE 10.2 with the latest patches.
> >
> > It is a new installAtion - NO UPGRADE from a previous version! ( i.e. I
> > opted for formatting the root partition and for a brand new system.)
> >
> OK, I can duplicate the problem here, and seemingly solve it by removing the
> 'msdfs proxy = no' parameter from your smb.conf file. I'm not sure what
> that line does -- hopefully it's not essential to your intended
> configuration.
> --
> bd
> NSC Volunteer SysOp
>
Now it works. Thank you for your competent and quick support.!

Now I am wondering why I was the first to report the problem. I assumed
that there are more people outside who wished to deploy a share volume on
their PC....


Is it a bug ? Who should be made aware of it?
Who knows the meaning of "msdfs proxy = no"?
I am a little bit concerned about it because this option has never been
chosen or configured consciuously by me... Everybody will encounter the
same problem.

Christian@Anschuetz.de wrote:

> Who knows the meaning of "msdfs proxy = no"?
>
That's a good question... I did a quick search and found lots of examples
which included it, but nothing that explained it.

> Is it a bug ? Who should be made aware of it?
>
It looks like it this point, but without knowing more, it's hard to say for
sure. Bugs can be reported at bugzilla.novell.com.

> I am a little bit concerned about itÂ*Â*becauseÂ*thisÂ*optionÂ*hasÂ*neverÂ*been
> chosen or configured consciuously by me...
>
Exactly how did you create your shares?
--
bd
NSC Volunteer SysOp

Christian@Anschuetz.de wrote:
[...]
> Who knows the meaning of "msdfs proxy = no"?
[...]

man smb.conf will tell you.


B

--
http://www.mailtrap.org.uk/

numpty@1.novell.mailtrap.org.uk wrote:

> man smb.conf will tell you.
>
>
> B
>
Thanks for that. Interesting that the default is supposed to be no, but
commenting out 'msdfs = no' is what fixed things in this case.
--
bd
NSC Volunteer SysOp

The Suse samba manager is list-like module... I think is not intuitive.
In the past Suse works with a web-admin for Samba. A web interface allow
to manage shares, users.

josepe wrote:

> The Suse samba manager is list-like module... I think is not intuitive.
> In the past Suse works with a web-admin for Samba. A web interface allow
> to manage shares, users.
Yeah, I think webmin can manage it. I usually just edit the conf file to
include what I need, then I don't get extraneous junk in there that some
program thinks I need.
--
bd
NSC Volunteer SysOp