Does the share you're after show up if you do a

smbclient -L peon

(no username)

What happens if you use administrator rather than sgrover to authenticate?

Why are you using security = domain?  I don't really think there's ever a
use for that, except MAYBE (and I doubt it here too) if you're wanting to
authenticate to an NT domain.

I'd go with security = user.  Then get rid of the password server = snow
line entirely.  For 99% of people, security will always be = user.  The
other options are only there to be confusing...  :)  (I learned it the hard
way).

I'm assuming that you have this box running as your PDC (that's how it's
set).  If you need "password server" (and I don't think you do), I'd
recommend ALWAYS using "= *".  This will be easier to maintain down the
road, as it will determine who the PDC is based on NMB traffic.  On your PDC
though, you don't need to specify a password server anyway.

Kev.


----- Original Message -----
From: "Shawn" <[EMAIL PROTECTED]>
To: "CLUG (E-mail)" <[EMAIL PROTECTED]>
Sent: Monday, November 10, 2003 10:15 PM
Subject: (clug-talk) Samba Help?


> Hi all.
>
> I have Samba 2.2.8 setup on my server, and it is serving as my domain
> controller.  It works great in that I can connect to shares on the Linux
> server from my windows pc.  But....
>
> Today, I have the need to reverse the connection - connect to a windows
> share from the linux server.  This is failing miserably.  I've browsed the
> web and made various tweaks to my smb.conf file, but still no luck...
>
> Here's the Globals section of my smb.conf file:
>
> [global]
>         workgroup = O2S
>         netbios name = SNOW
>         server string = Server Snow
>         security = DOMAIN
>         encrypt passwords = Yes
>         password server = snow
>         log level = 1
>         log file = /var/log/samba/%m.log
>         max log size = 50
>         socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>         domain admin group = @sysadmin
>         add user script = /usr/sbin/useradd -d /dev/null -g 100 -s
> /bin/false %u
>         logon script = login.cmd
>         logon drive = h:
>         domain logons = Yes
>         os level = 64
>         preferred master = Yes
>         domain master = Yes
>         dns proxy = No
>         admin users = @sysadmin root sgrover
>
> I'm trying to hook up a share on a Win2k box, where I have both a local
and
> network user account, both with the same username (sgrover), and password.
> This name has been set via smbpasswd, and also matches my shell account.
>
> Here's some sample output:
>
> Try 1:
> snow root # smbclient -L peon -U sgrover
> added interface ip=192.168.0.15 bcast=192.168.0.255 nmask=255.255.255.0
> Got a positive name query response from 192.168.0.20 ( 192.168.0.20 )
> Password:
> session setup failed: NT_STATUS_LOGON_FAILURE
>
> Try 2:
> snow root # smbmount file://peon/backup /root/peon -o
> credentials=//root/smb/cred.txt
> INFO: Debug class all level = 1   (pid 2458 from pid 2458)
> 2458: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
> SMB connection failed
>
> Try 3:
> snow root # mount -t smbfs file://peon/backup /root/peon
> INFO: Debug class all level = 1   (pid 2467 from pid 2467)
> Password:
> 2467: session setup failed: ERRDOS - 2215
> SMB connection failed
>
> A search of my logs shows that it can't find a login server (only for
these
> tests, otherwise, there's no errors....).  I'm thinking the bug is in my
> smb.conf file, but can't really see anything that looks right.  Any guru's
> see anything glaring?
>
> Thanks in advance for any tips.
>
> Shawn
>
>
>

Reply via email to