similar to: Samba 2.0.7pre4

Why do I keep getting these messages? (from /var/log/messages) I use RedHat 7.1 and have a coupple of shares on the machine on a bizzy samba network. Oct 10 04:03:50 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10 04:03:50 n243 kernel: smb_retry: successful, new pid=5506, generation=47 Oct 10 04:44:03 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10

Hi guys, I hope I've reached the correct mailinglist. I'm experiencing a problem with smbfs. You can mount shares, but after a while, the connection is broken and all sorts of strange stuff happens. I've got a share called /mnt/ntshare which remotely mounts an NT host: [arnow@foo /mnt]$ ls ls: ntshare: Input/output error cdrom/ floppy/ [arnow@foo /mnt]$ [arnow@foo /mnt]$ dmesg |

Greetings, About 2 months ago, we decided to backup our Oracle test servers via samba rather than nfs -- the backups were just taking too long using nfs. No problem mounting the remote file share to the server and the backup took about one-third of the time. Yep, worked good...and still continues to out perform nfs hands down. Problem is - I'm receiving errors on both of the test servers.

Found these messages in /var/log/dmesg on a Redhat 7.1 machine running Samba 2.2.2 accessing a Win 2000 share. Actually, there are a bunch of tasks accessing the same share, complete with file locking, etc. Any docs on what that error code means? ...Thanks, ...Kenneth smb_get_length: recv error = 113 smb_trans2_request: result=-113, setting invalid smb_file_write: syndex/csafe.log validation

Hi there. I'm having a very odd problem with samba. I have a Mandrake 7.2 linux distro, though I've compiled a 2.4.2 kernel for it (with samba support compiled in - not a module), and I've also compiled Samba 2.0.7. When I mount shares from my win98 machines, if I try to list a large directory or open a large file, the terminal freezes. I'm able to log in another, but if I

Hi! We're experiencing a really weird problem with our linux smb client. We map four directories to a NT4-share from our linux-box (2.2.12). The problem is that the mount goes through just fine with no complaints and I can see the files on that share, but, I can't see new files created with ls on the nt4-server on the linuxbox but if I run more <filename> I can see the contents of

Every morning at 2:02am, and 6:25am, I get the following two lines in my /var/log/messages: Nov 6 06:25:15 borgCube kernel: smb_trans2_request: result=-104, setting invalid Nov 6 06:25:16 borgCube kernel: smb_retry: successful, new pid=28929, generation=37 The pid always stays the same, and generation increases by 1 everytime it happens. Currently I got one share from a W2K computer mounted

My current smb.conf http://mdew.orcon.net.nz/samba/smb.conf , isnt showing up in windows b0xes (Win2k) I can however mount my drive from the linux router, and it shows this error (maybe unrelated/related to this..) mount /sharing/ryan smb_get_length: recv error = 5 smb_trans2_request: result=-5 setting invalid smb_retry: succesful, new pid=32382, generation=2 My drive is browsable from the

Hello everyone. I have two linux servers* that each have four directories mounted as SMBFS shares from a Windows 2000 Server. For the most part, this set-up is working great, however, there have been occasional hiccups. Every so often, one of the servers, LINUX-ONE, logs a couple of Samba-related errors. The following is an example: Jun 30 06:30:45 mx-two kernel: smb_trans2_request:

Hi, I'm using samba-2.0.6-19991110 on Redhat 6.1 in order to mount a NT-filesystem. The mount command is: smbmount //ISDN/CoTel /mnt/NT-Bank/ -o username=serv,password=serv,workgroup=WORK,uid=root,gid=users,ro everything works fine, except that after one or two days the mount disappears. A simple 'ls /mnt/NT-Bank/MCCWIN' results in 'Input/output error'. In

Hello, I am running Samba-2.2.0alpha-2 on a OpenLinux 2.3 (Caldera) system, and I was wondering if this error message is NORMAL behavior for a NT Server share mounted with the following command: //inet_server_1/C /mnt/server1 -o username=xxxxxxxx,password=xxxxxx,ip=x.x.x.2 here is what is in /var/log/messages: Mar 15 09:51:59 htmlodds kernel: smb_trans2_request: result=-32, setting invalid

After posting to samba-nt and samba-technical I was told that this was the place. Running 2.0.7-21 Feb 22 12:42:41 server1 kernel: smb_trans2_request: result=-32, setting invalid Feb 22 12:42:41 server1 kernel: smb_retry: sucessful, new pid=32561, generation=4 I have removed the system from the domain, erased the SID's, reset the computer account, rejoined the domain and still get this

Hi - My messages may not be reaching this list. Would someone at least confirm receipt of this message even if you have no suggestions/ comments re its content? I have sent several messages concerning mount.smbfs and I guess no one is using smbfs to mount a Windows machine -or- no one has encountered my problem. To recap the problem and give a solution: [problem] mount.smbfs is not working on

I have a number of RedHat 7.3 computers. Kernel 2.4.18-3. Samba version 2.2.3a, installed from RPM that came on the RedHat CD. All the computers share some directories, but I don't think this is the issue. They also mount some windows shares like this: //host/unc /mnt/host/unc smbfs username=admin,password=pwd,workgrou=support,uid=user,gid=user 0 0 Sometimes on access to these shares

Hi - [problem] mount.smbfs is not working on 3.0.0beta3; it has been working thru 3.0.0beta2. When I re-install 3.0.0beta2, it works again. [configuration] *Linux host <hanako> Linux version 2.4.20-4GB-athlon (root@Athlon.suse.de) (SuSE Linux 8.2)) #1 Fri Jul 11 20:16:51 UTC 2003 *samba-3.0.0beta3 complied from source, with configuration option '--with-smbmount'. (same

First off, I don't know if this is password caching revisited with a vengeance or what. It's very inconsistent for the amount of time the share will stay mounted. I *think* the following are the relevant messagess in the log: Jun 23 22:24:36 reliant kernel: smb_trans2_request: result=-32, setting invalid Jun 23 22:24:36 reliant kernel: smb_retry: caught signal And of course, I get the

I just had the unpleasant experience of crashing a production server _twice_ when trying to access a file share. The server is 64-bit Windows 2003 on an itanium3. My box is RedHat Linux 8.0 with Samba 3.0.0-2. Here's some messages from syslog: Mar 19 09:13:58 hedron automount[1037]: attempting to mount entry /dborg/POS Mar 19 09:13:58 hedron mount.smbfs[23153]: [2004/03/19 09:13:58, 0]

I keep seeing this in my logs: Jul 5 12:37:29 gateway kernel: smb_trans2_request: result=-32, setting invalid What have I screwed up? Also, any news on when the search stuff will be back up?

I don't know who this problem belongs to, samba or Linux, but it's a common one, judging by the responses in my INBOX to a previous post. Plus, it's a fairly serious one; many applications require smb shares to be mounted continuously and without interruption. It's been a recurring problem which seems to have been pushed off to the side as not important, even though it's a

Running NT 4.0 WS SP 5 and samba 2.0.5a on Linux, 2.2.12 kernel. Whenever I mount an NT share from Linux, it times out after an indeterminate period of time. This has been a continuing problem, the only workaround being to perform something requiring disk activity on the NT box, bypassing the cache (i.e., ls > /dev/null doesn't work, but df does). This must be done on a regular