user". Try changing it to "security = share" (that is, add a line that
says that under the [global] section) to see if the behavior changes.
The "map to guest" setting might be worth playing with, if you prefer
to leave it on "security = user" or "security = share" doesn't yield
you any better behavior.
<blockquote>
Note that this parameter is needed to set up "Guest" share
services when using security modes other than share and
server. This is because in these modes the name of the
resource being requested is not sent to the server until after
the server has successfully authenticated the client so the
server cannot make authentication decisions at the correct
time (connection to the share) for "Guest" shares. This param�
eter is not useful with security = server as in this security
mode no information is returned about whether a user logon
failed due to a bad username or bad password, the same error
is returned from a modern server in both cases.
</blockquote>
If you run a "man smb.conf" you'll get to see the reason Samba causes
headaches, the settings are organized alphabetically and thoroughly
explained.
Enjoy. :-)
Simón
P.S. The XP machines that do work, even if they log in automatically,
MUST have a username; do you know what that username is?
On Wed, Sep 3, 2008 at 5:15 PM, Mark Warner <markwarner1954@att.net> wrote:
>
> Here's a copy of the existing smb.conf:
>
*snip!*
>
> To my untrained eyes, nothing looks amiss. Then again, I dunno nuthin'.
>
> What I don't get is why all the Windows machines in the building (mix of W2K
> and XPp) *except* these two can see and connect to this share. The only
> thing these two have in common (that I can come up with) is that they have
> passworded Windows logins. All the other machines just boot the user
> straight to his desktop.
>
> --
> Mark Warner
_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug
No comments:
Post a Comment