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] client/smbmount.c:send_fs_socket(405) Mar 19 09:13:59 hedron mount.smbfs[23153]: 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 been working actually, for about 3 months, without a problem. Call it a testament to the reliability of 64-bit Win2003 that trying to do a file listing with Samba blue-screens the server. The first time I thought it must just be a coincidence, but after a reboot, it did it again! They have to constantly patch the window's boxes here for security problems of course; this could be an early warning that M$ has changed something to be incompatible with Samba. Kyle -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba