[Samba] smbmount ignores noatime
When mounting a Windows share within Linux the noatime option seems to be ignored. I use the following command mount -tsmbfs -ousername=user,noatime //192.168.0.12/eclipse /mnt/tmp Each cat /mnt/tmp/testfile updates the last access time regardless if noatime specified or not. I'm running smbmount v2.0.7 on a old Suse production system, but I could reproduce the same behaviour with a current Ubuntu system using mount.cifs. So I assume I'm doing something wrong?! Any help in this matter would be highly appreciated... Thanks Daniel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] smbmount NT_STATUS_INVALID_WORKSTATION problem
We have an install with sambe 3.0.10 (RHEL 4.3) server and clients. Server is security=ADS , and recently we had to set restrict workstation login in our windows domain. On linux clients (joined to domain) we are having issues with smbmount giving NT_STATUS_INVALID_WORKSTATION errors, but smbclient does not have this error. Debug dumps show smbmount logging is as [DOMAIN]/[us...@[0.0.0.0], where smbclient is logging in as [DOMAIN]/[us...@[machinename]. Even if I use -o netbiosname=MACHINENAME, smbmount is still passing the IP address instead. Any thoughts? Regards, Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/smbmount Windows-AD Kerberos und PAM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. As the Subject line discribes nearly all features/possibilities of interaction bewteen Windows and *nix I will get in detail now ;) I want to login on a linux-machine an get my home from a Windows share. On the one hand I use a Windows 2003 RC2 server - fileserver in an AD / Windows domain. On the other hand I use a linux PC (Ubuntu 8.04 amd64), that gets all login-information via kerberos out of the AD/domain. I added some lines/modified the following files: /etc/samba/smb.conf /etc/nsswitch.conf /etc/krb5.conf /etc/pam.d/common-auth /etc/pam.d/common-account Currently users can log in on the linux-pc using their AD-account. So far so good, but actually I wanted to provide a home directory that is mounted (Windows share) during the login-process. I thought pam_mount would be a good choice. First I wanted to test, if the share can be mounted manually after login - - and ups, first problem A user, who could sucessfully log in using the AD/domain, was able to mount the share via smbmount, but he could only list the content - no writing, modifing, ... My first thought: Might be a problem with the right-managemend, so let' s check and ply with them: 1. right of the windows share - share: everyone - full control - NTFS (Security) user, who logs in, has full control - I modified the advanced security settings, the user has full control on the folder, subfolders and files - the user is actually owner of this (shared) folder 2. after (domain)login on the linux machine I created a directory ~/mnt with usualy rights and ownership 3. I used the following options for smbmount: smbmount //W2K3-Server/share mnt/ -o user=AD-user, / domain=AD-Domain,rw,iocharset=utf8,uid=1, / gid=10004,file_mode=0777,dir_mode=0777 The user-information I fetched via id: uid=1(AD-user) gid=10004(domänen-benutzer) Gruppen=10001(BUILTIN\users),10004(domänen-benutzer),10005(AD-Gruppe1),10006(AD-Gruppe2) Now just a quick look at the lokal rights: ls -ld * drwxrwxrwx 1 AD-user domänen-benutzer 0 2008-11-17 17:01 mnt ls -l mnt - -rwxrwxrwx 1 AD-user domänen-benutzer 0 2008-11-17 17:00 / copy-test.txt.txt drwxrwxrwx 1 AD-user domänen-benutzer 0 2008-09-26 15:22 test123 As smbmount did not work the way I intended - no writing, modifing, ... - - I actually did not try to get lucky with smp_mount. i will try if smbmount works the way I want it to. I tried to mount (smbmount and mount -t smbfs/cifs) as root - surprise, surprise this works. So let's try to write/modify - no chance, neither writing nor modifing :( A quick look at /etc/mtab: more than one line with my mounted windows share exists. How could this happen ?!? I think nearly everyone can use the provided windows share, but not me ;) I tried to solve this problem for one day using google etc. - but could not find a good hint. Does anybody know what goes wrong and give me he hint? Thanks for help/advise best regards Bernd Kohler - -- UMIC - RWTH Aachen http://www.umic.rwth-aachen.de Otto-Blumenthal-Str. 2 52074 Aachen Tel.: +49 241 80 20680 Fax:+49 241 80 22640 E-Mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3mgAACgkQOiq/E1Lch49ZggCgg7Y3s+bQCX7MIy52TDMxTqhf rLEAn3sYFcjuVuOPuzneQxTdlrLjIfEb =k/SJ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount: reading changes ntfs journal
Hi @all! I'm new to this list and neither a samba nor a Windows specialist. That said: We have some linux servers mounting windows shares. The problem is that reading files on the share changes the journal / USN on the Windows side. Now our backup guys are backing up a lot of stuff that hasn't really changed because the journal tells them different. Even when I mount read- only a simple cat or less on a file causes this. Is there a way to fix this? Thanks in advance Mario -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount deprecated - what about Windows 9x?
Hallo, I've just installed Kernel 2.6.25.2 - works fine. But now when I use smbmount for mounting shares from my Win9x clients the system (kernel) tells me smbfs is deprecated and will be removed from the 2.6.27 kernel. Please migrate to cifs. But at least Win9x seems not to like cifs. Mounting via smbfs works since years, mounting (with the same options) via cifs produces several error messages. The ugliest is no such file or directory and strace shows that mount.cifs (or some subroutine) doesn't accept the share. It finds the other server ... Can I use smbmount even with kernel 2.6.27 (or newer)? May be cifs is better, but I need to mount Win9x shares. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount deprecated - what about Windows 9x?
Am Montag, 12. Mai 2008 schrieb Helmut Hullen: Hallo, I've just installed Kernel 2.6.25.2 - works fine. But now when I use smbmount for mounting shares from my Win9x clients the system (kernel) tells me smbfs is deprecated and will be removed from the 2.6.27 kernel. Please migrate to cifs. But at least Win9x seems not to like cifs. Mounting via smbfs works since years, mounting (with the same options) via cifs produces several error messages. The ugliest is no such file or directory and strace shows that mount.cifs (or some subroutine) doesn't accept the share. It finds the other server ... Can I use smbmount even with kernel 2.6.27 (or newer)? May be cifs is better, but I need to mount Win9x shares. Viele Gruesse! Helmut Hi Helmut, you can use cifs vfs to mount win9x shares, but need to add the following to the mount options: servernetbiosname=W9XSERVER or the shorter form servern=W9XSERVER where W9XSERVER is the upper case netbios name of the legacy server. Legacy servers like OS/2 in addition need the option sec=lanman Example: mount -t cifs //server/SHARE /mount/point -o credentials=/root/sec/.creds, \ servern=MYWIN98,dir_mode=0755,file_mode=0764,uid=test,gid=users ... Also have a look at 'man mount.cifs' about the meaning of - dir_mode - file_mode - uid - gid - ... when the server is not supporting the unix extensions. Also note that uppercasing the share name (i.e. //server/SHARE ) will avoid a duplicate treeconX call. IMPORTANT NOTE! When connecting to remote *legacy* servers like - win9x/me - OS/2 - others I strongly advise to *not* use current cifs vfs in a production environment! Initial testing should only be done against special test shares, which should not contain any valuable data! There are glitches with readonly files and the time stamps of directories/files - and possibly more... The cifs vfs developers are aware of this and are working on fixes. Everyone is invited to work with the developers to fix remaining legacy problems. Testing and reporting of bugs is very much appreciated :-) The main mailing list for the linux cifs client vfs is [EMAIL PROTECTED] Send bug reports to https://bugzilla.samba.org/ and choose the product CifsVFS These days lots of support talks are also happening on IRC. Samba/cifs related talks are done on irc.freenode.net in channels #samba (user related) #samba-technical (development only!) My irc nickname is kukks and you can also reach me via email at [EMAIL PROTECTED] Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount deprecated - what about Windows 9x?
Hallo, Günter, Du meintest am 12.05.08 zum Thema Re: [Samba] smbmount deprecated - what about Windows 9x?: smbfs is deprecated and will be removed from the 2.6.27 kernel. Please migrate to cifs. Can I use smbmount even with kernel 2.6.27 (or newer)? May be cifs is better, but I need to mount Win9x shares. you can use cifs vfs to mount win9x shares, but need to add the following to the mount options: servernetbiosname=W9XSERVER or the shorter form servern=W9XSERVER where W9XSERVER is the upper case netbios name of the legacy server. Legacy servers like OS/2 in addition need the option sec=lanman Example: mount -t cifs //server/SHARE /mount/point -o credentials=/root/sec/.creds,servern=MYWIN98,dir_mode=0755,file_mo de=0764,uid=test,gid=users ... Thank you - it works! sec=lanman seems not to be necessary (or outdated). man mount.cifs (Samba 3.0.28a) doesn't show the option lanman for sec. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount deprecated - what about Windows 9x?
Hi Helmut, Am Montag, 12. Mai 2008 schrieb Helmut Hullen: Hallo, Günter, Du meintest am 12.05.08 zum Thema Re: [Samba] smbmount deprecated - what about Windows 9x?: smbfs is deprecated and will be removed from the 2.6.27 kernel. Please migrate to cifs. Can I use smbmount even with kernel 2.6.27 (or newer)? May be cifs is better, but I need to mount Win9x shares. you can use cifs vfs to mount win9x shares, but need to add the following to the mount options: servernetbiosname=W9XSERVER or the shorter form servern=W9XSERVER where W9XSERVER is the upper case netbios name of the legacy server. Legacy servers like OS/2 in addition need the option sec=lanman Example: mount -t cifs //server/SHARE /mount/point -o credentials=/root/sec/.creds,servern=MYWIN98,dir_mode=0755,file_mo de=0764,uid=test,gid=users ... Thank you - it works! sec=lanman seems not to be necessary (or outdated). man mount.cifs (Samba 3.0.28a) doesn't show the option lanman for sec. 'man mount.cifs' atm is not completely uptodate - in the near future even more mount options might be added... When mounting OS/2 shares, sec=lanman _is_ needed! From the README of the cifs vfs kernel source: ... secSecurity mode. Allowed values are: noneattempt to connection as a null user (no name) krb5Use Kerberos version 5 authentication krb5i Use Kerberos authentication and packet signing ntlmUse NTLM password hashing (default) ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default) ntlmv2 Use NTLMv2 password hashing ntlmv2i Use NTLMv2 password hashing with packet signing lanman (if configured in kernel config) use older lanman hash ... All readers of this thread should also note that the cifs vfs kernel module must be build with the option CONFIG_CIFS_WEAK_PW_HASH=y to support legacy servers which depend on the weak lanman hash! Some distros have already started to ship kernels without setting this build flag (but have removed smbfs, too). Many distro maintainers have now been informed about this. Please drop me a note when a distro does not support cifs vfs legacy servers connections, so we can contact the maintainers. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount deprecated - what about Windows 9x?
Hallo, Günter, Du meintest am 12.05.08 zum Thema Re: [Samba] smbmount deprecated - what about Windows 9x?: sec=lanman seems not to be necessary (or outdated). man mount.cifs (Samba 3.0.28a) doesn't show the option lanman for sec. From the README of the cifs vfs kernel source: ... [...] All readers of this thread should also note that the cifs vfs kernel module must be build with the option CONFIG_CIFS_WEAK_PW_HASH=y to support legacy servers which depend on the weak lanman hash! Ok - I hope none of my clients uses OS2 ... (I had just compiled kernel 2.6.25.2 - without this option of course). Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount fails when trying inside a SSH tunnel
Hello All, Here is the problem definition: * I have a Windows XP SP2 system (part of a Samba NT domain). The system has a share created in its local disk which has read access for everyone. * I have a Linux (SuSE 9.3) system. * Using PuTTY, I create a SSH tunnel from the Windows XP to Linux (-R 4000:localhost:139) to mount the smb shared folder on the Linux system. * When I do smbclient -L CMCCLIENT6 -p 4000 -U adminuser, it lists the shares fine in the Linux server. * But, I am not successful in mounting the share using smbmount. Here are some of my tries: ribosome:~ # mount -t smbfs -o username=CMC-NT \adminuser,ip=127.0.0.1,port=4000 //127.0.0.1/foldertoshare /shares Password: 2079: session request to 127.0.0.1 failed (Call returned zero bytes (EOF)) 2079: session request to 127 failed (Call returned zero bytes (EOF)) ribosome:~ # mount -t smbfs -o username=adminuserribosome:~ # smbmount \\\CMCCLIENT6\foldertoshare /shares -o username=adminuser,ip=127.0.0.1,port=4000 27896: session request to CMCCLIENT6 failed (Call returned zero bytes (EOF)) 27896: session request to *SMBSERVER failed (Call returned zero bytes (EOF)) SMB connection failed ribosome:~ # smbmount \\\CMCCLIENT6\foldertoshare /shares -o username=adminuser,ip=127.0.0.1,port=4000 27896: session request to CMCCLIENT6 failed (Call returned zero bytes (EOF)) 27896: session request to *SMBSERVER failed (Call returned zero bytes (EOF)) SMB connection failed Anything I am missing? Thanks, Prakash -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount Permission Denied
Hey everyone, I have an SMB/CIFS share on a Samba Server that I am trying to mount on a workstation via the smbmount command. When I just connect to the share using smbclient everything works fine. When I mount the share with smbmount using the exact same credentials, I mysteriously can't write to it. I get Permission Denied. Can someone please clue me in to what could be so different about smbmount? I'm using uid= and gid= to set appropriate local permissions. In fact, all permissions seem fine, and I assume they are since I can do whatever I want with smbclient. Thanks! - SG -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
On Wednesday 18 July 2007, Server Gremlin wrote: When I mount the share with smbmount using the exact same credentials, I mysteriously can't write to it. I get Permission Denied. Can someone please clue me in to what could be so different about smbmount? man smbmount Maybe this: WARNING: smbmount is deprecated and not maintained any longer. mount.cifs (mount -t cifs) should be used instead of smbmount. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
Chris Smith wrote: On Wednesday 18 July 2007, Server Gremlin wrote: When I mount the share with smbmount using the exact same credentials, I mysteriously can't write to it. I get Permission Denied. Can someone please clue me in to what could be so different about smbmount? man smbmount Maybe this: WARNING: smbmount is deprecated and not maintained any longer. mount.cifs (mount -t cifs) should be used instead of smbmount. Chris What? I'm running the latest version of Ubuntu (Feisty Fawn, 7.04 Desktop Version) and nothing of the sort appears anywhere in the man page. I tried mount -t cifs, and that mounted the filesystem with the server's uid and gid numbers. Anything owned by root on the server shows up as root when I mount it on the client, though I can't change anything. Everything owned by something other than root on the server shows up as random numbers. The uid= and gid= parameters are being ignored, so I can't change the ownership to anything that my local workstation user can work with. Any suggestions? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
On Wednesday 18 July 2007, Server Gremlin wrote: What? I'm running the latest version of Ubuntu (Feisty Fawn, 7.04 Desktop Version) and nothing of the sort appears anywhere in the man page. Nothing I can do about that. Although it hasn't been a secret that smbfs has been, at best, out of fashion for a long time. I tried mount -t cifs, and that mounted the filesystem with the server's uid and gid numbers. Anything owned by root on the server shows up as root when I mount it on the client, though I can't change anything. Everything owned by something other than root on the server shows up as random numbers. The uid= and gid= parameters are being ignored, so I can't change the ownership to anything that my local workstation user can work with. Any suggestions? Does the server support the CIFS Unix Extensions? man mount.cifs maybe peek at noperm -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
Chris Smith wrote: On Wednesday 18 July 2007, Server Gremlin wrote: What? I'm running the latest version of Ubuntu (Feisty Fawn, 7.04 Desktop Version) and nothing of the sort appears anywhere in the man page. Nothing I can do about that. Although it hasn't been a secret that smbfs has been, at best, out of fashion for a long time. I tried mount -t cifs, and that mounted the filesystem with the server's uid and gid numbers. Anything owned by root on the server shows up as root when I mount it on the client, though I can't change anything. Everything owned by something other than root on the server shows up as random numbers. The uid= and gid= parameters are being ignored, so I can't change the ownership to anything that my local workstation user can work with. Any suggestions? Does the server support the CIFS Unix Extensions? man mount.cifs maybe peek at noperm Thanks, that finally did it. I've finally managed to mount the smb/cifs share on a local mount point by adding something like the following line to my fstab: //servername/sharename /local/mountpoint cifs exec,credentials=/path/to/myfile,noperm 0 0 I have a few lingering questions if anyone could please help me out. 1) The man page for mount.cifs seems to imply that using noperm allows anyone logged into my workstation to mess with my files. This is fine for me because I'm the only one with a login on this workstation, but this really seems like an awful solution under any other circumstances. Isn't there a better way to do what I want...? (Just to reiterate: I have an SMB/CIFS share on a Linux Samba Server that I want to mount locally on a Linux workstation.) 2) What are CIFS Unix Extensions? I Googled and Wikipedia'ed around and found little... sounds like they're a part of Samba that makes Samba return uid and gid information from the server's filesystem to the client. If that's so, why in the world would I ever want to do this? Thanks very much for your help, - SG -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
On Wednesday 18 July 2007, Server Gremlin wrote: What are CIFS Unix Extensions? man smb.conf -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount Permission Denied
On Wednesday 18 July 2007, Server Gremlin wrote: The uid= and gid= parameters are being ignored, so I can't change the ownership to anything that my local workstation user can work with. Normal when the CIFS Unix extensions are negotiated (man mount.cifs). Between controlling unix extensions on the share and perm/noperm, setuids/nosetuids on the client, plus whether or not your user/group ids match up an the client and server, you can probably find a satisfactory solution. There some additional documentation pointed by the cifs.txt file in the kernel source documentation. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
Am Montag, 7. Mai 2007 21:42 schrieb Chris Smith: On Monday 07 May 2007, John G Walker wrote: The files are on a W98 system for historical reasons and they are being slowly migrated off. However, the reason I can't just move them is because I'm using Windows programs on the legacy systems. Some I wrote myself, in Visual Basic, so I can't blame anybody else for the situation. Another program I use is Photoshop, which they won't port to Linux (despite the fact it is the program most wanted to be ported to Linux). Etc. I need to keep running Windows as long as I have the need for such stuff. The data files don't need to reside on that system. Virtually every app I know of, including Photoshop, can access, open, edit, and save files on remote shares. Some real legacy apps may require mapped drives instead of UNC paths but they should, in most cases, work just fine. Chris Hi all, just some additions and clarifications from my side. Samba3 / Samba4 === For some years now I'm trying hard to support the samba3 / samba4 team regarding missing features or bugs related to legacy clients - mainly OS/2, but also windows9x/me. Nice and interesting times and the experience, that the samba developers _always_ have had and _still_ have an open ear, when troubles or wishes are reported to them! The main problem is, that those missing stuff must be _reported_ to them! These days, most of the samba developers do not have any physical access to legacy client installations anymore. So it's getting more and more important to send them as much background information as possible, like detailed - debug 10 logs - network sniffs - used samba version and smb.conf settings - used operating systems (fixpak level) - used file systems (e.g. xattr support) - proposed patches - ... In addition, it's very important to help with testing suggested patches before they go mainstream. Cause some of those legacy questions can also easily be discussed on irc, some years ago I've opened 2 separate channels on irc.freenode.net: #samba-os2 #samba-os2-technical The names are a bit misleading - but all legacy smb users are welcome there. :-) To my knowledge, most of the outstanding (OS/2) glitches are solved now. CIFS kernel module: === When the first discussions about dropping the kernel module smbfs and its samba userland helpers - smbmount - smbmnt - smbumount were starting on @samba-technical about a year ago, Jeremy Allison (jra) told me on irc, that Steve French (sfrench) had already added some code to support legacy smb servers within cifs. That days I started to build my own cifs.ko from the samba hosted cifs-client svn repository, to be able to add and test code for possibly missing features regarding legacy smb servers. Cause I was not aware of the separately existing mailing list [EMAIL PROTECTED], private email exchange with Steve was starting to discuss and solve missing stuff - sending patches back and forth... for many weeks ... Steve also managed to get access to an OS/2 box, to test stuff himself. Afaik, he's testing against win9x, too. I must admit, that we had one big problem that days: Steve was doing his work on the kernel git-tree - and I was using the samba cifs-client svn repository... Both repos got more or less so worse out of sync, that the simple exchange of patches was no longer feasible. I'm working as a freelancer and got distracted from cifs due to other customer needs - which is a bit reflected in https://bugzilla.samba.org/show_bug.cgi?id=4090 Sorry for my probably upset comments... To solve the 2 repository problem, at the end of last year i did setup a completely separate linux box entirely for cifs stuff. Installed git, cogito and sparse - and joined LKML. I'm able to test here against 3 OS/2 and 1 win98 legacy box. One major issue was (and partly is) the reading and writing of file/directory time stamps - with ugly side-effects on the OS/2 side: due to the parameter lastwritetime = 0 used on SMBClose, all time stamps on the OS/2 side were reset to NULL during file- browsing. BTW - when browsing directories with konqueror, it usually tries to display some popup-contents of the file the mouse is over. - open file - read (part) of the file - close the file == SMBClose()!! = filetime = zero Another problem is the fact, that *nix and newer windows are using UTC as the base for time stamps, but some legacy servers always use localtime and send them on the wire. Today, afaik all of reading time stamps is fixed. But there are still issues when writing a file/dir. cp -p linux_src_file os2_dst_file does not preserve any time stamp (the legacy versions of setfileinfo() / setpathinfo() are not implemented atm). I mailed Steve, that this is even true, when copying to a win2k or winxp server. Setpathinfo() does not work, when the file is still open. _Only_ on winNT, a separate open, setfileinfo, close
Re: [Samba] smbmount
On Mon, 07 May 2007 20:41:47 +0100 Tom Crummey [EMAIL PROTECTED] wrote: Why does the W98 box have to be the server? Can't you make the disk from the Linux system available as a share, mount it on the W98 box and move the files from the W98 local drive to the share? Because there isn't a the share. There's a multiplicity of accounts, which W98 can't handle, without doing some horrendously complicated mapping. And the W98 machine isn't he server. It's a server. It works as a server for certain purposes, mainly to do with simplifying access to data. It's simplicity I'm after, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 07 May 2007 20:41:47 +0100 Tom Crummey [EMAIL PROTECTED] wrote: Why does the W98 box have to be the server? Can't you make the disk from the Linux system available as a share, mount it on the W98 box and move the files from the W98 local drive to the share? Because there isn't a the share. There's a multiplicity of accounts, which W98 can't handle, without doing some horrendously complicated mapping. And the W98 machine isn't he server. It's a server. It works as a server for certain purposes, mainly to do with simplifying access to data. It's simplicity I'm after, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Thu, 03 May 2007 18:24:19 -0400 Felix Miata [EMAIL PROTECTED] wrote: On 2007/05/03 17:32 (GMT+0100) John G Walker apparently typed: I installed samba on a PC running SuSE 10.2, using the version from the SuSE 10.2 repository (3.0.23). All very nice, except smbmount is missing. As I understand it, this would seem to be because the version offered had not been compiled with the --with-smbmount option. Is my interpretation correct? And if so, how can I fix things? Do I have to download the source and do my own compilation (urrgh)? Or is there a version on a repository somewhere compiled with the --with-smbmount option? I didn't have this problem with either SuSE 10.0 or 10.1, SUSE wants you to use cifs instead of smbfs, So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. As far as I understand it, Windows 98 doesn't use CIFS. Since the object of using Samba is partly to access a Windows 98 machine, not having SMBFS available sort of defeats the object of using Samba in the first place. Maybe they want us to go back to using floppy disks as substitutes for a network. If there is a way to network files to and from a Windows 98 machine via CIFS, by the way, please let me know, since this would solve my problem. but if you can't get cifs to work right, you can recompile the kernel to enable smbfs. I don't remember exactly the details of getting smbmount back, so I asked on freenode Thanks very much. This is over and above the call of duty and well appreciated. and got the following: 13:22 a-865 kukks: what did we do to get smbmount back in SUSE 10.2? 14:41 kukks a-865: You have to download the samba-client - possibly Suse even dropped stuff from that. you need: smbmount smbmt smbumount 14:42 I always use the samba3 svn source and build all stuff myself 14:44 kukks Then 2 symlinks must be set in /sbin to allow the basic mount cmd to work: mount.smbfs - /usr/bin/smbmount umount.smbfs - /usr/bin/smbumount In fact I have downloaded the Samba client - and have now upgraded Samba to version 3.0.24, just in case it was a version problem. Samba client informs me (in YaST) that it installs smbmount, but no such luck when I try it out. smbmount is just not found. When I look in /sbin there is no mount.smbfs, only mount.cifs. That would seem to be the main problem. So how do I get this installed if not by installing samba-client? -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, May 07, 2007 at 01:46:33PM +0100, John G Walker wrote: As far as I understand it, Windows 98 doesn't use CIFS. Since the object of using Samba is partly to access a Windows 98 machine, not having SMBFS available sort of defeats the object of using Samba in the first place. Maybe they want us to go back to using floppy disks as substitutes for a network. Just for your info: SMB is exactly the same as CIFS, except one packet at the start of the connection. Volker pgpJUzwhIFrHn.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John G Walker wrote: So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. smbfs.kio is unmaintained and no one wants to touch it. It's not just SuSE. It's a deprecated file system in the kernel. As far as I understand it, Windows 98 doesn't use CIFS. Support for netbios transport was added in cifs.ko I think around 2.6.15 cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPzD/IR7qMdg1EfYRAnBiAJ97g58qPHdRdQlGgvoLTtiVRmj6SwCg2kZy OGcHw0/jPlnaDcXd1xdYigs= =nwo6 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Monday 07 May 2007, John G Walker wrote: So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. They're not. Nothing is stopping you from compiling your own kernel and adding modules, or even your own code. Try that with Windows. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 7 May 2007 10:37:37 -0400 Chris Smith [EMAIL PROTECTED] wrote: On Monday 07 May 2007, John G Walker wrote: So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. They're not. Nothing is stopping you from compiling your own kernel and adding modules, or even your own code. Try that with Windows. Chris Just because nothing anyone can ever do with Linux is going to be anywhere near as bad as what I would get with Windows, doesn't mean that I'm not going to complain when Linux is not as good as it could be. :) -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On 2007/05/07 13:46 (GMT+0100) John G Walker apparently typed: On Thu, 03 May 2007 18:24:19 -0400 Felix Miata [EMAIL PROTECTED] wrote: SUSE wants you to use cifs instead of smbfs, So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. I think SUSE is saying the same thing as other distros. They prefer to give you maintained but dysfunctional CIFS over functional but unmaintained networking support. NAICT, the kernel developers are the root of the problem, not Novell. As far as I understand it, Windows 98 doesn't use CIFS. Since the object of using Samba is partly to access a Windows 98 machine, not having SMBFS available sort of defeats the object of using Samba in the first place. Maybe they want us to go back to using floppy disks as substitutes for a network. CIFS is supposed to replace SMBFS. It simply doesn't work right with W98 in the version supplied by SUSE. AFAIK, it still doesn't work right in newer versions either. If there is a way to network files to and from a Windows 98 machine via CIFS, by the way, please let me know, since this would solve my problem. There isn't AFAIK. This isn't directly related, but I think it's indirectly related in a major way. W98 is so horribly insecure that developers don't want to mess with it, which means testing CIFS with it is a logistical problem. The implication here is people still using W98 should find a way to not use it any more, either upgrading to a newer version of doz if possible, or replacing W98 with Linux, and using W98 in a virtual machine if necessary if not using W98 is not an option. but if you can't get cifs to work right, you can recompile the kernel to enable smbfs. I don't remember exactly the details of getting smbmount back, so I asked on freenode Thanks very much. This is over and above the call of duty and well appreciated. Not sure what you mean, but compiling a kernel on SUSE really isn't that big a deal. It's a big space and CPU/IO time consumer, but the mental effort required is relatively small. In fact I have downloaded the Samba client - and have now upgraded Samba to version 3.0.24, just in case it was a version problem. Samba client informs me (in YaST) that it installs smbmount, but no such luck when I try it out. smbmount is just not found. When I look in /sbin there is no mount.smbfs, only mount.cifs. That would seem to be the main problem. So how do I get this installed if not by installing samba-client? Try asking on the main SUSE list for SUSE-specific help: [EMAIL PROTECTED] I don't remember how I did it, which is why I asked on IRC before my previous reply. -- The path of the righteous is like the first gleam of dawn, shining ever brighter till the full light of day. Proverbs 4:18 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Felix, On 2007/05/07 13:46 (GMT+0100) John G Walker apparently typed: On Thu, 03 May 2007 18:24:19 -0400 Felix Miata [EMAIL PROTECTED] wrote: SUSE wants you to use cifs instead of smbfs, So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. I think SUSE is saying the same thing as other distros. They prefer to give you maintained but dysfunctional CIFS over functional but unmaintained networking support. NAICT, the kernel developers are the root of the problem, not Novell. No personal offense intended here, but ... rant mode=on This entire smbfs vs. cifs ongoing discussion is not helpful. And frankly, it is just a little silly. Old code goes away and is replaced by new code. Are you willing to maintain the smbfs code? No? Neither was anyone else. So it's not kernel developers that are the problem. But simply disinterest or lack of time from the community of people using and/or developing kernel code. And btw...If Novell had wanted to maintain smbfs.kko, they could have. But no linux vendor or developer volunteered to take it up (at least none that actually followed through). It's easy to pitch rocks at the people doing the work. But please at least get the facts straight before tossing your comments into the ring. cifs.ko is the the replacement for smbfs.ko. End-of-story. rant mode=off If you have bugs, then please file them at https://bugzilla.samba.org/ under the CIFS VFS component. Tell Steve French about them. The smbfs code was good in its time but has long since suffered from bit rot. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGP0l5IR7qMdg1EfYRAjopAJ9uWXIiVvTXKKmyKG/PASK2ytX/1gCfUg46 OaNl+NeY8vhhmKT1wbrJ5I0= =FqFr -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] smbmount
On the other hand, I would love to be able to use cifs exclusively, but I have several network drives ( WD and TrendNet ), and neither brand will mount via cifs with a credentials file. I have to use smbfs if I am to access them. No amount of googling has provided me with a clue, and a thread on this site went nowhere [http://lists.samba.org/archive/samba/2006-October/126556.html]. So, for as long as Debian supports smbfs, I'll continue to use it. Maybe a future firmware revision on the drives will correct the problem. Dale Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John G Walker wrote: So why is SuSE (or Novell) telling me what I should or shouldn't use? In any case, this is a bout the world I live in, not about their or my preferences. smbfs.kio is unmaintained and no one wants to touch it. It's not just SuSE. It's a deprecated file system in the kernel. As far as I understand it, Windows 98 doesn't use CIFS. Support for netbios transport was added in cifs.ko I think around 2.6.15 cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPzD/IR7qMdg1EfYRAnBiAJ97g58qPHdRdQlGgvoLTtiVRmj6SwCg2kZy OGcHw0/jPlnaDcXd1xdYigs= =nwo6 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 07 May 2007 11:27:44 -0400 Felix Miata [EMAIL PROTECTED] wrote: This isn't directly related, but I think it's indirectly related in a major way. W98 is so horribly insecure that developers don't want to mess with it, which means testing CIFS with it is a logistical problem. The implication here is people still using W98 should find a way to not use it any more, either upgrading to a newer version of doz if possible, or replacing W98 with Linux, and using W98 in a virtual machine if necessary if not using W98 is not an option. But if I can't migrate, then how the hell can I replace W98? This seems to me to be very American-style thinking: if you imagine something will be the case, then it will be the case. The world doesn't work like that. I have a W98 machine that I need to share files with other machines on the network, and no amount of wishful thinking will change that. but if you can't get cifs to work right, you can recompile the kernel to enable smbfs. I don't remember exactly the details of getting smbmount back, so I asked on freenode Thanks very much. This is over and above the call of duty and well appreciated. Not sure what you mean I mean that I appreciate your effort on my behalf. I don't know how I could have said that plainer. So thanks again, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dale Schroeder wrote: On the other hand, I would love to be able to use cifs exclusively, but I have several network drives ( WD and TrendNet ), and neither brand will mount via cifs with a credentials file. I have to use smbfs if I am to access them. No amount of googling has provided me with a clue, and a thread on this site went nowhere [http://lists.samba.org/archive/samba/2006-October/126556.html]. So, for as long as Debian supports smbfs, I'll continue to use it. Maybe a future firmware revision on the drives will correct the problem. You you filed a bug for Steve ? jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGP1/OIR7qMdg1EfYRAu5dAJ9vAwtvJZfsuUEV5bxXkW4YP62mBwCgio/O 17L/0k5QmcvDYpSAze80Nzs= =eGOB -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 07 May 2007 09:00:31 -0500 Gerald (Jerry) Carter [EMAIL PROTECTED] wrote: As far as I understand it, Windows 98 doesn't use CIFS. Support for netbios transport was added in cifs.ko I think around 2.6.15 So this would mean that I can access W98 files via CIFS? Felix says not. Maybe I should suck it and see? -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On 2007/05/07 10:44 (GMT-0500) Gerald (Jerry) Carter apparently typed: On 2007/05/07 13:46 (GMT+0100) John G Walker apparently typed: I think SUSE is saying the same thing as other distros. They prefer to give you maintained but dysfunctional CIFS over functional but unmaintained networking support. NAICT, the kernel developers are the root of the problem, not Novell. This entire smbfs vs. cifs ongoing discussion is not helpful. And frankly, it is just a little silly. Old code goes away and is replaced by new code. Are you willing to maintain the smbfs code? No? Neither was anyone else. So it's not kernel developers that are the problem. But simply disinterest or lack of time from the community of people using and/or developing kernel code. That's all well and good to say, but the fact is my old distro had networking that worked just fine for me, but fell out of support, so I had to upgrade to a newer distro in order to maintain access to security fixes. Now that I've upgraded, I have broken networking, unless I recompile to include the unsupported module that actually works to replace the supported module that is known to not work for everyone. I really don't care what's supported, only that my networking actually works. If you have bugs, then please file them at https://bugzilla.samba.org/ under the CIFS VFS component. Tell Steve French about them. I don't file bugs on samba because it's all over my head. I'm not a developer. When I find something that doesn't work, as has routinely been the case trying to network Linux released distros with OS/2 since the first release of samba version 3, I go to various forums to try to find current solutions, and try to apprise those who do understand so that they can find existing or file new bugs as they deem appropriate. See e.g. https://bugzilla.samba.org/show_bug.cgi?id=4090 and the other bugs in http://tinyurl.com/3xbcp9 where there are open bugs dating back as long as 3 years. With bugs there and relevant to me going so long unfixed, there seems little point in filing any more. Waiting on Steve French seems to be something that once started seems never to end. If anything deserves a rant, it should be about virtually total dependance of a component on one person whose work stays in a private tree for weeks or more on end (which is my limited and possibly broken understanding of the state of the relationship between CIFS and SF). The smbfs code was good in its time but has long since suffered from bit rot. All I know is if I recompile to reenable SMBFS I have networking that is no worse than it was before upgrading the OS to a supported version, quite unlike networking with CIFS. -- The path of the righteous is like the first gleam of dawn, shining ever brighter till the full light of day. Proverbs 4:18 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, May 07, 2007 at 01:36:26PM -0400, Felix Miata wrote: I don't file bugs on samba because it's all over my head. I'm not a developer. Just to assure you: Over my head is just a false assumption. We might ask you to provide log files and network traces, and we might ask you to update to current software, but not reporting a bug because you believe it is Over my head is just wrong. If we don't provide enough info to enable you to send us sufficient info, then it's our fault, not yours. Waiting on Steve French seems to be something that once started seems never to end. If anything deserves a rant, it should be about virtually total dependance of a component on one person whose work stays in a private tree for weeks or more on end (which is my limited and possibly broken understanding of the state of the relationship between CIFS and SF). The only way around this is to raise this issue on the mailing lists, as you did hear. Steve might not be directly subscribed, but there are enough people around who have regular personal contact to really bug him if something is severely broken. Volker pgpiMxB6ILHe2.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
No offense, but it sounds like you are venting about something that wasn't enabled for the packages in your particular distro of choice. If so, it seems to me that this is the wrong venue to vent. I would suggest contacting the vendor, distro maintainer and/or package maintainer with your concerns. Or continue to roll your own packages for whichever distro you choose. If you feel inspired, write a howto for it (if one doesn't already exist) so that people don't reinvent the wheel. Also it would help in case you forget something and don't have to resolve old problems. Felix Miata wrote: On 2007/05/07 10:44 (GMT-0500) Gerald (Jerry) Carter apparently typed: On 2007/05/07 13:46 (GMT+0100) John G Walker apparently typed: I think SUSE is saying the same thing as other distros. They prefer to give you maintained but dysfunctional CIFS over functional but unmaintained networking support. NAICT, the kernel developers are the root of the problem, not Novell. This entire smbfs vs. cifs ongoing discussion is not helpful. And frankly, it is just a little silly. Old code goes away and is replaced by new code. Are you willing to maintain the smbfs code? No? Neither was anyone else. So it's not kernel developers that are the problem. But simply disinterest or lack of time from the community of people using and/or developing kernel code. That's all well and good to say, but the fact is my old distro had networking that worked just fine for me, but fell out of support, so I had to upgrade to a newer distro in order to maintain access to security fixes. Now that I've upgraded, I have broken networking, unless I recompile to include the unsupported module that actually works to replace the supported module that is known to not work for everyone. I really don't care what's supported, only that my networking actually works. If you have bugs, then please file them at https://bugzilla.samba.org/ under the CIFS VFS component. Tell Steve French about them. I don't file bugs on samba because it's all over my head. I'm not a developer. When I find something that doesn't work, as has routinely been the case trying to network Linux released distros with OS/2 since the first release of samba version 3, I go to various forums to try to find current solutions, and try to apprise those who do understand so that they can find existing or file new bugs as they deem appropriate. See e.g. https://bugzilla.samba.org/show_bug.cgi?id=4090 and the other bugs in http://tinyurl.com/3xbcp9 where there are open bugs dating back as long as 3 years. With bugs there and relevant to me going so long unfixed, there seems little point in filing any more. Waiting on Steve French seems to be something that once started seems never to end. If anything deserves a rant, it should be about virtually total dependance of a component on one person whose work stays in a private tree for weeks or more on end (which is my limited and possibly broken understanding of the state of the relationship between CIFS and SF). The smbfs code was good in its time but has long since suffered from bit rot. All I know is if I recompile to reenable SMBFS I have networking that is no worse than it was before upgrading the OS to a supported version, quite unlike networking with CIFS. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Monday 07 May 2007, John G Walker wrote: I have a W98 machine that I need to share files with other machines on the network, and no amount of wishful thinking will change that. Maybe useful thinking can. Like how about transferring the files that are on the W98 system to a CD or Flashdrive, then transferring them to something other than a W98 system and sharing them to the network from there? No need to use cifs.ko to talk to a the W98 system as it wont be the server any longer. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On 2007/05/07 18:21 (GMT+0100) John G Walker apparently typed: On Mon, 07 May 2007 09:00:31 -0500 Gerald (Jerry) Carter wrote: As far as I understand it, Windows 98 doesn't use CIFS. Support for netbios transport was added in cifs.ko I think around 2.6.15 So this would mean that I can access W98 files via CIFS? Felix says not. Depends whether by access you mean properly working access, or any type of access at all. I can't remember the last time I tried to access W98 from Linux (several years by now probably), but when accessing a legacy OS/2 LM server with the latest CIFS client the timestamping is still broken. -- The path of the righteous is like the first gleam of dawn, shining ever brighter till the full light of day. Proverbs 4:18 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 7 May 2007 14:19:29 -0400 Chris Smith [EMAIL PROTECTED] wrote: On Monday 07 May 2007, John G Walker wrote: I have a W98 machine that I need to share files with other machines on the network, and no amount of wishful thinking will change that. Maybe useful thinking can. Like how about transferring the files that are on the W98 system to a CD or Flashdrive, then transferring them to something other than a W98 system and sharing them to the network from there? No need to use cifs.ko to talk to a the W98 system as it wont be the server any longer. Chris Transfer the to something other than a W98 system? Is this meant to be practical? Sorry if this sounds rude, since I know you're trying to help, but this is woolly thinking at its worst. What precisely other? The files are on a W98 system for historical reasons and they are being slowly migrated off. However, the reason I can't just move them is because I'm using Windows programs on the legacy systems. Some I wrote myself, in Visual Basic, so I can't blame anybody else for the situation. Another program I use is Photoshop, which they won't port to Linux (despite the fact it is the program most wanted to be ported to Linux). Etc. I need to keep running Windows as long as I have the need for such stuff. The only practical something other than W98 that I could possibly use is to buy a new PC installed with Windows Vista, and I'm buggered if I'm spending money going down that route. The reason for migrating to Linux in the first place was to get myself away from Microsoft. The more sensible backup plan, of course, is to use my SuSE 10.0 machine to link to the W98 machine, and pass files down the chain to my 10.2 PC. A pain in the arse, but a darn sight cheaper than shelling out money to Microsoft (and Dell, or whoever) and a lot easier than shuffling Flashdrives back and forth. But thanks all the same for taking an interest. I suppose there's always a chance that off-the-wall suggestions will work, and I'd rather hear a hundred suggestions that won't work than miss one that will, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Monday 07 May 2007, John G Walker wrote: The files are on a W98 system for historical reasons and they are being slowly migrated off. However, the reason I can't just move them is because I'm using Windows programs on the legacy systems. Some I wrote myself, in Visual Basic, so I can't blame anybody else for the situation. Another program I use is Photoshop, which they won't port to Linux (despite the fact it is the program most wanted to be ported to Linux). Etc. I need to keep running Windows as long as I have the need for such stuff. The data files don't need to reside on that system. Virtually every app I know of, including Photoshop, can access, open, edit, and save files on remote shares. Some real legacy apps may require mapped drives instead of UNC paths but they should, in most cases, work just fine. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, May 07, 2007 at 07:55:26PM +0100, John G Walker wrote: But thanks all the same for taking an interest. I suppose there's always a chance that off-the-wall suggestions will work, and I'd rather hear a hundred suggestions that won't work than miss one that will, File concrete bug reports with good info. And stop whining. Volker pgpaSzGfOntlV.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On 2007/05/07 23:28 (GMT+0200) Volker Lendecke apparently typed: On Mon, May 07, 2007 at 07:55:26PM +0100, John G Walker wrote: But thanks all the same for taking an interest. I suppose there's always a chance that off-the-wall suggestions will work, and I'd rather hear a hundred suggestions that won't work than miss one that will, File concrete bug reports with good info. And stop whining. It does little or no good to tell people looking for current solutions to file bug reports regarding legacy LM problems. There are existing bugs known to Steve French, whether filed or not, without a fix to which people needing access to legacy LM servers have no solution other than smbfs. We're on the doorstep of SUSE 10.3, with still no prospect of when to expect the year or more old LM timestamp problems to be solved, as https://bugzilla.samba.org/show_bug.cgi?id=3815 remains open, and rather stale. -- The path of the righteous is like the first gleam of dawn, shining ever brighter till the full light of day. Proverbs 4:18 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 7 May 2007 23:28:10 +0200 Volker Lendecke [EMAIL PROTECTED] wrote: On Mon, May 07, 2007 at 07:55:26PM +0100, John G Walker wrote: But thanks all the same for taking an interest. I suppose there's always a chance that off-the-wall suggestions will work, and I'd rather hear a hundred suggestions that won't work than miss one that will, File concrete bug reports with good info. And stop whining. Volker Bugs? Whining? Have you actually read this thread? -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Mon, 7 May 2007 15:42:16 -0400 Chris Smith [EMAIL PROTECTED] wrote: On Monday 07 May 2007, John G Walker wrote: The files are on a W98 system for historical reasons and they are being slowly migrated off. However, the reason I can't just move them is because I'm using Windows programs on the legacy systems. Some I wrote myself, in Visual Basic, so I can't blame anybody else for the situation. Another program I use is Photoshop, which they won't port to Linux (despite the fact it is the program most wanted to be ported to Linux). Etc. I need to keep running Windows as long as I have the need for such stuff. The data files don't need to reside on that system. Virtually every app I know of, including Photoshop, can access, open, edit, and save files on remote shares. Some real legacy apps may require mapped drives instead of UNC paths but they should, in most cases, work just fine. Chris Yes, Photoshop can run across a network, and I do run it that way a lot. But it's only one program. Other programs do not, including ones written in VB. And, even if there was a way around this, the problem of multiple accounts I mentioned in my reply to Tom Crummey's post would remain. Basically, W98 is so primitive that the only practical solution is to let the complexities of the situation be handled by Linux. I'm beginning to feel that restricting sharing the W98 data to the SuSE 10.0 machine is the best solution. It's bit fiddly, but then, sharing data between Linux and W98 is not something I do every day. It's just something i have to be able to do, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount
I installed samba on a PC running SuSE 10.2, using the version from the SuSE 10.2 repository (3.0.23). All very nice, except smbmount is missing. As I understand it, this would seem to be because the version offered had not been compiled with the --with-smbmount option. Is my interpretation correct? And if so, how can I fix things? Do I have to download the source and do my own compilation (urrgh)? Or is there a version on a repository somewhere compiled with the --with-smbmount option? I didn't have this problem with either SuSE 10.0 or 10.1, -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On 2007/05/03 17:32 (GMT+0100) John G Walker apparently typed: I installed samba on a PC running SuSE 10.2, using the version from the SuSE 10.2 repository (3.0.23). All very nice, except smbmount is missing. As I understand it, this would seem to be because the version offered had not been compiled with the --with-smbmount option. Is my interpretation correct? And if so, how can I fix things? Do I have to download the source and do my own compilation (urrgh)? Or is there a version on a repository somewhere compiled with the --with-smbmount option? I didn't have this problem with either SuSE 10.0 or 10.1, SUSE wants you to use cifs instead of smbfs, but if you can't get cifs to work right, you can recompile the kernel to enable smbfs. I don't remember exactly the details of getting smbmount back, so I asked on freenode and got the following: 13:22 a-865 kukks: what did we do to get smbmount back in SUSE 10.2? 14:41 kukks a-865: You have to download the samba-client - possibly Suse even dropped stuff from that. you need: smbmount smbmt smbumount 14:42 I always use the samba3 svn source and build all stuff myself 14:44 kukks Then 2 symlinks must be set in /sbin to allow the basic mount cmd to work: mount.smbfs - /usr/bin/smbmount umount.smbfs - /usr/bin/smbumount -- The path of the righteous is like the first gleam of dawn, shining ever brighter till the full light of day. Proverbs 4:18 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount and file-locking
Hi all; I'm having a problem due locking of files using smbmount (or mount -t smb). My samba server used with Windows locks allright, overthise, I have a LTS server that runs a 16-bit system (via DOSEMU) that just don't get the files locked (just ignore their status). Does someone know something about that? Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount failed
In fact I have fixed the problem now. I have compiled smbmnt, but I have not placed the samba files in the install directory that specificed at the compile time, or placed in the $PATH (I have placed it in /tmp for testing...). So the smbmount cannot find smbmnt. It is fixed after I modify the $PATH. However, I have another question, smbmnt accesses a file /etc/mtab, which is sometimes read-only in an embedded system. I have modified the codes so that it now access a dummy file in /tmp. smbmnt seems to be working now but is there any potential problem? Thanks! Hei On 9/22/06, Adam Nielsen [EMAIL PROTECTED] wrote: execvp of smbmnt failed. Error was No such file or directory.smbmnt failed: 1 Did you compile and install the helper program 'smbmnt'? On my system it appears in /usr/bin/smbmnt Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount failed
Hi all, I am trying to cross compile samba version 2.2.12 to an ARM platform (kernel 2.4.20) using arm-tools chain 3.4.2. I get the smbmount compiled, however, when I want to mount a directory that is located in a Windows XP PC, I get the following message: WARNING: The strip dotoption is deprecated unrecognized character set handle_source_env: Failed to open file , Error was Success WARNING: The alternate permissionsoption is deprecated WARNING: The statusoption is deprecated WARNING: The postscriptoption is deprecated WARNING: The printer driveroption is deprecated WARNING: The printer driver fileoption is deprecated WARNING: The printer driver locationoption is deprecated Unable to copy service - source not found: execvp of smbmnt failed. Error was No such file or directory.smbmnt failed: 1 And I cannot mount the directory. I do not think that it is related the permission problem because when I use wrong username/password or try in some wrong target paths, it can report me the corresponding error message. I have tried another tool - smbclient, which works perfectly! Seems that I am just not able to mount with smbmount. Can anyone one elp me to solve this problem? Thanks a lot! Hei -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount failed
execvp of smbmnt failed. Error was No such file or directory.smbmnt failed: 1 Did you compile and install the helper program 'smbmnt'? On my system it appears in /usr/bin/smbmnt Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount and smbumount
Hi, I'm using Ubuntu Dapper Drake 6.06 and Samba 3.0.22 provided by default. I mounted a samba share: smbmount //testpc/folder /home/myuser/folder -o username=,passwd= it mounted successfully. If I do the 'mount' command, I see the samba mounted folder on my mounts. I did some operations and then umounted it: smbumount /home/myuser/folder The 'mount' command shows me that the folder isn't mounted, BUT: I can see inside it and do file operations. The folder isn't umounted. And I cannot umount it because it is not in mount list anymore. Any suggestions? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount and win2003 sp1
Volker Lendecke schrieb: On Mon, Jun 05, 2006 at 07:54:51PM +0800, Latrell wrote: I encountered a problem with smbmount and win2003 sp1. It is very likely that smbfs does not do some of the advanced authentication options that W2k3 SP1 now requires. Please test the cifs filesystem, smbfs is unsupported for a while now. I've had the same problem a while ago when I had to copy a single file to the 2003sp1-server. I managed to copy it by using smbclient and playing around with the put command. Foobar code for the console: smbclient //win/share -U username%password -W domain -o get foo.txt; put bar.txt; exit -W domain is for servers, which are sitting in a different Domain. If you plan to make a script for Cron, don't forget to make it non-readeable for non-roots because of the cleartext-password! You can use the command without %password. You'll have to type in the password, it will not be displayed then. Files 2GB can't be transferred this way. Don't ask me why... Greets, Benjamin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount limitations
Hello, I am trying to use smbmount to mount a Samba share that is larger than 2 TB. However, the amount of disk space that is displayed from the df -k command for the mounted share is only 2 TB, and when I try to access the share, my terminal session hangs. Is there a limitation on the size of the share that can be mounted? Thanks, Daryl Ashley Institute for Advanded Technology -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount problem - Input/output error
Hello, I am trying to mount a samba partition using a CGI program (C language) and a get the following error when i do $ df: df: `/mnt/b': Input/output error The samba log bring the following message: smbd/service.c:close_cnum(646) srv (192.168.1.2) closed connection to service b I am using the command smbmount //192.168.1.2/b /mnt/b -o username=user,password=pass,ip=192.168.1.2 Can anyone help? -- Rodrigo J. Florenciano -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount uclinux
Hello All, Is there any information other than uclinux-dev mailing list that outlines the proper way to use smbmount on uclinux? I have looked through the mail lists on uclinux-dev and googled everything that I could think of. I have tried every form of the smbmount //windowsbox/share /mnt -o options I can think of. I always get ERRDOS ERRnoaccess (Access Denied). Robert Armenta /table /Pre HTML br br br The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.br br /HTML -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount vs. mount -t cifs
Hi, During testing I discovered something interesting with different mount methods. This is the environment: PDC = RedHat rhel4, 2.6.9-34.0.2ELsmp kernel, samba version 3.0.10-1.4E.6 Client = SuSE sles9, 2.6.5-7244-smp kernel, samba version 3.0.20b-3.4-SUSE I have a share (shareB) with attribute readonly = yes (smb.conf is included below). Mounting the share as user1 and opening a file in the share for writing and appending gives me the following results: Could not open for writing mounted with mount -t cifs Could not open for writing mounted with smbmount Could not open for appending mounted with mount -t cifs Opened for appending mount with smbmount (unexpected result) After changing the share attributes from readonly = yes to writelist = user1 and restarting smbd, I tried again with these results: Could not open for writing mounted with mount -t cifs (unexpected result) Opened for writing mounted with smbmount Opened for appending mounted with mount -t cifs Opened for appending mounted with smbmount I tried this with open in perl and fopen in c with identical results. Is this a (known) problem? # # Generated by /usr/share/doc/samba-3.0.10/misc/modify_samba_config.pl # [global] adminusers= Administrator, root addgroupscript= /usr/sbin/groupadd -p %g addsharecommand = /usr/share/doc/samba-3.0.10 /misc/modify_samba_config.pl winbindusedefaultdomain = no deletesharecommand= /usr/share/doc/samba-3.0.10 /misc/modify_samba_config.pl deleteuserfromgroupscript = /usr/sbin/groupmod -x %u %g maxlogsize= 50 adduserscript = /usr/sbin/useradd -m %u idmapuid = 16777216-33554431 dnsproxy = no deleteprintercommand = /usr/share/doc/samba-3.0.10 /misc/modify_samba_config.pl addmachinescript = /usr/sbin/useradd %u setprimarygroupscript = /usr/sbin/usermod -g %g %u addprintercommand = /usr/share/doc/samba-3.0.10 /misc/modify_samba_config.pl printcapname = /etc/printcap domainlogons = yes deleteuserscript = /usr/sbin/userdel -r %u passdbbackend = tdbsam logfile = /var/log/samba/%m.log socketoptions = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 cupsoptions = raw loadprinters = yes addusertogroupscript = /usr/sbin/groupmod -m %u %g workgroup = SAMBA_TEST templateshell = /bin/false serverstring = Samba Server security = user domainmaster = yes idmapgid = 16777216-33554431 ## Section - [shareD] [shareD] read list = @root,@users write list= user1 path = /tmp/shareD ## Section - [printers] [printers] comment = All Printers browseable= no writable = no printable = yes path = /var/spool/samba guestok = no ## Section - [shareA] [shareA] readlist = user1 path = /tmp/shareA writelist = user1 ## Section - [shareC] [shareC] readlist = @root,@users path = /tmp/shareC writelist = user1,user2 ## Section - [homes] [homes] comment = Home Directories browseable= no writable = yes ## Section - [shareB] [shareB] readonly = yes path = /tmp/shareB # # end of generated smb.conf # ## [pshareA] [pshareA] printer = filepr directorymask = 0775 createmask = 0664 comment = filepr printable = Yes path= /var/spool/samba writelist = @ntadmin root ## [pshareB] [pshareB] printer = filepr directorymask = 0775 createmask = 0664 comment = filepr printable = Yes path= /var/spool/samba writelist = @ntadmin root Sincerely,Don Watson Linux Technology and Solutions; Beaverton, OR 503-578-4861/TL: 775-4861; [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount ... error [Solution]
Bob McGowan wrote: I've spent the last 3 hours (it seems like) going over postings in the comp.protocols.smb newsgroup trying to find a solution for this problem. It seems that a lot of folks have had the issue, but none of the posts I looked at had any useful resolution. Here's the error: 28968: protocol negotiation failed SMB connection failed I'm running RHEL 4 Workstation with Samba Version 3.0.10-1.4E. I'm running as a client, not a server, and am attempting to mount a share from a Windows server. There is much networking mumbo-jumbo in the way, but I don't think any of it applies, since I can telnet to port 139 on the server in question and telnet connects nicely. But any Samba utility I use fails with the above error, never getting to the point where it asks for a password. The main command I need to run is: smbmount //.../share /data/mount -o username=me It should prompt me for my password. The domain is specified correctly in the smb.conf file. In fact, I can use 'smbmount' to access another system in the company, without any problem. Any suggestions and assistance is much appreciated. *Please* respond to me directly as I'm not subscribed to the list. Thanks in advance. Bob This is, as is the case for many questions, user error. In this case, specifically lack of knowledge. Full access requires more than just port 139 (netbios), you also need port 445 (SMB). So I didn't know I needed to check port 445 also. It turns out the firewall was not quite correctly configured and so it was rejecting port 445 and causing this error. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount ... error
I've spent the last 3 hours (it seems like) going over postings in the comp.protocols.smb newsgroup trying to find a solution for this problem. It seems that a lot of folks have had the issue, but none of the posts I looked at had any useful resolution. Here's the error: 28968: protocol negotiation failed SMB connection failed I'm running RHEL 4 Workstation with Samba Version 3.0.10-1.4E. I'm running as a client, not a server, and am attempting to mount a share from a Windows server. There is much networking mumbo-jumbo in the way, but I don't think any of it applies, since I can telnet to port 139 on the server in question and telnet connects nicely. But any Samba utility I use fails with the above error, never getting to the point where it asks for a password. The main command I need to run is: smbmount //.../share /data/mount -o username=me It should prompt me for my password. The domain is specified correctly in the smb.conf file. In fact, I can use 'smbmount' to access another system in the company, without any problem. Any suggestions and assistance is much appreciated. *Please* respond to me directly as I'm not subscribed to the list. Thanks in advance. Bob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount
I am moving FROM: RH EL AS 3.0, Kernel is 2.1.21-4, Samba is 3.0.0-14.3E (This is what came with the RH distribution) TO: Fedora Core 5 Kernel is 2.6.16-1.2122_FC5 Samba is 3.0.22-1.fc5 (Both kernel and samba have been upgraded from the distribution.) I can't find the smbmount (or smbumount) command. I am running VMWare and want to be able to move files between the host WIndows XP system and the guest Linux system. Under RH I could issue an smbmount command and mount the XP systems file system and then use all the file tools. I know I can use smbclient but mounting the host file system is much easier. man indicates No manual entry for smbmount The man entry for mount talks about using -t smbfs and refers to /sbin/mount.smbfs but this doesn't exist either. My RH system has a link from /sbin/mount.smbfs to /usr/bin/smbmount ls -l /usr/sbin/smb* yields: -rwxr-xr-x 1 root root 1982532 Mar 30 17:29 /usr/bin/smbcacls -rwxr-xr-x 1 root root 978844 Mar 30 17:29 /usr/bin/smbclient -rwxr-xr-x 1 root root 657248 Mar 30 17:29 /usr/bin/smbcontrol -rwxr-xr-x 1 root root 1873448 Mar 30 17:29 /usr/bin/smbcquotas -rwxr-xr-x 1 root root 1949732 Mar 30 17:29 /usr/bin/smbget -rwxr-xr-x 1 root root 1886692 Mar 30 17:29 /usr/bin/smbpasswd -rwxr-xr-x 1 root root2295 Mar 30 17:29 /usr/bin/smbprint -rwxr-xr-x 1 root root 887872 Mar 30 17:29 /usr/bin/smbspool -rwxr-xr-x 1 root root 636412 Mar 30 17:29 /usr/bin/smbstatus -rwxr-xr-x 1 root root4896 Mar 30 17:29 /usr/bin/smbtar -rwxr-xr-x 1 root root 892668 Mar 30 17:29 /usr/bin/smbtree Douglas Corner Herndon, VA [EMAIL PROTECTED] - -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Sun, Jun 11, 2006 at 09:22:20AM -0400, Douglas Corner wrote: I am moving FROM: RH EL AS 3.0, Kernel is 2.1.21-4, Samba is 3.0.0-14.3E (This is what came with the RH distribution) TO: Fedora Core 5 Kernel is 2.6.16-1.2122_FC5 Samba is 3.0.22-1.fc5 (Both kernel and samba have been upgraded from the distribution.) I can't find the smbmount (or smbumount) command. The FC5 kernel ditched smbfs in favor of cifs. I'm pretty sure we mentioned it in the release notes. You can use mount -t cifs ... to mount remote SMB filesystems using the Liunx CIFS filesystem. Further information about the Linux CIFS filesystem can be found at http://linux-cifs.samba.org/ Bug reports about the Linux CIFS filesystem in Fedora 5 should go to bugzilla.redhat.com under the kernel component. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount and win2003 sp1
It is very likely that smbfs does not do some of the advanced authentication options that W2k3 SP1 now requires. Please test the cifs filesystem, smbfs is unsupported for a while now. Volker I tried mount.cifs, and get the following message: [EMAIL PROTECTED]:# mount -t cifs //localhost/share1 /tmp/testmount/ -o username=u1,password=u11 mount error 22 = Invalid argument Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) Anything wrong with my option? Thanks, Latrell - Original Message - From: Volker Lendecke [EMAIL PROTECTED] To: Latrell [EMAIL PROTECTED] Cc: samba@lists.samba.org Sent: Monday, June 05, 2006 8:25 PM Subject: Re: [Samba] smbmount and win2003 sp1 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount and win2003 sp1
I did some more tests. Local user can cifsmount correctly, but when I joined domain (2003 ad domain with sp1), cifsmount will fail. Then same condition also happened on smbmount. Why does sp1 cause smbmount and cifsmount fail? [EMAIL PROTECTED]:~# mount.cifs //localhost/share1 /tmp/testmount/ -o username=NAS\adu1,password=adu1 mount error 22 = Invalid argument Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) I also tried username=adu1, NAS\adu1, still not worked. Latrell - Original Message - From: Latrell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: samba@lists.samba.org Sent: Tuesday, June 06, 2006 7:35 PM Subject: Re: [Samba] smbmount and win2003 sp1 It is very likely that smbfs does not do some of the advanced authentication options that W2k3 SP1 now requires. Please test the cifs filesystem, smbfs is unsupported for a while now. Volker I tried mount.cifs, and get the following message: [EMAIL PROTECTED]:# mount -t cifs //localhost/share1 /tmp/testmount/ -o username=u1,password=u11 mount error 22 = Invalid argument Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) Anything wrong with my option? Thanks, Latrell - Original Message - From: Volker Lendecke [EMAIL PROTECTED] To: Latrell [EMAIL PROTECTED] Cc: samba@lists.samba.org Sent: Monday, June 05, 2006 8:25 PM Subject: Re: [Samba] smbmount and win2003 sp1 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount and win2003 sp1
Hi All: I encountered a problem with smbmount and win2003 sp1. Before I upgrade sp1, everything works fine. But after sp1, smbmount can't work. The command and error message are as follows: smbmount //localhost/share1 /tmp/mountest -o username=domainu1,password=password ERRDOS - ERRnoaccess (Access Denied.) SMB connection failed I also checked the release note about the issue, and found a fix on 3.0.14a about: Compatibility issues between Winbind and Windows 2003 SP1 domain controllers (*2k3sp1*). Does it fix my bug? My version is 3.0.21c. Why did I have the problem? Thanks, Latrell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount and win2003 sp1
On Mon, Jun 05, 2006 at 07:54:51PM +0800, Latrell wrote: I encountered a problem with smbmount and win2003 sp1. It is very likely that smbfs does not do some of the advanced authentication options that W2k3 SP1 now requires. Please test the cifs filesystem, smbfs is unsupported for a while now. Volker pgpW3rckWMYEi.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount and win2003 sp1
Hi All: I encountered a problem with smbmount and win2003 sp1. Before I upgrade sp1, everything works fine. But after sp1, smbmount can't work. The command and error message are as follows: smbmount //localhost/share1 /tmp/mountest -o username=domainu1,password=password ERRDOS - ERRnoaccess (Access Denied.) SMB connection failed I also checked the release note about the issue, and found a fix on 3.0.14a about: Compatibility issues between Winbind and Windows 2003 SP1 domain controllers (*2k3sp1*). Does it fix my bug? My version is 3.0.21c. Why did I have the problem? Thanks, Latrell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount and credentials
When I run the following command: smbmount //192.168.0.1/backup /mnt/backup rw uid=root gid=root credentials=/etc/smbcreds I get this: WARNING: The printer admin option is deprecated Password: smbcreds contains this: username=root password=rootpassword Can anyone tell me why it isn't reading the password from the credentials file, and why the printer admin warning is appearing? -- Ray Greene -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Smbmount and credentials
smbmount //192.168.0.1/backup /mnt/backup rw uid=root gid=root credentials=/etc/smbcreds Can anyone tell me why it isn't reading the password from the credentials file Probably because you forgot the -o flag, and there aren't any commas between the options :-) smbmount //192.168.0.1/backup /mnt/backup -o rw,uid=root,gid=root,credentials=/etc/smbcreds and why the printer admin warning is appearing? There is a 'printer admin = ...' option in your smb.conf. If you're not sharing any printers, remove this line to get rid of the error. Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount right's Problems
Hello, i have problems with the right's, when i mount my home share. The Version on the Server is (debian): 3.0.14a-6 0 The Version on the Client is (debian): 3.0.14a-3 0 This is the smb.conf on the Server side: [global] unix extensions = no panic action = /usr/share/samba/panic-action %d workgroup = abc123 server string = %h server (Samba %v) guest account = nobody invalid users = root log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 security = user encrypt passwords = true passdb backend = smbpasswd guest socket options = TCP_NODELAY dns proxy = no passwd program = /usr/bin/passwd %u obey pam restrictions = yes [homes] comment = Home Directories browseable = no writable = yes create mask = 0755 directory mask = 0755 This is my problem: when i have mount my home share - I see not the correct Permissions, thats the home share have on the Server side. When i make a chmod 644 of any File, on the Clientside the Permissions are right. May the rights on the Server have not change ... Two hours Later the Rights on the Client side change to the rights on the Server side. What make i wrongly!? Thanks for your help. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount right's Problem
Hello, i have problems with the right's, when i mount my home share. The Version on the Server is (debian): 3.0.14a-6 0 The Version on the Client is (debian): 3.0.14a-3 0 This is the smb.conf on the Server side: [global] unix extensions = no panic action = /usr/share/samba/panic-action %d workgroup = abc123 server string = %h server (Samba %v) guest account = nobody invalid users = root log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 security = user encrypt passwords = true passdb backend = smbpasswd guest socket options = TCP_NODELAY dns proxy = no passwd program = /usr/bin/passwd %u obey pam restrictions = yes [homes] comment = Home Directories browseable = no writable = yes create mask = 0755 directory mask = 0755 This is my problem: when i have mount my home share - I see not the correct Permissions, thats the home share have on the Server side. When i make a chmod 644 of any File, on the Clientside the Permissions are right. May the rights on the Server have not change ... Two hours Later the Rights on the Client side change to the rights on the Server side. What make i wrongly!? Thanks for your help. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount syntax for two users?
I want to allow two users to mount a share. Would the syntax be: smbmount //computername/share /mnt/computername -o username=user1,user2 ?? Larry -- Larry Alkoff N2LA - Austin TX Using Thunderbird on Slackware Linux -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Smbmount syntax for two users?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Alkoff a écrit : I want to allow two users to mount a share. Would the syntax be: smbmount //computername/share /mnt/computername -o username=user1,user2 ?? Larry No, -o username=xxx it's for specify the username which must be used for the connexion to the server, not the user which have the permission to mount a share. - -- Stéphane Purnelle [EMAIL PROTECTED] Site Web : http://www.linuxplusvalue.be -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD7igs8tswkE3d0ecRAjXyAJ9EUw2DGFWhKT32SNT8JR3rsHmY9gCfR1Bw Hy7SDl5NW5K+KK4r53n8/A0= =5SR6 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Smbmount syntax for two users?
Stéphane Purnelle wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Alkoff a écrit : I want to allow two users to mount a share. Would the syntax be: smbmount //computername/share /mnt/computername -o username=user1,user2 ?? Larry No, -o username=xxx it's for specify the username which must be used for the connexion to the server, not the user which have the permission to mount a share. Thanks for the reply Stéphane. Is it possible to specify two such usernames? I want to allow both root and user lba to connect to samba shares. Larry -- Larry Alkoff N2LA - Austin TX Using Thunderbird on Slackware Linux -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount and permission denied
Hello all. I just run across the same problem. Did you find the solution? TIA Reto -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount inconsistant counts
Hey Guys, I have a strange problem. I have a RHFC3 box connected to a Windows 2003 advanced server share via smbmount. This is what my entry looks like in /etc/fstab //datasilo01/tdhcamhsol /mnt/tdhcamhsol smbfs credentials=/root/.smbpasswd,uid=600,gid=501,ttl=500 We run scripts on this share that count the number of images in the directory vs. the number in a text file. But if I do something like ls -R 0058 | grep 'tif' | wc -l I get like 3059 like 8 times out of 10. But it will be off by one or more the other times. Even if I don't use a grep statement and just output it to a file, I've done like a sample of 10 output files and then did a diff on them and it simply missed a tif image name. I thought it might be a cache timing issue, but even after the directory is no longer being added to the count is off sometimes. This is driving me crazy, and it's a critical issue for our scripts to work properly. I've been wondering if I should switch to a CIFS mount instead? Would this solve this kind of issue? I've looked at the network cards for any dropped packets or errors and it's 100% clean. TIA, James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount - Permission denied after upgrade to FC2
http://lists.samba.org/archive/samba/2004-August/091522.html Have you resolved this issue? I am experiencing the same thing. Thanks, Chris Ancelin Product Integration Engineer Adtec Digital 904.720.2003 x 241 Office # 904.887.6869 Mobile # -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount codepage/iocharset settings vs NT4
Hi, I'm in the process of setting up a backup server for a somewhat antiquated NT4 server. Backup server is CentOS-4 (~ RHEL-4), kernel-2.6.9-11.EL, samba-client-3.0.10-1.4E, rsync-2.6.3-1, LANG=en_US.UTF-8. NT4 shares are mounted on the server and rsynced to local disk. This setup is working pretty well, however on the NT box there are some files with names containing odd characters like accented characters and ellipsis. I'm a bit at a loss as to the correct settings of the smbmount iocharset and codepage parameters to use, and whether the display charset and unix charset options in smb.conf are relevant to the mounts. I've setup a test share. An ls in smbclient gives me the correct output in a gnome-terminal and an mget gets me the files with their correctly utf8itfied names (console seemed ok until after a toggle to X): $ smbclient -U auser //david-bowie/Test Password: Domain=[EVERYTHING] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] smb: \ ls . D0 Sat Oct 29 18:58:49 2005 .. D0 Sat Oct 29 18:58:49 2005 ellipsis zijn heel fijn (…).doc A24064 Sat Oct 29 18:57:14 2005 Nogmaals ellipsis ….doc A24064 Sat Oct 29 18:58:31 2005 één document á €50.doc A24064 Sat Oct 29 18:55:28 2005 één document.doc A24064 Sat Oct 29 18:54:20 2005 ‘‰’.doc A24064 Sat Oct 29 18:57:55 2005 “quotes”.docA24064 Sat Oct 29 18:53:40 2005 52004 blocks of size 262144. 2165 blocks available However, an smbmount without any charset options gives me the following result: $ sudo mount -o username=auser //david-bowie/Test /mnt/tmp Password: $ ls /mnt/tmp `%'.doc ??n document.doc ellipsis zijn heel fijn (.).doc Nogmaals ellipsis ..doc ??n document ? ?50.doc quotes.doc Using cp850 improves the output somewhat: $ sudo mount -o username=auser,codepage=cp850 //david-bowie/Test /mnt/tmp Password: $ ls /mnt/tmp `%'.doc ellipsis zijn heel fijn (.).doc één document á ?50.doc Nogmaals ellipsis ..doc één document.docquotes.doc I assumed the code page used by NT4 was cp1252 (MS-ANSI), but using cp1252 for the codepage gives me the same output for these files as the mount with no codepage option set. To make a long story short: What are the proper options to pass to smbmount and/or set in /etc/samba/smb.conf? Thanks, Leonard. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount codepage/iocharset settings vs NT4
Hello Andrew, On Mon, 2005-10-31 at 08:34 +1100, Andrew Bartlett wrote: This setup is working pretty well, however on the NT box there are some files with names containing odd characters like accented characters and ellipsis. I'm a bit at a loss as to the correct settings of the smbmount iocharset and codepage parameters to use, and whether the display charset and unix charset options in smb.conf are relevant to the mounts. You should use the CIFS VFS for your backup operations, as it will correctly use unicode on the wire, and therefore allow a correct utf8 translation. smbfs is considered deprecated, and certainly should not be used for new installations. Ok. $ sudo mount -t cifs -o username=auser //david-bowie/Test /mnt/tmp Password: [EMAIL PROTECTED] ~]$ ls /mnt/tmp één document á €50.doc ellipsis zijn heel fijn (…).doc ‘?颂ꋩ?? één document.docNogmaals ellipsis ….doc “???鲂닩? That indeed solves the issue for the more common cases. Luckily in real life I don't have to deal with these cases but what about the below 2 file names? They are printed correctly in smbclient. ‘‰’.doc A24064 Sat Oct 29 18:57:55 2005 “quotes”.docA24064 Sat Oct 29 18:53:40 2005 Leonard. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount codepage/iocharset settings vs NT4
On Sun, 2005-10-30 at 23:08 +0100, Leonard den Ottolander wrote: Hello Andrew, On Mon, 2005-10-31 at 08:34 +1100, Andrew Bartlett wrote: This setup is working pretty well, however on the NT box there are some files with names containing odd characters like accented characters and ellipsis. I'm a bit at a loss as to the correct settings of the smbmount iocharset and codepage parameters to use, and whether the display charset and unix charset options in smb.conf are relevant to the mounts. You should use the CIFS VFS for your backup operations, as it will correctly use unicode on the wire, and therefore allow a correct utf8 translation. smbfs is considered deprecated, and certainly should not be used for new installations. Ok. $ sudo mount -t cifs -o username=auser //david-bowie/Test /mnt/tmp Password: [EMAIL PROTECTED] ~]$ ls /mnt/tmp één document á €50.doc ellipsis zijn heel fijn (…).doc ‘?颂ꋩ?? één document.docNogmaals ellipsis ….doc “???鲂닩? That indeed solves the issue for the more common cases. Luckily in real life I don't have to deal with these cases but what about the below 2 file names? They are printed correctly in smbclient. ‘‰’.doc A24064 Sat Oct 29 18:57:55 2005 “quotes”.docA24064 Sat Oct 29 18:53:40 2005 This will be smbclient correctly finding your 'display charset' (localle) from the environment which the cifsvfs can't tell from kernel space. You should use UTF8 everywhere if possible. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Samba Developer, SuSE Labs, Novell Inc.http://suse.de Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount codepage/iocharset settings vs NT4
On Sun, Oct 30, 2005 at 11:08:06PM +0100, Leonard den Ottolander wrote: Hello Andrew, On Mon, 2005-10-31 at 08:34 +1100, Andrew Bartlett wrote: This setup is working pretty well, however on the NT box there are some files with names containing odd characters like accented characters and ellipsis. I'm a bit at a loss as to the correct settings of the smbmount iocharset and codepage parameters to use, and whether the display charset and unix charset options in smb.conf are relevant to the mounts. You should use the CIFS VFS for your backup operations, as it will correctly use unicode on the wire, and therefore allow a correct utf8 translation. smbfs is considered deprecated, and certainly should not be used for new installations. Ok. $ sudo mount -t cifs -o username=auser //david-bowie/Test /mnt/tmp Password: [EMAIL PROTECTED] ~]$ ls /mnt/tmp één document á €50.doc ellipsis zijn heel fijn (…).doc ‘?颂ꋩ?? één document.docNogmaals ellipsis ….doc “???鲂닩? That indeed solves the issue for the more common cases. Luckily in real life I don't have to deal with these cases but what about the below 2 file names? They are printed correctly in smbclient. Log a bug with Steve French. He should be using similar unicode conversions as smbclient. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount codepage/iocharset settings vs NT4
Hello Andrew, On Mon, 2005-10-31 at 09:16 +1100, Andrew Bartlett wrote: On Sun, 2005-10-30 at 23:08 +0100, Leonard den Ottolander wrote: This will be smbclient correctly finding your 'display charset' (localle) from the environment which the cifsvfs can't tell from kernel space. You should use UTF8 everywhere if possible. LANG=en_US.UTF-8. Setting display charset and unix charset to UTF8 in smb.conf does not solve this. I'll consider filing a bug as Jeremy suggested. Right now I'm just going to be content :) . Thanks guys. Leonard. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount codepage/iocharset settings vs NT4
On Sun, 2005-10-30 at 23:32 +0100, Leonard den Ottolander wrote: Hello Andrew, On Mon, 2005-10-31 at 09:16 +1100, Andrew Bartlett wrote: On Sun, 2005-10-30 at 23:08 +0100, Leonard den Ottolander wrote: This will be smbclient correctly finding your 'display charset' (localle) from the environment which the cifsvfs can't tell from kernel space. You should use UTF8 everywhere if possible. LANG=en_US.UTF-8. Setting display charset and unix charset to UTF8 in smb.conf does not solve this. Just for clarification, that is because the CIFS VFS doesn't read our (userspace) smb.conf file, and smbclient didn't change because it was already on UTF8. I'll consider filing a bug as Jeremy suggested. Sounds like a bug to me. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Samba Developer, SuSE Labs, Novell Inc.http://suse.de Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount not obeying locks; it will not delete but will overwrite locked files.
Hi all, I have a problem with smbmount. I use smbmount to mount a tree from a server (either windows xp or linux samba). Then I access the files in it with the linux smbmount and with windows. When I open a file (let's say document.doc) in windows with word this file is sucessfully locked and I cannot overwrite it on another windows computer. But when I want to write-access this file with the linux client I can overwrite it without problems. Though deleting is not possible... example: First I open document.doc with word on the windows machine. Then I try to overwrite document.doc on a second windows machine. This cannot be done offcourse. Then I type to overwrite (echo xxxdocument.doc) document.doc on a linux machine (mounted through smbfs). To my surprise this could be done. Why can the linux smb client overwrite files that cannot be overwritten on a windows client? ps If I use a linux samba server instead of a windows xp server the problem stays. So it's not a problem with the server. Linux: Red Hat Enterprise Linux ES release 4 (Nahant Update 1) Kernel: 2.6.9-11.EL mount.smbfs: Version 3.0.10-1.4E Regards, Eelco Grakist The Netherlands -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount can't take more than one option
Hello I have a problem with smbmount (3.0.14a, Debian Sarge, kernel 2.6.8-2). I was using the following (on the command line, not /etc/fstab): smbmount //myserver/myshare /mount/smbmount/ -o credentials=~/smbcredentials, ro, codepage=cp850, iocharset=iso8859-15 and french caracters (éèà...) were not displayed correctly. I thought it was a problem with the codepage and credentials options, but I noticed the mount was read write. If I type: smbmount //myserver/myshare /mount/smbmount/ -o ro, credentials=~/smbcredentials, codepage=cp850, iocharset=iso8859-15 I am asked for a password. smbmount doesn't take the second and following options, and doesn't complain in case of errors in options. If I type: smbmount //myserver/myshare /mount/smbmount/ -o fshkfhskfhk I am just asked for a password. How can I correct this and pass smbmount more than one option ? Thanks in advance -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount can't take more than one option
Stupid error. My options were not comma, but comma and space, separated. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount of services with embedded spaces
smbmount v3.0.13 Hi, I'm trying to set-up my /etc/fstab configuration file to automatically map to a Samba share at bootup. This is not working I think because the share that I require has a space within it. This seems to confuse fstab/smbmount and me. An interactive command such as: smbmount '//nslu2/DISK 1' /mnt/nslu2/disk-1 works fine. However the service name does not seem to have the quotes when mount passes control to smbmount. Naturally, commands such as: smbmount //nslu2/DISK 1 /mnt/nslu2/disk-1 don't work. Is there anyway to specify the service name without quotes but keep the embedded space ? I've also tried: smbmount //nslu2/DISK\0401 /mnt/nslu2/disk-1 this comes back with: 26920: tree connect failed: ERRDOS - ERRnosuchshare (You specified an invalid share name) SMB connection fail Any ideas ? Steve ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount problem
hi all.. i'm using samba 3.0.11 and i got a weird problem here.. my domain server have samba 3.0.11 running with ldap support. both my pc and my server are using slackware 10.1. i can either joining domain or browsing other network members using smbclient without problem. but when i try to mount a client service i got this error message: session setup failed: ERRSRV - 2240 SMB connection failed i tried to find out what '2240' meant and it came to INVALID_NT_WORKSTATION error message. FYI, I have 'sambaUserWorkstation' attribute in my LDAP server and smbmount works fine if I remove it. but I got to keep the attribute based on my company policy. I have tried 'mount -t smbfs //CLIENT_NAME/SHARE /mnt/samba -o username=my_username' but it fail to the same error. I have no idea what's wrong with my samba (client / server). Please help me :( here is the smb.conf on my pc: --- [global] workgroup = KAPUKVALLEY netbios name = pinix-newage server string = :: DigitaLinux :: interfaces = lo, eth0 security = SERVER encrypt passwords = No password server = 172.168.0.1 max log size = 10 socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 hostname lookups = Yes load printers = No disable spoolss = Yes show add printer wizard = No preferred master = No local master = No domain master = No dns proxy = No wins server = 172.168.0.1 message command = /bin/mail -s 'Message from %s' root %s; rm %s guest ok = Yes dos filemode = Yes dos filetimes = Yes dos filetime resolution = Yes [Cineplex 1] comment = Online Cinema Studio 1 path = /mnt/data/Cineplex 1 [Cineplex 2] comment = Online Cinema Studio 2 path = /mnt/apps4/Cineplex 2 - and the smb.conf on my samba domain server: - [global] dos charset = 850 unix charset = ISO8859-1 workgroup = KAPUKVALLEY server string = Domain Server interfaces = lo, eth0 bind interfaces only = Yes passdb backend = ldapsam:ldap://127.0.0.1/ syslog = 0 log file = /var/log/samba/%m max log size = 10 large readwrite = No name resolve order = lmhosts time server = Yes deadtime = 10 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = No disable spoolss = Yes show add printer wizard = No logon script = logon.bat logon path = logon home = domain logons = Yes os level = 32 preferred master = Yes domain master = Yes wins support = Yes ldap admin dn = cn=Manager,dc=kapukvalley,dc=net ldap delete dn = Yes ldap group suffix = ou=Groups ldap idmap suffix = ou=Users,dc=kapukvalley,dc=net ldap machine suffix = ou=Computers ldap passwd sync = Yes ldap suffix = dc=kapukvalley,dc=net ldap user suffix = ou=Users host msdfs = Yes admin users = @Domain Admins create mask = 0664 directory mask = 0775 hosts allow = 127.0.0.1, 172.168.0.0/23 hosts deny = 0.0.0.0/0 map acl inherit = Yes case sensitive = No dont descend = /proc,/dev,/etc,/lib,/lost+found,/initrd dos filemode = Yes dos filetimes = Yes [kaval info] comment = Kapuk Valley Info path = /home/samba/kaval invalid users = root thanks in advance. best regards, M. Novan Adrian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount symbolic links not followed
Hello, When I smbmount a Samba share on a station running Ubuntu 5.04 (Samba 3.0.14a) symbolic links located on the share are not followed (they appear as symbolic links). smbmount on Mandrake 7.2 and 9.2 stations work normally. smbclient works normally, with symbolic links resolution. The Samba client in Nautilus works normally. Windows clients follow the symbolic links normally. The Samba server is version 3.0.14a runnning under Mandrake 9.2. I browsed the web to no avail. I tried to copile and install variuous Samba versions on my Ubunt 5.04 station to no avail (Samba 3.0.14a, Samba 2.2.12). Thank you for your help! Sincerely, Martin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount and daily savings time shifted timestamps?
Background: I use rsync to shuffles files around from my production server and testing server. The testing server's central file share (the one that the production server pulls from) is a smbmount from an internal file server (OSX 10.4, but this is irrelevant as you'll see). I had to switch from NFS to Samba after the 10.4 upgrade due to their new NFS implementation breaking readdir(). After doing this, all my rsync's from the test server (on the smbmount directory) to the production server started listing nearly every file in any directory I'd sync. Rsync builds its transfer list from file sizes and *timestamps*. What's happening: On smbmount'd shares, files created during the winter have their time stamp listed as one hour earlier as they are on the actual servers. This is happening not only on the OSX 10.4 box to the production server, but also if the *production server* does a local mount (eg: mount -t smbfs -U username //127.0.0.1/username /blah) of some share, such as a home directory. Here's some sample output: -- outputs from the production server connecting to 127.0.0.1 -- In the smbmount: -rwxrwxr-x 1 root root 27613 Jan 20 08:16 2004 1040EZ.pdf* -rwxrwxr-x 1 root root 11044 May 11 09:44 payfuse.tcpdump* in the smbclient: 2004 1040EZ.pdf 27613 Thu Jan 20 09:16:54 2005 payfuse.tcpdump 11044 Wed May 11 09:44:42 2005 In my actual home dir: -rw-rw-r-- 1 gabebug mis 27613 Jan 20 09:16 2004 1040EZ.pdf -rw-rw-r-- 1 gabebug gabebug 11044 May 11 09:44 payfuse.tcpdump -- and some examples from the example cited in Background, the 10.4 server to the production server -- Locally, on the OSX Samba server: -rw-rw-r-- + 1 rachelbu mudbug 2266 Mar 21 09:33 damon1.jpg A separate random OSX client, over AFP: -rwxr--r-- 1 gabebug gabebug 2266 Mar 21 09:33 damon1.jpg* Production server, over `smbclient`: damon1.jpg 2266 Mon Mar 21 09:33:23 2005 Production server, over `smbmount` (mount -t smbfs): -rwxrwxr-x 1 root root 2266 Mar 21 08:33 damon1.jpg* This behavior is obviously only occurring in smbmount, and smbclient isn't affected. This also isn't a reaction between OSX and the production server, as it occurs just the same locally. The production client is running Linux kernel version 2.4.29 and Samba 3.0.13. These are a minor version behind, but I saw nothing mentioning timestamps/DST in either changelogs. The /etc/localtime on all of my servers is set to /usr/share/zoneinfo/ US/Central I'm unclear if this is a kernel VFS/SMBFS bug, a smbmount bug, or some configuration flag I haven't run into, but either way the inconsistency between smbmount and smbclient is concerning. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount codepage / iocharset problem w/ W2k
Hi: I have written to this list once before regarding the same problem. (ref smbmount problem on 03/28/2005) Paul Gienger sugested asking the kernel boys as they maintain smbmount. Maybe my problem wasn't deserving of a reply from them, maybe I subscribed to the wrong list. Can someone suggest a kernel list where I may get a useful reply? smbclient's ftp like interface works correctly, however the debug output (--debug 10) isn't helping me determine what codepage/iocharset is being used. Is there a way to determine what codepage and iocharset are being used? My smb.conf contains dos charset = 850 unix charset = ISO8859-1 display charset = ISO8859-1 so can I assume it's cp850 the codepage being used by smbclient? is iso8859-1 the charset being used by smbclient? Lastly can someone send me google keyword(s) where I can read up on how the smb protocol uses codepages and iocharsets? (just to clear up the issue for me?) Is it safe to presume that the MS implementation of the SMB protocol if compatible (they like to invent stuff just to muck up standards as I hear)? TIA Leo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount -- text file busy?
I'm trying to copy files from a Windows system to a Linux system using smbmount. Everything works fine until I hit a text file that is open read/write on the Windows system, such as an SQL Server database file. At that point, I get a Text file busy (26) error message, and the copy process (rsync) skips the file. Is there any way around this, short of stopping the SQL Server service and restarting it? I just need to read an in-use copy of the file in question. Is smbmount capable of opening a file in shared mode, or is this a limitation on the Windows side of things? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount non root write access denied
I am using smbfs in /etc/fstab on Debian. The share mounts with no problem but only root can write to it - not the user. The user sharing and the user I want to have access have the same username but not the same userid The user can not write. I am using uid=username gid=username fmask=777 dmask=777 and most importantly rw The directory is shared from centos (redhat enterprise linux) 4 Everything works fine on windows so I think it is a smbmount/linux client problem. From memory I got round the problem in the past by making sure the user id of the user on both the client and the server was the same. This is not an option on the current setup. The mount point is owned by the user btw. Any help appreciated. Thanks, Tim. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount problem
Hello all: I have an annoying problem with smbmount; My Win2k server has many folders and files named with accented characters (cp850 and/or cp860 or European w/0 euro or Portugese). My mount command is: mount -t smbfs -o username=leo,codepage=cp850 //servername/d$ /mnt/pt to mount my d: drive at /mnt/pt I am prompted for my password and the shared folder is mounted. I can see all files and folders and navigate them except for that I noticed Á appear as A ã and õ appears as a and o Most other accented chars like ç, á, é, í, ó, à, è, ì, ò all seem to appear correctly. these files (when listed explicitly) return an error as though the file didn't exist (logical since the real names are different, accented). I have tried specifying an iocharset (iso8859-1) smbmount parameter but nothing really changes. My kernel nls support is ISO-8859-1 by default (the default if I remember correctly) My dos charset (smb.conf) is 850 display and unix charsets are set to ISO8859-1 When I run smbclient -U leo //servername/d$ The ftp like command program displays all characters correctly. Does anyone have any suggestions as to how to correctly display accented from a Win2k served folder mounted on a linux filesystem? I have exhausted all possibilities I can think of. Thanks in advance, Leo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount problem
Does anyone have any suggestions as to how to correctly display accented from a Win2k served folder mounted on a linux filesystem? I have exhausted all possibilities I can think of. First off, ask the kernel boys, they maintain the mount-called subsystems. Second, perhaps look into CIFS instead of SMBFS as your mount type. I don't know if it will fix your problem specifically, but its the usual answer when somebody has a problem with mount -t smbfs -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount and session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or Session Setup are invalid.
Hi, I am also getting the same error. Did you figure out what was the cause for this error. Could you please let me know. Thank you, Ravi -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount problem
I wish to mount a Windows network share in Linux (Windows running WinXP) I can successfully connect to the Windows network share with smbclient: smbclient //andyson01/clientfiles -U victor%password But when I try to mount this share with the following: smbmount //andyson01/clientfiles /home/victor/client -o username=victor password=password I get the following error messages: (the directory client exists before trying the smbmount command) cli_negprot: SMB signing is mandatory and we have disabled it. 2172: protocol negotiation failed SMB connection failed I can use the smbmount for shared directories on another Windows 98 machine. I am new to Linux, and would appreciate any help. Victor Warner -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount across networks
Hi, I'm still having problem with smbmount across two different networks. My server has a few shares with the guest access enabled, and in the same network of the server, I can mount those shares in guest mode. Nevertheless, in another network I cannot mount the share in guest mode (I get a ERRNOACCESS), and I have to specify a username/password (even the guest one). I cannot understand why, anybody has an idea? I'm using samba 3.0.9. Thanks, Luca -- Luca Ferrari, [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Smbmount and permission denied
Hello, First of all, thank for your answer. Unfortunatelly, It do not work ... You speak only about a uuid and what about the password and the workgroup ? One additional thing: do the user exists on the Linux machine. In my point of view: no. What are you thinking about this ? Thanks for your help. François (Belgium) -Original Message- From: Tom Skeren [mailto:[EMAIL PROTECTED] Sent: mardi 18 janvier 2005 17:14 To: MATHIEU FRANCOIS-XAVIER Cc: '[EMAIL PROTECTED]' Subject: Re: [Samba] Smbmount and permission denied MATHIEU FRANCOIS-XAVIER wrote: Hello, Note that I found many place with similar problem, but I don't understand any solution. Can you help me ? I use Samba 3.0.10 on a Suse 8.2. On SuSE 9.2 I use mount -t smbfs -U=user //machine_name/share /local/directory. I think that's the right structure. Sorry don't use linux much. My goal is to mount a shared directory from a XP machine to a directory on my linux. * I have created a directory in order to mount the XP directory * a ls -l show me this directory * I mount the XP directory with a valid command : smbmount //be2a03xc/pmlist /home/team/monsysrv -o username=NT_user,password=NT_password,workgroup=BE001 * This command gives no error message and mount command shows me that all seems to be correct. * When I do a ls -l, I see no more this directory, but I can enter in it with cd * a ls -l of this directory gives me permission denied. * strange ? No ? If you have any tips or additional question in order to solve this very strange problem, do not hesitate to respond to me. Kind regards, François -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Smbmount and permission denied
Hello, Note that I found many place with similar problem, but I don't understand any solution. Can you help me ? I use Samba 3.0.10 on a Suse 8.2. My goal is to mount a shared directory from a XP machine to a directory on my linux. * I have created a directory in order to mount the XP directory * a ls -l show me this directory * I mount the XP directory with a valid command : smbmount //be2a03xc/pmlist /home/team/monsysrv -o username=NT_user,password=NT_password,workgroup=BE001 * This command gives no error message and mount command shows me that all seems to be correct. * When I do a ls -l, I see no more this directory, but I can enter in it with cd * a ls -l of this directory gives me permission denied. * strange ? No ? If you have any tips or additional question in order to solve this very strange problem, do not hesitate to respond to me. Kind regards, François -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Smbmount and permission denied
MATHIEU FRANCOIS-XAVIER wrote: Hello, Note that I found many place with similar problem, but I don't understand any solution. Can you help me ? I use Samba 3.0.10 on a Suse 8.2. On SuSE 9.2 I use mount -t smbfs -U=user //machine_name/share /local/directory. I think that's the right structure. Sorry don't use linux much. My goal is to mount a shared directory from a XP machine to a directory on my linux. * I have created a directory in order to mount the XP directory * a ls -l show me this directory * I mount the XP directory with a valid command : smbmount //be2a03xc/pmlist /home/team/monsysrv -o username=NT_user,password=NT_password,workgroup=BE001 * This command gives no error message and mount command shows me that all seems to be correct. * When I do a ls -l, I see no more this directory, but I can enter in it with cd * a ls -l of this directory gives me permission denied. * strange ? No ? If you have any tips or additional question in order to solve this very strange problem, do not hesitate to respond to me. Kind regards, François -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount performance stinks, smbclient is good
thanks for the suggestions. an interesting update: the network between the server (a PC in the basement) and the client (my laptop) uses 802.11b infrastructure. I found a knob on the linksys wireless router that could jack up the bandwidth. (why the default wasn't maxed out is a mystery to me). anywho, before turning the knob I got say ~40-50kByte for the smbmount and ~200-400kByte for the smbclient transfers. After I get ~400kByte for the smbmount and ~670kByte for the smbclient. cool. I still wonder why there is a noticeable difference between the two. 1. Make sure you've got a new(ish) kernel. Read the changelogs to see if you're missing anything in new versions. I'm using 2.6.7 (gentoo hacked) on both the server and the client. samba 3.0.10 is installed on both. Maybe the gentoo'y kernel is wonky. 2. Try using the cifs mount instead. Personally I've never tried it, but it is a common solution given 'round these parts for probmes with smbfs kernel operations. why oh why does the computer hate me so? i enabled CIFS support and rebuilt my kernel on the laptop but mount.cifs is a no go. e.g. $ mount -t cifs //asterix/media /mnt/media -o user=root,password=big_secret gives me mount error 5 = Input/output error Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) crud. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbmount performance stinks, smbclient is good
Hi, I use smbmount to mount a share from a linux smbd. Bandwidth for transferring a big file (via cp) is 1/5th that of when I do the equivalent using smbclient to transfer the file. Duh?! Any clues? Any pointers on how to debug the problem? Thanks! /Zac -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount performance stinks, smbclient is good
Bandwidth for transferring a big file (via cp) is 1/5th that of when I do the equivalent using smbclient to transfer the file. These (mount -t smbfs and smbclient) are completely different programs running. Using a mount is a kernel module and smbclient is the samba maintained program. 1. Make sure you've got a new(ish) kernel. Read the changelogs to see if you're missing anything in new versions. 2. Try using the cifs mount instead. Personally I've never tried it, but it is a common solution given 'round these parts for probmes with smbfs kernel operations. -- -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
