Running smbclient 2.2.0-alpha2
on Redhat Linux 7.0
I don't have a fully installed samba suite with full setup and really
only use smbclient occasionally like an ftp client. I'm able to
access a win2k and win98 box that way from my linux workstation.
Able to access but not transfer anything to the win98.
Although I can transfer files from/to the win2k box.
I have no passwords set on the win98 shares and so just hit <enter>
when the password prompt is presented:
$ smbclient //chub2/c
params.c:OpenConfFile() - Unable to open configuration file
"/usr/local/samba/lib/smb.conf":
No such file or directory
Can't load /usr/local/samba/lib/smb.conf - run testparm to debug it
added interface ip=xxx.xxx.xxx bcast=xxx.xxx.xxx.255 nmask=255.255.255.0
added interface ip=xxx.xxx.xxx bcast=xxx.xxx.xxx.255 nmask=255.255.255.0
Password: <ENTER>
NOTE: -ed As you can see, I've never even bothered to setup a smb.conf file
smb: \> more AUTOEXEC.BAT
getting file /tmp/smbmore.1043 of size 200 as \
/tmp/smbmore.1043 (10.9 kb/s) (average 10.9 kb/s)
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
[...] snip
path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I5 D1 T2
@SET CLASSPATH=C:\PROGRA~1\PHOTOD~1.0\ADOBEC~1
As you see, I'm able to access stuff fine, But:
smb: \> put test.txt
ERRSRV - ERRaccess (The requester does not have the necessary access
rights within the specified context for the requested function. The
context is defined by the TID or the UID.) opening remote file
\test.txt
Not able to transfer a file.
The discouraging thing here is that none of the stuff mentioned will
lead a user to discovering what is wrong.
`Man smbclient' conains no hits whatever on TID or UID
It does contain hits on `user access' in the form of a repeated
footnote or comment.
Remove the specified directory (user access privi?
leges permitting) from the server.
Create a new directory on the server (user access
privileges permitting) with the specified name.
And several more similar ones.
I have trouble understanding the point of including such a useless
comment that points nowhere.
It also seems some care should be taken that error messages include
keywords that can lead a user to information concerning that error.
Needless to say `help put' is useless in this regard as well.
I've also discovered that my smbclient apparently doesn't know who it
is.
The usual routes to such information all fail.
smbclient --help|grep version <nothing>
smbclient --version <nothing>
smbclient -V <nothing>
smbclient -v <nothing>
Finally culled it from the very bottom of the manpage.
Shouldn't smbclient follow one or more of the above practices?
So what is the trick to simple file transfers?
