search for: smb_lookup

Hi people,

...ports detected Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver. 1.2.1 Copyright (c) 2000 Intel Corporation e100 - Intel(R) 8255x-based Ethernet eth0: Mem:0xfe900000 IRQ:16 Speed:100 Mbps Dx:Full Hardware receive checksums enabled smb_trans2_request: result=-32, setting invalid smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find...

...after I've discovered the problem, it clears up on its own, and I see messages like these in the syslog: Jul 1 13:52:57 mx-two kernel: smb_get_length: recv error = 110 Jul 1 13:52:57 mx-two kernel: smb_trans2_request: result=-110, setting invalid Jul 1 13:52:57 mx-two kernel: smb_lookup: find archive/s failed, error=-5 Jul 1 13:52:57 mx-two kernel: smb_lookup: find archive/c failed, error=-5 Jul 1 13:52:57 mx-two kernel: smb_lookup: find archive/s failed, error=-5 Jul 1 13:52:57 mx-two kernel: smb_lookup: find archive/c failed, error=-5 Jul...

...PP/somevolume /mnt/smb-test. The operation appears succesful. Yet, when I ls -alFG in the /mnt directory /mnt/smb-test is not listed. If I ls without the -alFG flags I do see the smb-test folder. If I cd into the folder it works fine, but as soon as I type ls I get the following error; kernel: smb_lookup: find /// failed, error=-13 The mount command shows the volume as mounted. I am having very limited luck finding information for a error=-13. I am running Novell Open Enterprise Server without the Novell packages installed making it functionally equivalent to SuSE Linux Enterprise Server 9. I...

...mount: Input/output error total 2 drwxr-xr-x 3 aigfpdev aigfpdev 1024 Jul 14 08:00 . drwxrwxrwx 3 aigfpdev aigfpdev 1024 Jul 14 07:57 .. 3. Syslog reports the following errors Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find //Risk failed, error=-5 Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find //Risk failed, error=-5 Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find /...

...mount.smbfs: entering daemon mode for service \\dborg\POS, pid=23153 Mar 19 09:14:29 hedron kernel: SMB server not responding Mar 19 09:14:29 hedron kernel: smb_get_length: recv error = 5 Mar 19 09:14:29 hedron kernel: smb_trans2_request: result=-5, setting invalid Mar 19 09:15:29 hedron kernel: smb_lookup: find //Store_257 failed, error=-5 Mar 19 09:16:29 hedron kernel: smb_lookup: find //Store_257 failed, error=-5 Mar 19 09:16:39 hedron kernel: smb_retry: caught signal Mar 19 09:16:39 hedron kernel: smb_lookup: find //Store_261 failed, error=-5 Normally, I automount my windows shares. This has be...

