similar to: Samba quota 'feature' fix?

I began with Samba 1.9.18.p10. on SunOs 5.6. I try backup PC(Windows95) with this: smbclient \\\\pcbig\\test .. .. smb:\> recurse smb:\> directory recursion is now on smb:\> tar c /dev/rmt/0 .... Until it is OK. But restore has error: smb:\> tar x /dev/rmt/0 smb:\> restore tar file \test1.txt of size 70 bytes smb:\> Updating creation date on \testfolder1\ smb:\> ERRDOS - 50

Hi, First time I try ro resolve a domain user after samba/winbind is started, it takes a couple of seconds during which winbind says the following Received packet for \MAILSLOT\NET\GETDC700000A GetDC got invalid response type 21 Received packet for \MAILSLOT\NET\GETDC700000A GetDC got invalid response type 21 Received packet for \MAILSLOT\NET\GETDC700000A GetDC got invalid response type 21

Hi, I've used Samba several years without any problems. Last week I added a new disk to my system, and Samba started to behave very strange. It's slow in terms of establish a connection and time to list directories. I've tried to resolve the problem without success. No other daemon has problems, both ftp and http works fine as well as internal communication. Below I've attached

While trying to switch a domain from an WinNT 4.0 SP ? to an AIX 4.3 with samba 2.2.8 with OS2/warp 4 clients we receive some unexpected errors. - we can log on to the new domain , run logon scripts, map network drives , store and retrive files , print to a Remote server using the printers shared by samba. - we can't run VisualAge Generator (2.X) retriving files from the samba server. (we

Samba is causing a couple huge problems for the NT admins here since we switched a bunch of machines to security=server and started running nmbd. We're running Samba 2.0.2 and 2.0.3 on a mix of Solaris, HP-UX, and OSF1 machines. One, selecting a Samba server in Server Manager, then selecting Computer/ Services causes Server Manager to crash ("An application error has occurred, blah blah,

Two simple build fixes for libldm. Well, the first isn't a build fix as such, but a code improvement. Rich.

Hi! After more work on the oplock_break problem, I've found the following in my tcpdump-smb logging. It seems that when ost5 (pid=26339 in the logs that follow) requests access to the oplocked file comm.inf from ost6 (pid=5872) the oplock_break failes (this is NOT isolated to any one or two systems on our network, just using these two as an example, and the server reports no dropped packets

Prior to upgrading from RH7.0 to RH7.3 our Samba filserver worked perfectly. Now we are having locking problems. Initially Iused the same samba binaries built on RH70, I tried rebuilding Samba and reinstalling but it had no effect. If user bon opens an M$-Office file they frequently get a 'file is already in use by bob'. Sure enough smbstatus -L shows the file locked by bob, but bob

Hi All, When I copied one file from NT4.0 to Linux through samba with 'copy' command in NT4.0, the file was always corrupted. Size of the file copied into Linux was always about 4G. If I copied it through Windows Explorer, it was OK. It seems samba cannot process the "Write Raw" request sent by 'copy' command correctly when file size is larger than 4G bytes. Thanks

Failure for me is always: SMB PACKET: SMBsesssetupX (REPLY) > SMB Command = 0x73 > Error class = 0x6D > Error code = 49152 (0xc000) > Flags1 = 0x80 > Flags2 = 0x3 > Tree ID = 0 (0x0) > Proc ID = 12056 (0x2f18) > UID = 29165 (0x71ed) > MID = 3 (0x3) > Word Count = 0 (0x0) > NTError =

I'm running Samba 3.4.7 on Ubuntu 10.04. This is a recent upgrade and we've starting experience a sporadic problem after this upgrade. When users are browsing through Windows Explorer they sometimes run across folders that appear as unassociated files. This requires the user to click the 'Refresh' button in Windows Explorer to properly see the folders. The files and folders are

On Tue, Aug 11, 2020 at 11:20:54AM +0200, peterz at infradead.org wrote: > On Tue, Aug 11, 2020 at 10:38:50AM +0200, J?rgen Gro? wrote: > > In case you don't want to do it I can send the patch for the Xen > > variants. > > I might've opened a whole new can of worms here. I'm not sure we > can/want to fix the entire fallout this release :/ > > Let me

On Tue, Aug 11, 2020 at 11:20:54AM +0200, peterz at infradead.org wrote: > On Tue, Aug 11, 2020 at 10:38:50AM +0200, J?rgen Gro? wrote: > > In case you don't want to do it I can send the patch for the Xen > > variants. > > I might've opened a whole new can of worms here. I'm not sure we > can/want to fix the entire fallout this release :/ > > Let me

I am the sysadmin in an office with an overabundance of Win95 machines and a few NT 4.0 workstations. All installs went relatively easy for logon scripts, wins, etc. I have run into a semi-serious problem with 2 of the 3 NT workstations. (All running the same service pack - 1). When trying to make a share from one of the 2 remaining workstations, I will recevie an error message saying that:

Hi! I'm currently hunting a strange problem and looking for help! I have a samba3 fileserver (currently samba-3.0.20b, but problem can be reproduced with samba-3.0.7, but _not_ with samba2 like 2.2.8a), and I see performance problems when writing files with MS word 2002 SP3 from a NT4.0 (SP6a) workstation. Saving even the smallest file takes more than 10 seconds! Copying files with Windows

Hi, I am running Samba 3.2.4 on a Solaris 10 SPARC machine. The config is pretty simple (see below). Security is set to 'domain'. The PDC and BDC are running 3.0.30 without problems. When joining the machine to the domain with 'net rpc join', it fails with: Could not connect to server 130.37.79.2 Connection failed: NT_STATUS_INVALID_PARAMETER when running the net command

Hi, I'm having terrible difficulties getting Samba to cooperate. I have the following scenario: Samba 2.2.3 set up as a PDC on a linux machine (turing, with the domain set to DEFAULTDOMAIN), working fine with a win2k client. Now I wish to join a Samba 2.2 linux machine was a domain member server (moog), and I can't seem to convince samba to do what I want it to. moog$ is set up on the PDC

Hello all, I am having a pretty serious problem with rpcclient ... if I try 'enumprinters' at the prompt, i get back rpcclient $> enumprinters cli_pipe: return critical error. Error was NT_STATUS_INVALID_PARAMETER result was NT_STATUS_UNSUCCESSFUL However, enumdrivers works fine. Addriver does not work either, and just returns NT_STATUS_UNSUCCESSFUL ... which means that

i can use the smbclient -L just fine to get a list of shares off my NT4 (Alpha processor) server. My problem lies with rpcclient. It lets me login but then samtest gives the following error: smb: \> samtest samtest SAM Encryption Test SAMR_R_UNKNOWN_38: Unknown NT error smb: \> all i need to be able to do is change the nt password, but the ntpass command gives the same error. any ideas

I am running samba 2.2.6 and cups 1.1.16. I can't get cupsaddsmb to complete successfully. I'm at an end here, I can't think of anything else to try after 2 weeks of searching the web. It copies the drivers to the print$ share directory, however the SetPrinter command fails on the rpcclient command and it returns with an NT_STATUS_UNSUCCESSFUL error. At the SetPrinter failure, it