"Zach Young" wrote in message
news:3FB7D398.2050208@netscape.net...
> When try to connect to samba I get this message.
>
> [young@dyoung zach]$ smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_ACCESS_DENIED
> [young@dyoung zach]$
>
>
> I have upgraded to Redhet 9
>

Sounds like a password or user account problem. Can you give us some more
information about your setup.

What kind of info to you need?

I just upgraded to Redhet 9. I would like to make samba work with Win
XP Home

m.marien wrote:
> "Zach Young" wrote in message
> news:3FB7D398.2050208@netscape.net...
>
>>When try to connect to samba I get this message.
>>
>>[young@dyoung zach]$ smbclient '//192.168.1.50/young' -U young
>>added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
>>Password:
>>session setup failed: NT_STATUS_ACCESS_DENIED
>>[young@dyoung zach]$
>>
>>
>>I have upgraded to Redhet 9
>>
>
>
> Sounds like a password or user account problem. Can you give us some more
> information about your setup.
>
>

[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_ACCESS_DENIED
[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
Anonymous login successful
Domain=[MYGROUP] OS=[Unix] Server=[Samba 2.2.7a-security-rollup-fix]
tree connect failed: NT_STATUS_WRONG_PASSWORD
[root@dyoung samba]#

smb.conf

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings
=====================================
[global]
log file = /var/log/samba/%m.log
protocol = NT1
smb passwd file = /etc/samba/smbpasswd
load printers = yes
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*passwd:*all*authentication*tokens*updated*success fully*
socket options = SO_KEEPALIVE SO_BROADCAST TCP_NODELAY
SO_SNDBUF=8192 SO_RCVBUF=8192
obey pam restrictions = yes
encrypt passwords = no
passwd program = /usr/bin/passwd %u
wins support = true
dns proxy = no
netbios name = SUNDROP
printing = cups
default = YOUNG
unix password sync = Yes
remote announce = 192.168.1.0/MYGROUP
workgroup = MYGROUP
os level = 20
printcap name = /etc/printcap
security = user
max log size = 0
pam password change = yes



[young]
path = /young

"Matt Jones" wrote in message
news:3FB8451C.8090209@hotmail.com...
> [root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_ACCESS_DENIED
> [root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> Anonymous login successful
> Domain=[MYGROUP] OS=[Unix] Server=[Samba 2.2.7a-security-rollup-fix]
> tree connect failed: NT_STATUS_WRONG_PASSWORD
> [root@dyoung samba]#
>

Sorry about not specifying what info is needed. The smb.conf file and the
types of computers you are trying to connect with is the most helpful
information.

I put this conf file into my system and it works. I have to change the
encrypt passwords = yes or it denys access to my XP Pro system, but I can
connect using smbclient. The error you have still points to a user account
or password problem. A couple of things to check. There has to be a
Linux/Unix user account with the same name as the Samba user. The passwords
can be different. The account name must be all lower case (Samba thing), but
the password can be any combination.

> smb.conf
>
> # This is the main Samba configuration file. You should read the
> # smb.conf(5) manual page in order to understand the options listed
> # here. Samba has a huge number of configurable options (perhaps too
> # many!) most of which are not shown in this example
> #
> # Any line which starts with a ; (semi-colon) or a # (hash)
> # is a comment and is ignored. In this example we will use a #
> # for commentry and a ; for parts of the config file that you
> # may wish to enable
> #
> # NOTE: Whenever you modify this file you should run the command
"testparm"
> # to check that you have not made any basic syntactic errors.
> #
> #======================= Global Settings
> =====================================
> [global]
> log file = /var/log/samba/%m.log
> protocol = NT1
> smb passwd file = /etc/samba/smbpasswd
> load printers = yes
> passwd chat = *New*password* %n\n *Retype*new*password* %n\n
> *passwd:*all*authentication*tokens*updated*success fully*
> socket options = SO_KEEPALIVE SO_BROADCAST TCP_NODELAY
> SO_SNDBUF=8192 SO_RCVBUF=8192
> obey pam restrictions = yes
> encrypt passwords = no

All newer versions of windows require encrypt passwords = yes

> passwd program = /usr/bin/passwd %u
> wins support = true
> dns proxy = no
> netbios name = SUNDROP
> printing = cups
> default = YOUNG
> unix password sync = Yes
> remote announce = 192.168.1.0/MYGROUP
> workgroup = MYGROUP
> os level = 20
> printcap name = /etc/printcap
> security = user
> max log size = 0
> pam password change = yes
>
>
>
> [young]
> path = /young
>

[young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_ACCESS_DENIED
[young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_LOGON_FAILURE
[young@dyoung samba]$

I am login into the Red Hat box that is running samba. I am just trying
to run smbcliet on the server. I figure if this is not working it will
not work on the XP. When I try to login onto the Windows box I can do that.

see
[young@dyoung samba]$ smbclient '//zyoung/dara' -U zach
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Got a positive name query response from 127.0.0.1 ( 192.168.1.100 )
Password:
Domain=[MSHOME] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
smb: \>

the error message with the correct password
[young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_ACCESS_DENIED

the error message with wrong correct password
[young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_LOGON_FAILURE
[young@dyoung samba]$

I have delete the smbpasswd and run smbpasswd -a young but still getting
error message.


m.marien wrote:
> "Matt Jones" wrote in message
> news:3FB8451C.8090209@hotmail.com...
>
>>[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
>>added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
>>Password:
>>session setup failed: NT_STATUS_ACCESS_DENIED
>>[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
>>added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
>>Password:
>>Anonymous login successful
>>Domain=[MYGROUP] OS=[Unix] Server=[Samba 2.2.7a-security-rollup-fix]
>>tree connect failed: NT_STATUS_WRONG_PASSWORD
>>[root@dyoung samba]#
>>
>
>
> Sorry about not specifying what info is needed. The smb.conf file and the
> types of computers you are trying to connect with is the most helpful
> information.
>
> I put this conf file into my system and it works. I have to change the
> encrypt passwords = yes or it denys access to my XP Pro system, but I can
> connect using smbclient. The error you have still points to a user account
> or password problem. A couple of things to check. There has to be a
> Linux/Unix user account with the same name as the Samba user. The passwords
> can be different. The account name must be all lower case (Samba thing), but
> the password can be any combination.
>
>
>>smb.conf
>>
>># This is the main Samba configuration file. You should read the
>># smb.conf(5) manual page in order to understand the options listed
>># here. Samba has a huge number of configurable options (perhaps too
>># many!) most of which are not shown in this example
>>#
>># Any line which starts with a ; (semi-colon) or a # (hash)
>># is a comment and is ignored. In this example we will use a #
>># for commentry and a ; for parts of the config file that you
>># may wish to enable
>>#
>># NOTE: Whenever you modify this file you should run the command
>
> "testparm"
>
>># to check that you have not made any basic syntactic errors.
>>#
>>#======================= Global Settings
>>=====================================
>>[global]
>> log file = /var/log/samba/%m.log
>> protocol = NT1
>> smb passwd file = /etc/samba/smbpasswd
>> load printers = yes
>> passwd chat = *New*password* %n\n *Retype*new*password* %n\n
>>*passwd:*all*authentication*tokens*updated*success fully*
>> socket options = SO_KEEPALIVE SO_BROADCAST TCP_NODELAY
>>SO_SNDBUF=8192 SO_RCVBUF=8192
>> obey pam restrictions = yes
>> encrypt passwords = no
>
>
> All newer versions of windows require encrypt passwords = yes
>
>
>> passwd program = /usr/bin/passwd %u
>> wins support = true
>> dns proxy = no
>> netbios name = SUNDROP
>> printing = cups
>> default = YOUNG
>> unix password sync = Yes
>> remote announce = 192.168.1.0/MYGROUP
>> workgroup = MYGROUP
>> os level = 20
>> printcap name = /etc/printcap
>> security = user
>> max log size = 0
>> pam password change = yes
>>
>>
>>
>>[young]
>> path = /young
>>
>
>
>

"Matt Jones" wrote in message
news:3FB8D19D.9010907@hotmail.com...
> [young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_ACCESS_DENIED
> [young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_LOGON_FAILURE
> [young@dyoung samba]$
>
> I am login into the Red Hat box that is running samba. I am just trying
> to run smbcliet on the server. I figure if this is not working it will
> not work on the XP. When I try to login onto the Windows box I can do
that.
>
> see
> [young@dyoung samba]$ smbclient '//zyoung/dara' -U zach
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Got a positive name query response from 127.0.0.1 ( 192.168.1.100 )
> Password:
> Domain=[MSHOME] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
> smb: \>
>
> the error message with the correct password
> [young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_ACCESS_DENIED
>
> the error message with wrong correct password
> [young@dyoung samba]$ smbclient '//192.168.1.50/young' -U young
> added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> session setup failed: NT_STATUS_LOGON_FAILURE
> [young@dyoung samba]$
>
> I have delete the smbpasswd and run smbpasswd -a young but still getting
> error message.
>


Ok - I was close, but no prize. It looks like an account problem but I can't
duplicate it exactly. From my smb.conf file:

[young]
path = /tmp/test

[root@amos-rh tmp]# ls -ld test
drwx------ 2 mm users 4096 Nov 17 17:25 test

[root@amos-rh mm]# smbclient //sundrop/young -U guest
Password:
Anonymous login successful
tree connect failed: NT_STATUS_ACCESS_DENIED

I can get the same error, but for the wrong reason: "tree connect failed"
rather than "session setup failed". The session setup probably happens
before the tree connect, most likely during or after authentication. But
then that suggests an account problem.

Anybody else ?

>
> m.marien wrote:
> > "Matt Jones" wrote in message
> > news:3FB8451C.8090209@hotmail.com...
> >
> >>[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
> >>added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> >>Password:
> >>session setup failed: NT_STATUS_ACCESS_DENIED
> >>[root@dyoung samba]# smbclient '//192.168.1.50/young' -U young
> >>added interface ip=192.168.1.50 bcast=192.168.1.255 nmask=255.255.255.0
> >>Password:
> >>Anonymous login successful
> >>Domain=[MYGROUP] OS=[Unix] Server=[Samba 2.2.7a-security-rollup-fix]
> >>tree connect failed: NT_STATUS_WRONG_PASSWORD
> >>[root@dyoung samba]#
> >>
> >
> >
> > Sorry about not specifying what info is needed. The smb.conf file and
the
> > types of computers you are trying to connect with is the most helpful
> > information.
> >
> > I put this conf file into my system and it works. I have to change the
> > encrypt passwords = yes or it denys access to my XP Pro system, but I
can
> > connect using smbclient. The error you have still points to a user
account
> > or password problem. A couple of things to check. There has to be a
> > Linux/Unix user account with the same name as the Samba user. The
passwords
> > can be different. The account name must be all lower case (Samba thing),
but
> > the password can be any combination.
> >
> >
> >>smb.conf
> >>
> >># This is the main Samba configuration file. You should read the
> >># smb.conf(5) manual page in order to understand the options listed
> >># here. Samba has a huge number of configurable options (perhaps too
> >># many!) most of which are not shown in this example
> >>#
> >># Any line which starts with a ; (semi-colon) or a # (hash)
> >># is a comment and is ignored. In this example we will use a #
> >># for commentry and a ; for parts of the config file that you
> >># may wish to enable
> >>#
> >># NOTE: Whenever you modify this file you should run the command
> >
> > "testparm"
> >
> >># to check that you have not made any basic syntactic errors.
> >>#
> >>#======================= Global Settings
> >>=====================================
> >>[global]
> >> log file = /var/log/samba/%m.log
> >> protocol = NT1
> >> smb passwd file = /etc/samba/smbpasswd
> >> load printers = yes
> >> passwd chat = *New*password* %n\n *Retype*new*password* %n\n
> >>*passwd:*all*authentication*tokens*updated*success fully*
> >> socket options = SO_KEEPALIVE SO_BROADCAST TCP_NODELAY
> >>SO_SNDBUF=8192 SO_RCVBUF=8192
> >> obey pam restrictions = yes
> >> encrypt passwords = no
> >
> >
> > All newer versions of windows require encrypt passwords = yes
> >
> >
> >> passwd program = /usr/bin/passwd %u
> >> wins support = true
> >> dns proxy = no
> >> netbios name = SUNDROP
> >> printing = cups
> >> default = YOUNG
> >> unix password sync = Yes
> >> remote announce = 192.168.1.0/MYGROUP
> >> workgroup = MYGROUP
> >> os level = 20
> >> printcap name = /etc/printcap
> >> security = user
> >> max log size = 0
> >> pam password change = yes
> >>
> >>
> >>
> >>[young]
> >> path = /young
> >>
> >
> >
> >
>

Does smbpasswd & passwd require a machine account as well as the normal user
account?
Bill in Sacramento, California....

"Bill" wrote in message
news:20031124004545.28890.00000840@mb-m17.aol.com...
> Does smbpasswd & passwd require a machine account as well as the normal
user
> account?
> Bill in Sacramento, California....

Yes - but only for systems that can join the domain. The machine account in
smbpasswd is created on the fly when you join, but you need a matching
machine account in the passwd file.

However, looking back on his smb.conf file he is using security = USER, but
without a domain so the machine accounts aren't required. I think he wants
to share with a WinXP Home system. The Samba system can authenticate and
access the WinXP system. It just can't authenticate to itself ?