Hi all, I'm seeing messages like these: Mar 13 18:07:09 dropbear kernel: smb_trans2_request: result=-32, setting invalid Mar 13 18:07:09 dropbear kernel: smb_retry: new pid=18567, generation=9 in my syslog. Further investigation has revealed that they appear when I try to access a directory which has been mounted from an NT server using samba, and it hasn't been accessed for some time. The period of inactivity required to cause this has varied from half an hour to a couple of hours. If I have a directory mounted from a Solaris or Linux server (again using smbmount), it doesn't happen. I've used: 1. NT 4.0 SP3, Linux 2.2.11, Samba 2.0.5a 2. NT 4.0 SP5, Linux 2.2.11, Samba 2.0.5a 3. NT 4.0 SP5, Linux 2.2.14, Samba 2.0.5a 4. NT 4.0 SP5, Linux 2.2.14, Samba 2.0.6 With Samba 2.0.5a, the smbmount process would exit after two or three retries, and the only way to recover would be to unmount as root (smbumount couldn't unmount because the smbmount process had died). At least 2.0.6 fixes that, so it's no longer a serious problem. I'd still like to know why it's happening though. Anyone seen anything like this or know why it's happening? Cheers, John -- whois [EMAIL PROTECTED] -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
