linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eve Atley" <eatley@wowcorp.com>
To: 'Jens Knoell' <jens@surefoot.com>
Cc: linux-admin@vger.kernel.org
Subject: Resolved: Best way to enable 'guest' access onto Linux fileserver?
Date: Mon, 28 Mar 2005 11:53:18 -0500	[thread overview]
Message-ID: <00ab01c533b6$a4cc3d00$580aa8c0@lanadmin> (raw)
In-Reply-To: <4241F54F.2020307@surefoot.com>


Thanks for everybody's help. For some reason, after coming back over the
holiday weekend, it just worked. Guests are now able to connect.

Thanks!
Eve

-----Original Message-----
From: linux-admin-owner@vger.kernel.org
[mailto:linux-admin-owner@vger.kernel.org] On Behalf Of Jens Knoell
Sent: Wednesday, March 23, 2005 6:02 PM
To: eatley@wowcorp.com
Cc: linux-admin@vger.kernel.org
Subject: Re: Best way to enable 'guest' access onto Linux fileserver?


Eve Atley wrote:

>Thanks everyone who responded to this question. I have tested it, but 
>still am unable to provide public access, either with or without a 
>password. Perhaps I have set up something incorrectly. Allow me to 
>present what's inside the smb.conf file...
>
>[global]
>        workgroup = WOWCORP
>        netbios name = SERVER
>        server string = WOW corp server
>        encrypt passwords = Yes
>        obey pam restrictions = Yes
>        pam password change = Yes
>        passwd program = /usr/bin/passwd %u
>        passwd chat = *New*password* %n\n *Retype*new*password* %n\n 
>*passwd:*al
>l*authentication*tokens*updated*successfully*
>        unix password sync = Yes
>        log file = /var/log/samba/%m.log
>        max log size = 0
>        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>        os level = 70
>        dns proxy = No
>        hosts allow = 192.168.10. 127.
>        printing = lprng
>        guest account = samba
>        map to guest = Bad User
>
>[home]
>        path = /home
>        invalid users = root bin linux daemon adm sync shutdown halt 
>mail news uucp operator
>        printable = no
>        hide dot files = yes
>        hide files = /.*/
>        admin user = eve
>        writable = yes
>  
>

Which version of samba are you running? If its older than 2.2 you may 
need to add "security = user" to the global section. Also, it may help 
to temporarily set samba to debug mode and see what it tells you when a 
guest connects.

J
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2005-03-28 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 10:27 how to protect against peer-to-peer? Luca Ferrari
2004-11-22 13:02 ` urgrue
2004-11-22 13:39 ` Adam Lang
2004-11-22 13:53   ` Adrian C.
2004-11-22 13:57     ` Adrian C.
2005-02-12  1:01     ` RH Ent. 3.0 = no support for firewire HD? Eve Atley
2005-03-22 19:49     ` Best way to enable 'guest' access onto Linux fileserver? Eve Atley
2005-03-22 20:09       ` Grant Coady
2005-03-23 16:15       ` Jens Knoell
2005-03-23 21:10         ` Eve Atley
2005-03-23 23:01           ` Jens Knoell
2005-03-28 16:53             ` Eve Atley [this message]
2004-11-22 15:53 ` how to protect against peer-to-peer? Jens Knoell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00ab01c533b6$a4cc3d00$580aa8c0@lanadmin' \
    --to=eatley@wowcorp.com \
    --cc=jens@surefoot.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).