similar to: difference between samba and smbclient

Hello, Recently, the following problem started happening with a particular samba server: If i have a file open for reading (say, a pdf in xpdf) and then try to write to it (say, through recompiling a latex document) it complains that it cannot open the file for writing. this seems like a file lock issue but I am unsure where it is happening. My previous usage should be perfectly safe since

Hi list. I am a complete newbie to samba and not particularly experienced with linux, can someone please tell me how do I upgrade to samba 3.6.0? I have managed to upgrade from the default samba 3.4 that the ubuntu repositories provide to samba 3.5, but obviously would like to run the latest version I am just not sure what repository I need to add etc. I am running a version of ubuntu lucid 64

Hello, I sent the following message to the Debian folks. They don't think that the Debian packaging could be responsible for the issue described there. > Well, I'm not completely convinced that we will have very useful input > for you. I don't really see any reason for this to be caused by the > Debian packaging. To check this, why not compile samba from sources,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Suse Linux 10.1 X86_64 server that is destined to work with a mixed bag of OS/2, Windows and Linux clients. For this reason, I have again chosen to use the SMB protocol, which mandates the use of samba. I started with samba 3.0.22, but ran into some glitches so migrated to 3.0.23rc3. My Linux client is running Suse 10.1 X86_32 with samba

The parameters 'force create mode' and 'force directory mode' have no effect when the option 'unix extensions' is active. The documentation does not report any interaction between the unix extensions and the forced modes, so I'm assuming it's a bug.I'd like to know if it is a known bug ?Has it been solved, if so in which version ? My server runs Debian lenny,

Hello, I am trying to work out the file locking mechanism on our Samba server when connecting from Linux clients. I am getting some strange behaviour in a mixed Linux/Windows environment when multiple clients open/lock the same file for writing. Everything seems fine when a Windows client creates the lock, but if a Linux client creates the lock, we get either two or more Linux clients being able

Hi! I have a problem for a few weeks, and can't figure out what could be the problem. The client computer runs RHEL 5.2 (arch: x64_64); the smb server is unknown for us. I'm sorry, that I can't provide any info (usernames, servernames, IPs, etc), they are masked to look like variables. But they are correct as far as i am concerned. When I try to mount it with mount.cifs (.smbfs

Greetings, I am working on getting mount.cifs version: 1.11-3.2.4 on debian to mount a share on a samba server Version 3.0.13-1.1-SUSE on SuSe. This was working on older debian systems, but upon upgrading some of the systems to Lenny I am now having trouble mounting shares. Again, this was working and I have smbfs installed on the systems (which is what I used before). The samba server is set

Greetings All, My problem is trying to mount an SMB share from Fedora Core5 to a Windows 98 Machine. Before upgrading from FC4 to FC5 everything worked. I have searched around and it appears that the smbmount and mount -t smbfs options have been deprecated in Samba 3.0.22-1 in favor of CIFS. The command I have been trying now is: mount -t cifs //192.168.0.126/laptop /mnt/share -o username=chime

Hi All, I seem to have exactly the same problem which was described in this thread a while ago. I have gone through every piece of information I was able to find on mailing list archives but all I found was people reporting similar problems and not a solution to it. As in the original discussion if I use smbclient it works fine but if I use mount.cifs it does not work at all. To make smbclient

Hi, I was trying smbmount (SuSE's samba-client-3.0.20b-3.4). The mount command replied: cli_negprot: SMB signing is mandatory and we have disabled it. 9451: protocol negotiation failed SMB connection failed No I'd suggest to change the message at least: It's unclear who "we" is: The Samba Team, the client, or the server The server is a "Windows 2003 server",

Hi, I just installed CIFS support on my machines and must say it works much better than smbfs. special characters alright, transfer speed doubled (from 2.8MB/s to 5.6MB/s on 100MBit). There's two issues tho I haven't been able to root out: -credentials file: tried username=<username> and password=<password> in /etc/credfile, tried user=<username> to match the

>From a linux box, I mount a native NT share (mount -t smbfs -o<options, etc. etc>). I want to be able to do an 'ls -l' in that share and have the owner/group information show the right thing. Currently, no matter what the ACLs on the file on the NT side, from linux, an 'ls -l' shows 'root' as the owner/group. I was expecting winbind to work similar to ypbind in

??Hi all! We use Samba 3 server for some video stuff (editing, rendering, and so on) -- that's why performance is critical. We've tried a lot smb.conf options, but Samba can't satisfy our requirements. Our server configuration is as following: * Hard drive: RAID5 (8 x Seagate 7200.10), 3ware 9550SX-8LP controller * NICs (trunked): 2 x Broadcom NetXtreme BCM5704 * Processor: Opteron

Hi there I recall in times past that when a locked file on a Windows server was accessed by smbfs, you received a kind of "text file busy" type error under Linux. However, on our CentOS4 servers running mount.cifs, accessing a locked file now only reports a "Permission denied" Wireshark shows the server sending "STATUS_FILE_LOCK_CONFLICT" errors to Linux, but it

Hi! I've just searching the list archives but cannot solve my problem with mounting samba (v3.0) shares back on linux (RH 8.0 and 9). Mounting on Win clients works fine and any filenames (including long names with non-ascii chars and spaces) are perfictly supported and accessed. Mounting the share back on (even the same) linux box is a complex task. I use: mount -t smbfs -o guest

Hi guys, samba client version 3.0.5, server version 3.0.5, kernel 2.4.26. Relevant configs on server: unix extensions = Yes wide links = Yes follow symlinks = Yes On client computer with home user mounted via smbfs I'm trying this: D102-054 [/lp/home/dito/tmp] > cd /tmp D102-054 [/tmp] > mkdir dest_dir D102-054 [/tmp] > cd - D102-054 [/lp/home/dito/tmp] > ln -s /tmp/dest_dir

Hello folks. I bought a Western Digital NetCenter drive since it seemed a low-cost way of having a NAS in my home. The NetCenter drives run GPL'ed software (I downloaded the source from Western Digital's Web site, and it refers to Broadcom's "BCM478x Linux NASoC Software." The src directory also contains samba 3.0.2.) The device offers two ways of accessing your data:

Using Samba 3.0.9-Debian on Linspire 5.0.59. Server running is a Windows 2003 Server. I am trying to mount a share on the server but getting error message: cli_negprot: SMB signing is mandatory and we have disabled it. 8919: protocol negotiation failed SMB connection failed In smb.conf I have changed setting "server signing = no" to "server signing = required" but

Greetings Samba peoples... apologies for the long post. I have an issue that remains unresolved on my usual forum, linuxforums.org... it relates to SMB Signing when connecting from Linux to a Win 2003 file server. My OS: >> PClinuxOS - a Mandriva derivative My Samba versions: >> samba-client-3.0.30-3pclos2007.i586.rpm >> samba-common-3.0.30-3pclos2007.i586.rpm >>