similar to: Samba-3.0.2a and pathwork server smbmount problem

I am trying to connect with smbmount to a VAX/VMS system running, I believe, PathWorks. Using smbclient: $ smbclient '\\cowboy\hopkins' -UHOPKINS -Icowboy Added interface ip=199.187.33.84 bcast=199.187.33.255 nmask=255.255.255.0 Server time is Tue Jun 2 14:45:26 1998 Timezone is UTC-0.0 Password: security=user smb: \> ls AWHSTUFF.RS 31750 Thu May 28

[This seems like it should be a FAQ, but I searched for quite some time without finding anything.] Mounting a samba share using smbmount under linux leads to problems when dealing with filenames that differ in case only. These problems do not affect WinXP mounting the same share, so it looks like a client issue. The server is running Samba 3.0.1 on linux, kernel 2.4.20. The relevant part of

Mark Hessling posted about this problem earlier but I (and he) have not seen any reply to his original post. I was running Samba 3.0.0 on a Redhat 7.3 server for quite a while and then recently upgraded to RHEL 3.0 and Samba 3.0.9 (3.0.10 most recently). Before the upgrade, I was able to, from the Samba server, mount shares from an XP box. After the upgrade, the mount succeeds (it shows up the

Hello. I have a samba server setup with 3.0.2a-r1. It was working just fine, then suddenly, I cannot connect to any of my shares on my server with smbmount. Everytime I try to connect, I get this error: session setup failed: ERRDOS - 2215 I do something like this: smbmount //myserver/share /mnt/misc -o username=myself,workgroup=myworkgroup The password prompt comes up, I put it in, it hangs

Hi, I use samba on Linux 2.6 and 2G over size file sharing. It seems smbmount '-o lfs' need to use with large file. but default man page doesn't say this option. I want to edit smbmount.8.xml for lfs and unicode option. I believe using mount.cifs is right way on latest Linux. But one of the implementation smb_clients tools take this lazy option. Is it right way to change of man page

I have cross-compiled smbmount(smbmnt, smbclient) using samba-3.0.24.tar.gz, then ported them to an ARM Arch machine whose /etc directory is read only. The smbmount command always results in errors """Can't get /etc/mtab~ lock filesmbmnt failed: 1""" Someone says that If we rebuild samba with the smbmount-nomtab.patch and smbmount-mtab-flags.patch, it would work

Hello, I tried to compile Samba-2.0.5b with smbmount after setting the configure-option "--with-smbmount". On systems (SuSE 5.0 and SuSE 5.3) running Linux kernel 2.0.35 and 2.0.37 I didn't have success: Compiling client/smbmount.c In file included from /usr/include/linux/smb_fs.h:11, from client/smbmount.c:28: /usr/include/linux/smb.h:47: warning: `PVAL'

On Wed, 2 Aug 2000, Bojana Bjeljac wrote: (questions on use and bug reports are more appropriate in samba@samba.org, not on samba-technical. If you subscribed to samba-technical you may want to subscribe to samba@samba.org instead/also) > I have Samba 2.0.7 ( configured with "--with-smbwrapper" and "-smbmount" > options ), running on RedHat 6.0 and I mount Win2000

Iztok Polanic <iztok@hakl-hakl.si> carved some runes like this: > > 1. I have just installed samba on my computer. It works great and > > I can mount all Windows computers, except NT. When I try > > "smbmount //192.168.1.4/C /mnt/test" I get this error: > > > > Password: > > smb_get_length: Invalid NBT packet > >

Hi, Iam using Red hat linux 6.1 with samba version 2.0.7 .I had compiled and used it,and also used the patch given for smbmount.c by Urban.But Strangely the smbmount version is still version 2.0.5a.Is this the correct version for smbmount since i thought when i upgraded samba from 2.0.5a to 2.0.7 smbmount would also be upgraded.Because iam still facing some problems in using smbmount.If iam

Hello, I have found a solution on an other news group : uk.comp.os.linux There is a set of messages with the subject "Ordinary user to mount SAMBA share" You can read the content of that uk.comp.os.linux group through the web, the URL is http://x35.deja.com In one of the message the author wrote "After, further test. I find smbmount, unlike mount, requires the user owns the

I have built, installed, and run 2.0.6 successfully without smbmount, but want to do it with this time. I know that it's not part of samba, but am hoping someone can tell me if I'm making a simple mistake. It's possible that it's not even samba related. I'm a novice at this and have not gotten very good at figuring out what's wrong when something doesn't build

RH6.0. I downloaded: samba-2.0.4b-19990527.src.rpm Follwing the instrucions in README.smbmount, I edited samba2.spec to add 1) --with-smbmount to configure 2) the smbmount related files and man pages to the install and files sections. rpm -ba samba2.spec stops with: ..... Compiling smbd/ssl.c with -fpic Linking shared library bin/smbwrapper.so Compiling client/smbmount.c client/smbmount.c: In

For long time I used to smbmount my windows-xp share from my SuSE-Linux machine with smbmount from samba 2.2.12. Now I changed to debian-linux with samba 3.0.13. The smbmount-cmd: ' smbmount //winxp/share /unix-dir -o username=user,password=xxx,ro' returns no error. with 'mount' I see the mounted win-share. But when I try a 'ls /unixdir' I get a 'Permission

I'm trying to periodically mount an XP share on my linux box, and I've noticed that smbmount doesn't return a value so I can't test for success in my shell script: #!/bin/bash smbmount //NonsenseShare /bad/mnt/point || echo "error with smbmount" In this case smbmount silently fails. I searched the archives and found a couple of messages about smbmount demonizing

I use samba in a very limited application to mount smb shares using smbmount. I have a simple script I use that mounts several shares to a variety of mount points as a specific user on my system. The script passes username, password, share, mount point, domain information to each call to smbmount. This script worked perfectly under redhat 8.0 but since upgrading to redhat 9 I have had some

Hi I have two different distributions running, RedHat 6.0 and Slackware 7.0. Both machines are running Samba 2.05a. When I try the smbmount command on the RedHat machine, it has no problem mounting the smb service. RedHat 6.0: works: smbmount //win95machine/c /mnt/c failed: smbmount "\\win95\c" -c `mount /mnt/c -u 123 -g 456` Slacware 7.0: failed: smbmount //win95machine/c /mnt/c

Hello, I'm looking for some (user & technical) feedback on a change I'm considering on how mount and smbmount works together. The current way mounts are done are: mount -t smbfs ... => smbmount ... => smbmnt Possibly without the mount step. smbmount stays as a daemon and reconnects when asked (unless it crashes). Problems: - Some mount options should affect if the mount

Hello-- A quick question, to see if anyone could help me out. I have a home network with two nodes, my laptop and my girlfriend's. I have Debian sarge with kernel 2.6.6 on my laptop while on my girlfriend's machine is the Latin American Spanish version of Windows ME. I am trying to use smbmount to allow me to mount her machine's Windows file shares. I have set up the shares on her

Hi, I am wondering what the right way is to have smbmount negotiate a block size value of more than 4kB with the Samba server. I cannot seem to let smbmount understand the value I want it to use. I assumed first it gets this from smb.conf, and by adding DEBUG() info to the code and printing c->max_xmit, that's what it is using in smbmount.c. I also tried influencing the number using