similar to: Scripting smbclient

I'm using smbclient 3.0.22-13.16-SUSE-SLES10. I'm using the smbclientparser Perl module to use smbclient from within my Perl scripts. Whenever I perform a GET on a file, smb outputs this line to stdout: Domain=[mydomain] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] This results in hundreds of mail messages in my local mail queue. How can I turn this off, so that smbclient

Hi I have problem with smbclient in samba3 rc2, rc4. When I start tar backup with it: smbclient //comp-32/volume pass -U user -d0 -Tc /dev/tape0 > /dev/null [2003/09/23 08:27:46, 0] client/clitar.c:do_tar(830) directory \Kart-32\ [2003/09/23 08:27:46, 0] client/clitar.c:do_tar(830) directory \Kart-32\mairs\ [2003/09/23 08:27:46, 0]

We are building smbclient 4.3.3 for Intel, which was working fine. We got a toolchain update, which added the lttng-ust libraries(previously missing in our toolchain), but not lttng/tracef.h and now we get an error in the config.log: Checking for lttng-ust pkg-config --errors-to-stdout --print-errors --cflags --libs lttng-ust Package lttng-ust was not found in the pkg-config search path. Perhaps

Hi out there, I'm facing a problem which drives me nearly nuts... On Solaris 2.6 today I upgraded SAMBA from 2.0.7 to the fresh 2.2.8 from Sunfreeware. Everything works fine - besides the smbclient. I used to use smbclient by some PERL-scripts to transfer huge crowds of files from SUN to some Windblows-boxes. With 2.0.7 everything worked fine for 18 months... As long as I connect to

I've got problems getting files from a win2000 server using smbclient (see subject "SMBClient & Windows 2000"). I've tried using the -b parameter (documented in the online man pages) to change the buffersize in case that might be the problem but the smbclient I'm running doesn't recognise it. I've installed 2.0.7 on Compaq Tru64, smbclient declares itself as

http://bugzilla.mindrot.org/show_bug.cgi?id=542 Summary: OpenSSH 3.6.1p1 - sftp exit codes and improved logging for scripting Product: Portable OpenSSH Version: -current Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: sftp AssignedTo:

I've written a python wrapper around the smbclient program, so that I can list/upload/download from Windows shares. Using smbclient 2.0.9 or Version 2.2.5-2 for Debian, my wrapper works well and is able to control the smbclient process via pipes well. With both smbclient 2.999+3.0cvs20020723-1 and 2.999+3.0.alpha20-3 (on a Debian box) the smbclient responses appear to be not always BEFORE the

I made some tests with smbclient and gzip, and it seems to me that what I'm doing should be safe, but I'd like to know if this kind of input and output redirection has some "hidden" drawbacks/problems: may it cause corruption of output files? backup: smbclient '\\server\share' -Tc - | gzip > file.tar.gz restore: gzip -dc file.tar.gz | smbclient

My systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre3 as 2.0.7 === 1) "ls" of an empty dir 1a) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available 1b) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* <=======

Hi! Seems like I need some help with a really awkward problem I stumbled over today. In a remote access solution I developed, a Perl CGI script accesses a Windows NT 4.0 Server through Filesys::SmbClient and thus libsmbclient. Browsing the shares and the directories works perfectly but as soon as I try to get any file, it fails with a "Permission denied", even if I try it with the

Hi, I'm trying to have a program automate getting a browse list via smbclient -L. I am having a problem with the way it handles passwords. For example, if I run: smbclient -L SERVER Then it prompts for a password. I can just press enter and it will show the shares and browse list. However, if I then try, smbclient -N -L SERVER it gives me access denied. Is there a difference between

Hello Samba Gurus, I am new to samba. I configured samba in an HPUX machine. And when i run smbclient program i got the following error message. # smbclient -U% -L localhost added interface ip=3.209.112.223 bcast=3.209.115.255 nmask=255.255.252.0 Domain=[CADCAM] OS=[Unix] Server=[Samba 2.0.7] tree connect failed: code 0 Can anyone guide me? Thanks in advance, Malar

Hi! I have a problem with smbclient. When I start smbclient (-L switch or in ftp-like mode) it asks me for the password. After entering the password my XP notebook seems to answer with NT_STATUS_DUPLICATE_NAME (at least this is what smbclient tells me on the shell prompt ;-). I don't know what this means. I tried different -d levels but received no useful information. Strange is: 1)

It appears that "smbclient -p <portnumber>" doesn't work as advertised in Samba 2.x? On both Linux 6.2 and Solaris 2.6, independent of firewalls and the like, it works with old Samba (e.g. 1.9.18p10) , but not with new Samba (e.g. 2.0.7). The new version seems to *IGNORE* the port specification and attempt to connect to port 139. Here's the result when I try to send a

This is driving me up the wall. I've had a basic samba server up for a couple of years and it was easy to do. Now with a second server I try to mount the same shares from the new linux box but I can get nothing to work. I would use NFS between the linux boxes but the support isn't compiled into my kernel, and I don't want to tackle that beast tonight... To test I tried the smbclient

Hi Folks! I try to send a popup via "smbclient -M" from a sun (SunOS 5.8, Samba 2.0.7, hostname "sonne") to a WinXP (hostname "dezntmneubeck_x") but it fails. Both machines are in the same physical network. All I get are the following lines: root@sonne(1017)/> smbclient -s /usr/local/samba/lib/smb.conf -M dezntmneubeck_x added interface ip=193.102.105.71

I posted this problem as a question to this list a while ago and got no reply. I submitted it as a bug, but found that "samba-bugs@samba.org", no longer accepts bug reports, even though the web page says to send them to that address. Wondering if the option had been intentionally discontinuted without updating the man page, I made a quick check of the source and found that the "-p

Hi, I'm trying to manage printer queues on a XP box in the lan. Other client commands work well, even echo "test" | smbclient //XPBOX/PRINTER -c "print -" works as expected and starts a print job. But either queue and cancel don't work, without debug flags with no errors. Cancel even says job is deleted. With -d4 I see # smbclient -d3 //volker/HPDJ1120C -U admin

There's a race condition: when a file increases in size when being archived by the tar function in smbclient, the resulting tar file is created with an invalid format. The tar header for the file has the wrong length, and many tar programs will abort when they get to the invalid header/file. I've seen this happen when using smbclient/tar to back up a Win98 computer, and there's

I reported this a few weeks ago. Could someone acknowledge it and confirm that it is on the bug list and will be actioned in due course? Thanks. > -----Original Message----- > From: Koller,Anthony > Sent: 07 April 2000 12:33 > To: 'samba@samba.org' > Subject: smbclient problems with very large files > > > smbclient ls command doesn't like large files (eg