...t error mv: cannot stat `/mnt/xfer/DIR/F0005161': Input/output error ls: /mnt/xfer/TMP/F0005161.tmp: Input/output error ..." The follow messages appeared on "/var/log/message": "... May 6 03:00:17 gprod kernel: smb_retry: no connection process May 6 03:00:17 gprod kernel: smb_lookup: find //DIR failed, error=-5 May 6 03:00:17 gprod kernel: smb_lookup: find //DIR failed, error=-5 May 6 03:00:17 gprod kernel: smb_lookup: find //TMP failed, error=-5 May 6 03:00:17 gprod kernel: smb_lookup: find //DIR failed, error=-5 May 6 03:00:17 gprod kernel: smb_lookup: find //TMP failed,...

When I mount a particular Windows 2000 share, I get this error hundreds of times in /var/log/messages. All I have to do is mount the share, I don't have to go into the directory or do anything with the share. I actually don't know for sure that it's only for this one share. Why does this happen? I'm on Fedora Core 2, using the samba-3.0.7-2.FC2 RPM that comes with it. Raul

...yesterday Detail Level of Output: 0 Logfiles for Host: inchgapp ################################################################=20 --------------------- Kernel Begin ------------------------=20 WARNING: Kernel Errors Present smb_get_length: recv error =3D 5...: 1Time(s) smb_lookup: find //i686 failed, error=3D-5...: 4Time(s) smb_lookup: find //libacl.so.1 failed, error=3D-5...: 1Time(s) smb_lookup: find //libtermcap.so.2 failed, error=3D-5...: 1Time(s) smb_lookup: find //mmx failed, error=3D-5...: 2Time(s) smb_lookup: find //tls failed, error=3D-5...: 8Time(...

...te RAID 10, Gigabit Ethernet). There is a Samba Server (2.2.0) on it and there is a mounted Share from an NT-PC (mount -t smbfs -o username=xxx,password=xxx //xxx/mount /home/mnt). In the file /var/log/messages I have the following error Messages : smb_trans2_request: result=-104, setting invalid smb_lookup: find //xxx failed, error=-104 smb_lookup: find //xxx failed, error=--5 # a few of them and there is a Problem to write on it. The Problems come and go, sometimes it's working and sometimes not. What can I do ? It's very important !! Thank you kind regards Sascha -------------- nex...

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

...Error Connection reset by peer Oct 17 11:02:00 x370 smbd[8747]: [2005/10/17 11:02:00, 0] lib/util_sock.c:send_smb(762) Oct 17 11:02:00 x370 smbd[8747]: Error writing 39 bytes to client. -1. (Connection reset by peer) The /var/log/messege on client shows: Oct 17 17:47:56 x206f kernel: smb_lookup: find //p0 failed, error=-5 Oct 17 17:48:26 x206f kernel: smb_add_request: request [e56b9c80, mid=121] timed out! Oct 17 17:48:26 x206f kernel: smb_lookup: find //p0 failed, error=-5 Oct 17 17:48:56 x206f kernel: smb_add_request: request [e56b9c80, mid=122] timed out! Oct 17 17:48:56 x206f ke...

...ca 7c c7 8b 1d c0 25 b5 f8 81 fb c0 25 b5 f8 74 79 8b 33 eb 0e <8b> 06 89 f3 81 fe c0 25 b5 f8 74 50 89 c6 8b 43 08 85 c0 75 eb Nov 8 18:02:42 poseidon syslogd 1.4.1: restart. ################################################################################ Oct 26 09:30:11 poseidon kernel: smb_lookup: find //fabnet failed, error=-5 Oct 26 09:30:11 poseidon kernel: smb_add_request: request [e1a5e280, mid=104] timed out! Oct 26 09:30:11 poseidon kernel: smb_lookup: find //fabnet failed, error=-5 Oct 26 09:30:11 poseidon kernel: smb_add_request: request [c5610280, mid=65] timed out! Oct 26 09:30:1...

...=192.168.1.2,ro,username=linux,password=XXXXXX //blitzwing/jimothy /blitzwing/write smbfs ip=192.168.1.2,rw,username=linux,password=XXXXXX Error lines from 'dmesg' on machine thats failing smb_add_request: request [c69f8ec0, mid=6] timed out! SMB connection re-established (-5) smb_lookup: find //Documents and Settings failed, error=-512 smb_add_request: request [c351be60, mid=13] timed out! smb_lookup: find //Documents and Settings failed, error=-5 smb_add_request: request [c3929ec0, mid=13] timed out! SMB connection re-established (-5) SMB connection re-established (-5) smb_add_re...

...than 3 months, by now I have almost 90 users, and the server seems to crash after around a week, does anyone know what this means, any help would be appreciated here are the log from the kernel Info May 25 19:00:00 unicorn kernel: SMB connection re-established (-5) May 25 19:00:00 unicorn kernel: smb_lookup: find //AMGA failed, error=-5 May 25 19:20:00 unicorn kernel: SMB connection re-established (-5) May 25 19:20:00 unicorn kernel: smb_lookup: find //AMGA failed, error=-5 May 25 19:40:00 unicorn kernel: SMB connection re-established (-5) May 25 20:25:00 unicorn kernel: SMB connection re-established...

...After waiting for a long (minutes and minutes depending on the quantity of files in the directory) it gets back. The /var/log/message shows the following: Nov 21 20:18:17 redqueen kernel: smb_add_request: request [d716fe60, mid=1497] timed out! ... (many times) Nov 21 21:17:14 redqueen kernel: smb_lookup: find mp3/Bush failed, error=-5 ... (for many files in the directory) The logs on the server do not show anything relevant. I've read that it may be cause of the "resolve host" method in the server. It is configured to use only "host" and the server has /etc/hosts config...

...ed, error=4294967291 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291 smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291 smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291 smb_lookup: find syndex/.csafe.log.swp failed, error=-5 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/csafe.log validation fai...

...ent oplocks! Mar 20 11:17:20 showa16 kernel: smb_get_length: Invalid NBT packet, code=31 Mar 20 11:17:20 showa16 kernel: smb_add_request: request [e9361dc0, mid=1916] timed out! Mar 20 11:17:50 showa16 kernel: smb_add_request: request [e9361ee0, mid=1917] timed out! Mar 20 11:17:50 showa16 kernel: smb_lookup: find 060711/Brother's.JPG failed, error=-5 Mar 20 11:18:07 showa16 kernel: smb_proc_readdir_long: error=-2, breaking Mar 20 11:18:36 showa16 kernel: smb_get_length: Invalid NBT packet, code=33 Mar 20 11:19:06 showa16 kernel: smb_add_request: request [e9361ee0, mid=28823] timed out! Mar 20 11:1...

...var/log/messages I get the following info: Mar 19 07:24:58 services kernel: smb_trans2_request: result=-32, setting invalid Mar 19 07:24:58 services kernel: smb_retry: new pid=1059, generation=8 Mar 19 07:30:01 services kernel: smb_retry: signal failed, error=-3 Mar 19 07:30:01 services kernel: smb_lookup: find //MCCWIN failed, error=-5 any hint is welcome. thanks Edmund -- Edmund Mergl mailto:E.Mergl@bawue.de http://www.edmund-mergl.de

...is registered in the ring buffer as follows: a) successful reconnect negotiation: smb_trans2_request: result=-32, setting invalid smb_retry: new pid=24456, generation=3 smb_trans2_request: result=-32, setting invalid smb_retry: new pid=24456, generation=4 b) unsuccessful reconnect negotiation: smb_lookup: find //linux failed, error=-5 smb_retry: caught signal smb_retry: signal failed, error=-3 I am using Linux, kernel 2.2.15pre17, glibc 2.1. I have tried other kernel versions to remedy this problem without success. There was a topic in comp.protocols.smb, "disappearing shares" problem...