> I've tested using the smb.conf you provided, which enabled me to narrow
> this
> down to a reproducible test case. The case where this breaks is when
> security = share is set, you're connecting to a [homes] autoshare, *and*
> valid users = %S is set.
>
> Strangely, even though 'valid users' shouldn't be required at all when
> using
> security=share, if I remove the 'valid users' setting from my config I'm
> able to connect to other users' home shares. Otherwise, I would suggest
> this as a workaround.
>
> On the other hand, I'm not sure why you say that setting security=user is
> not the behavior you want. What doesn't work the way you want it to?
> It's
> certainly far more secure than having to enable lanman auth when your
> clients are WinXP...
>
> In any case, I will try to isolate the fix for this bug and forward
> upstream.
Thank you. I removed the "valid users" line from the [homes] share, and I
can connect, too.
In my case, security is not the problem ("home server"), so "security=share"
is the problem. I need this as a workaround, because with "security=user",
you always need a user/password when connecting to the server, even when
only displaying the shares (how can this be disabled)? I want to have some
shares, accessible readable for everyone without authentication (for
MP3-Players etc), but home directories read/writeable with user
authentication. Beyond this bug, do you have a hint for this? "user=share"
was the only solution I got from Google for my problem :-)
Uwe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
