similar to: Hints for bad smbclient-2.0.3 put performance (Go back to 1.9.18p10!)

Hi, I've had extremely bad smbclient put performance when connecting from my Linux box to a Windows 95 box. I only get about 10KBytes/s! All other forms of data transfer work fine, and I get from 600-700KBytes/s. This is on a local 10BT LAN. I've seen a few other reports of this, but no solutions as of yet. smbclient does puts just fine to another Linux/Samba Server. I'm using

STEP 6. Try listing the shares available on your server k6:/usr/sbin# smbclient -L k6 Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such file or di rectory Server time is Wed May 5 18:35:46 1999 Timezone is UTC-4.0 Session setup failed for username= myname=K6 destname=K6 ERRSRV - ERRbadpw (Ba d

Hi ! I have a problem with samba that I cannot seem to solve: smbclient put it extremely slow. I am setting up a two-computer home network, with a '95 client (also print server), and a Linux 2.2.0-pre8 server, using samba-2.0. I've finished the setup, and most things work fine. However, I noticed that doing a 'put' with smbclient is extremely slow. I've read the

I am trying to use smbclient to migrate data from OS/2 LanServers to a filesystem on an AIX 4.3.1 machine. Everything works great except renaming directories on the OS/2 LanServer. I get the error ERRDOS - ERRbadfile (File not found.) renaming files when I do a "rename <existing_dir_name> <new_dir_name>" at the prompt, but <existing_dir_name> exists. I connected to a

Greetings- We use smbclient -M to send a Message of the Day to clients every once in a while. The clients are NT4 (SP3), and the server is Samba 1.9.19-prealpha. However, the same problem appears with version 2.0.0. The issue is: once the file to be sent exceeds approximately 675 bytes (smbclient reports sending 975 bytes, presumably including some overhead), the message turns up blank on the

The Samba Team are pleased to announce Samba 1.9.18p10. Note that the 1.9.18p9 code was not distributed due to a problem discovered during the final QA testing phase. However, in order not to allow any confusion about versions the Samba Team are upping the patch revision number to ensure we can identify a particular release of code exactly. It may be fetched via ftp from :

I've already posted about this to the samba list and samba-bugs (19990301); no response, so I retry here. A win95 pc, and a linux 2.0.33 with: 1) smbclient1.9.18 (patched to restore subdirs) 2) a patched smbclient2.0.2 or smbclient2.0.3. On the win95 pc there's a share, this share contains a dir with: MB 4 Files 142 Subdirs 2 Tarring from the pc to the linux box takes: 1.9.18: 10sec

-------- --Multipart_Thu_Apr__8_13:33:51_1999-1 Content-Type: text/plain; charset=US-ASCII Hello guys, I always wondered why smbclient keeps timestamp in `put'ting a file but does not keep it in `get'ting a file. Alternative to keep the time stamp in `get'ting file is to use -Tc option or smbtar script, but they are a bit hairy for interactive use, and it can only dump files with an

Hi list, I'm using Samba 3.0.21 on a FC4 box. When copying files using smbclient I get huge speed differences between put and get commands. smb: \> put backup.tar putting file backup.tar as \backup.tar (543.0 kb/s) (average 543.0 kb/s) smb: \> get backup.tar getting file \backup.tar of size 31549440 as backup.tar (7681.4 kb/s) (average 7681.4 kb/s) smb: \> put backup.tar

Hi, All I'm brand new to the list, and here's what's going on: I am running samba 1.9.18 on a RedHat Linux box (RH release 5.2). Samba was installed via RPM rather than built locally. While configuring smbd for a different purpose than I write about here, I discoverd smbtar. It struck me that this might prove a useful tool for backing up an NT mail-server (icky, I know) from a

Hi, I have reciently been attempting to connect an OS\390 system to a windows file server using the smbclient program that is part of the MVS port of samba. The problem I have encountered is this. When I try to connect from MVS to windows without a password I can connect with no problem at all. Files transfer fine and the encoding is fine. However the moment that i put a password on the

Since the release of the first 2.0.x (jan1999) I noted that smbclient '\\server\share' -Tx filename.tar was terribly slow. smbclient '\\server\share' -Tc filename.tar is as fast as 1.9.18. If I use smbclient from 1.9.18 the performance is high (with the same target pc). These are some tests with: - Win98pc - lan 10Mbps - samba-2.0.5-pre4/rh60 - a dir containing 1,2MB in 52

All, With the belief that, "given enough eyes all bugs are shallow", I submit the following to the list. I had sent a shorter version to samba-bugs last week, but, given the nature of this problem, I think everyone needs to check this on their own systems. Overview: Pulling files from an NT 4.0 machine to a RedHat 5.0 linux box using 2.0.3 or 2.0.4b smbclient *consistently* results in

jimd@gie.com wrote: > > Overview: > Pulling files from an NT 4.0 machine to a RedHat 5.0 linux box using > 2.0.3 or 2.0.4b smbclient *consistently* results in randomly corrupt > files, with no error message to indicate internal file corruption. We > are able to recreate this problem on all manners of servers and > workstations running NT 4.0, and all manner of linux boxen

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 \* <=======

Dear *, I have to perform an ANOVA analysis to study the effects on the performance of some algorithmic components in the design of my algorithm. I have done a full factorial design for the following 5 factors (my response variable is "best"): $ model :'data.frame': 3360 obs. of 6 variables: ..$ best : num [1:3360] 0.108 0.573 0.625 1.057 0.451 ...

The Wine development release 1.9.19 is now available. What's new in this release (see below for details): - Initial version of a udev bus driver for HID. - Various improvements in joystick support. - Initial implementation of DC rendering in Direct2D. - Improved metafile support in GDI+. - Various bug fixes. The source is available from the following locations:

The Samba Team are pleased to announce Samba 1.9.18p1. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p1.tar.gz This is a bugfix release, designed to address issues that users have reported with the 1.9.18 major release. Due to an oplock problem in 1.9.18 (fixed in this release) that could cause data loss in certain circumstances, it is recommended that all

Hello, I'm trying to track a possible bug. I'm running samba 2.0.3 on Solaris 2.5.1 (with current patches), and I am having a problem that came up overnight. We use a single global name mangle {mangled map = Makefile makefile.unx} that has been working just fine for years, and now it fails. We build software on the unix side and on the PC side and use different make files for the

smbclient can create GNU tar files with long file names, but cannot restore them. The included patch will rectify this. This patch is against 1.9.18.p4. -Rob -- Rob Riggs Devil's Thumb Entertainment Network Administrator Boulder, CO - (303) 938-1200 rob@DevilsThumb.COM http://www.DevilsThumb.COM/~rob "The notion of errors is