similar to: problem copying large directories from NT 4.0 server to samba server

Jandeep S Kang wrote: > > Hi, > we have installed samba 2.0.0 under solaris. when we try > to copy a large directory around 160MB to a folder on samba > it stops in the middle with a message like "session > cancelled". what is this? did anybody experience the same > behaviour. i assume some setting is wrong in the smb.conf > or is it something else?? >

I'm encountering problems copying files from a Windows NT workstation to a Linux system. Not all of the files are being copied. A week ago I submitted a bug report. The only response was an automated reply acknowledging that the message was received. I'm assuming that they are very busy and have not had time to go through all of the incoming e-mail. Maybe someone here could help, or

Folks -- I've read the FAQ at samba.org/samba/docs/FAQ, I've searched the mailing list archives for "unexpected network error", I've searched Google for "samba unexpected network error", and been unable to find anything. If there's another source of information that I should check, I'd greatly appreciate a pointer. I'm trying to copy files to Samba

At the risk of stating the obvious but 2.2.3a is rather old - try updating to the latest stable 2.2.x series of Samba. After that you might want to look into the options relating to "Oplocks" >>I am wondering if anybody has expected the same problem before? The only idea i have is that this error occures because i have a lot of file and directory, chown, chmod directives in my

Hi all, first i want to say a big "Hello" to the list, since this is my first posting here. Yesterday i just installed another SAMBA server on a middle class (K6-2 500, 128MB) machine. All shares are accessable like expected but i often get an "Can't move file. File in use." error from my W2K client when moving large amount of files to the SAMBA server. This error

This is a problem I get with various versions of Samba, up to and including 2.0.7. (The version shipped with Debian.) I have an NT machine (4.0, service-pack 3 using NTFS) exporting a filesystem to Linux through smbmount. Specific directories are not browsable. By that I mean that "ls *" comes up blank, however if you know the filename, "ls foo.txt" will still find the

I tried upgrading from samba 1.9 to 2.0 on two seperate RedHat servers, and after both upgrades nobody could get authenticated. The windows boxes had the registry hacks to turn off encrypted passwords, and I'm authenticating out of passwd+shadow. I found many similiar posts on DejaNews and in the samba mailing list archives. I broke out strace and found the problem. Samba 2.0 tries to

Hi I'm having trouble with Samba, when I copy large complex directories to my Samba server, the target doesn't match the source, some files seem to be missing. *Stats on source(windows client) are:* Size: 4.99 GB (5,367,477,260 bytes) Size on disk: 5.00 GB (5,376,487,424 bytes) Contains: 4,481 files, 281 folders *Stats on target(Samba server) are:* Size: 4.92 GB (5,286,067,654

mc.broersma@signaal.nl wrote: > So, a simple test case is selecting all 20.000 files and performing a > delete action using the NT client. > The maximum speed is about 3 files/sec and the Samba server is using all > the CPU time for this (only) action from one NT-client. It will take you > hours to complete this command. > > I tried the Samba lock options and tuning

Ever since I upgraded from Samba 1.9.18 to 2.0.0, I've been having problems with applications started from a Samba share dying silently, or with an Illegal Instruction message, on NT 4.0 Workstation. Since the only configuration change has been the Samba upgrade, that would seem to be the orgin of the problem. Below is my smb.conf file, in case I have something configured (or not configured)

When copying files from the Samba server to a Windows95 client or vv, the speed varies dramatically. When I try to copy the same (20MB) file 10 times some times it copies in less than 10 seconds. The next time it takes allmost a minute. And most worrying of all quite often the copying just stops halfway in the middle. The progress bar in Windows just stops. The traffic on the NIC also stops (the

"Marc Remijn" <marrem@IAEhv.nl> write > When copying files from the Samba server to a Windows95 client or vv, > the speed varies dramatically. When I try to copy the same (20MB) file 10 > times > some times it copies in less than 10 seconds. The next time it takes allmost > a > minute. And most worrying of all quite often the copying just stops halfway > in

Hello, I'm running NT 4.0 (ws & server) with SP5. Everything was running fine with samba 2.0.0, but after building and installing 2.0.4b (freebsd 2.2.8) trying to browse the server shares results in a "A remote procedure call (RPC) protocol error occured." net view \\myserver also produces the same error message: "System error 1728 has occurred. A remote procedure

All, This is my first posting to any of the Samba mailing lists. I've been a lurker for a year or so as I've been working on a VFS for the company I'm working for. We're currently using Samba 3.0.10-4 on RedHat AS 3 Update 4 and we are observing the following problem both with our VFS and with shares residing in a Linux directory on the Samba server. If a directory has lots of

Hello everyone. I am having trouble with rsync stopping in the middle of a transfer. Everything works fine for smaller batches of file, but when I try to rsync big groups, it just stops in the middle. I have been using rsync to copy my home directory to an SD card. I recently got a Drobo+Droboshare (NAS) and want to do the same thing to the Drobo, but when I run rsync, it stops somewhere in

Apologies to the list, the title of this thread is completely wrong. It should be something like "Question about --partial-dir and aborted transfers of large files". Let's see if this mailing list program will allow me to change it... -- T.J. On 10 August 2012 15:28, T.J. Crowder <tj at crowdersoftware.com> wrote: > Hi all, > > rsync is a fantastic tool. :-)

I have a new Sun Fire AMD64 server running Solaris 10 12/06 and Samba 3.0.21b. I have migrated a configuration file from an older RHEL machine running Samba 2.2.x. On this new machine, if one tries to copy a large number of files from a Windows XP client to the server, the copy starts and runs for a few minutes, but then stops. The error message on the XP machine is "Cannot copy

Hello, I have a Debian Stable (Sarge) with a samba to share file with windows client. All is working fine but 2 files generates errors when i try to copy it. The transfer begins, but stops in the middle of the file, and freeze. The error message is (French translation): <Unable to copy file_name.psd : Network name is no more available > I do not understand why I cannot copy those

Dear team I have had problems copying word files from NT directories to Linux directories, conecting with smbmount from Linux. The problem seems to appear with certain long-name files. But I cannot find the pattern for this behavior. Is there anything reported about it? Should I change or add any parameter in the smb.conf file? Will I have problems with future long name files? I appreciate

I have a Samba 3.0.24-7 on Fedora 6 as a member of an Windows NT 4.0 domain, with a simple share setup with ACLs. The permissions on the share from Windows XP Pro Security tab shows Everyone, and root (Unix Group\root) without any Permissions. When trying to add permissions from XP while logged on as CPDOM+admin the error is display "Unable to save permission changes on "share