samba - Mar 2001 - smb client problem

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 the file. 

If I edit the files contents from the linuxbox I can see it with ls (and can
copy it to other directories). Then if I change the filename of that same
file on the nt4-server my linuxbox still sees the old filename.. and cp/more
etc just writes "file not found" when I try to do anything with it.

The TCP-connections are up and running (one for each mount) and I don't see
any strange things on the NT4-server. If I run smbclient I see all new files
created on the server and it looks normal.

Dmesg writes these messages:
smb_retry: new pid=25233, generation=6 (which is normal .. right? )
smb_trans2_request: result=-32, setting invalid
smb_retry: new pid=10801, generation=6
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3

Does anyone have a clue of what this could be ?

Thanks alot for your help!

Martin Svensson
Server Operations Centre
DRIFTBOLAGET AB SCHEELEV?GEN 15 223 70 LUND SWEDEN
PHONE: +46 709-540 02 00  FAX: +46 46-540 02 50
DIRECT: +46 709-95 46 86
martin.svensson@driftbolaget.com http://www.driftbolaget.com

On Fri, 2 Mar 2001, Svensson, Martin wrote:
> 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).
Upgrade to 2.2.18, it should fix the dir caching problems (I hope).

> smb_retry: signal failed, error=-3
and it should help vs "signal failed, error=-3" too, which unlike the
other error messages is an actual error. Make sure you are running
smbmount from samba 2.0.7 as well.

/Urban