smbclient: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
Juhani Jaakola
long time. Today I installed Samba 2.0.6 on Unixware and tried to use
smbclient in exactly the same way on it, but I get the following error:
session setup failed: ERRDOS - ERRnoaccess (Access denied.)
The target machine is a NT4 box.
On Unisys SVR4 smbclient 1.9.x prints the following:
Can't load /usr/local/samba/lib/smb.conf - run testparm to debug it
Unable to open configuration file "/usr/local/samba/lib/smb.conf"!
pm_process retuned false
Added interface ip=193.240.55.10 bcast=193.240.55.255
nmask=255.255.255.0
Got a positive name query response from 193.240.55.11 (194.240.55.11)
Server time is Wed Jan 5 13:23:32 2000
Timezone is UTC+2.0
Domain=[XXX] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
On Unixware smbclient 2.0.6 prints the following:
params.c:OpenConfFile() - Unable to open configuration file
"/usr/local/samba/!
No such file or directory
Can't load /usr/local/samba/lib/smb.conf - run testparm to debug it
added interface ip=193.240.55.13 bcast=193.240.55.255
nmask=255.255.255.0
session setup failed: ERRDOS - ERRnoaccess (Access denied.)
The command is (I have tried several variations):
smbclient //server/share password -U Administrator -W XXX -c dir
uname -a gives:
UnixWare akuankka 5 7.0.1 i386 x86at SCO UNIX_SVR5
What exactly does the error mean? How can I correct it?
Juhani Jaakola
all-lowercase password in the 2.0.6 version - and it started working! This
is really surprising, because with the older version 1.9.x (which has been
working for a long time and still works) I used different capitalization
for the password. Really weird...
Andrew Williams
possibilities. If it does not help, bump your debug level up and look at the
logfiles.
Sean Riley wrote:
> I am having the same issue (kind of). It has been driving me crazy for a few
> days. I use RH 6.0, with Samba 2.0.5a. I can attach to my Linux SMB shares
> like a champ, from other machines. I have tested nmb, smb and both seem to
> be operational and have no issues.
>
> I can attach to Linux Samba SMB shares (1.9 something) with absolutely no
> problems, but NT 4.0 mounts and smbclient connections bomb on authentication
> wityh the ERRDos message below. I can list empty data regarding NT 4.0 from
> a smbclient -L <server> -N (no shares available for non logged in, no guest
> account, shows communication), but if I try to use my user name (9 characters
> ??? could this be the problem ??) and password I get a failed login attempt
> with smbclient and smbmount.
>
> It almost seems like the password is not being encrypted before being sent to
> the NT server. I have turned on encryption from the generic smb.conf but
> this seems to only govern the way in which the SMB server handles passwords
> not the client.
>
> I am at a loss, I tried changing my password to all lowercase based on this
> note, but it didn't work for me. :-(
>
> Does anyone have a clue ( UI have read the docs, the txt's and have medium
> experience with Linux) anything will be appreciated.
>
> SR
--
Mielipiteet omiani - Opinions personal, facts suspect, especially on my
http://home.germany.net/101-69082/samba.html
Simple Samba Solutions web page ICQ 1722461
Sean Riley
tracy...@bourns.com
I have been having a simular problem for MONTHS with smbmount, and tried the
same things you did to get it to work. Smbmount 1.9x has worked for me in the
past , but smbmount 2.0.5a has been a pain in my back side! I have even used the
-d [number from 1-9] switch to list additional information on why smbmount
failed, but the information listed was not of much use.
After months of intermitant troubleshooting, moments ago I had success! I
had contacted the IS department last week to see if they would look at their log
to try to find out what I was missing in my parameter list on smbmount. The IS
department looked through their logs, and found that smbmount tries to use the
workgroup specified after -W as the domain!!! Why? I don't know!
Since smbmount 2.0.5a has no parameter for specifiying the domain, I used
"smbmount //server/service /mnt -U USERNAME%PASSWORD -W DOMAIN" where the DOMAIN
is the name of the domain that you are logging into, and NOT the workgroup, let
me repete, NOT THE WORKGROUP! This WORKED! I could hardly believe it! It mounted
the NT share first time - No problem!
I hope this is a solution to the problem in genereal, and I hope this
solution works for you!
TSJ
Sean Riley
exuberence from deja.com, but it never went through. Ah well.....
Courious, is your NT domain architecture a multiple master domain model ? Because
in addition to changing the version of samba, we also have changed the NT domain
structure from a single domain to a multiple master, and my account is not in the
domain the servers are in.