|
I have an odd Samba problem I hope someone has
seen. I have a SS20 with 2 network cards running as a NAT firewall for an
isolated subnet. Suse 7.1, kernel 2.2, Samba 2.0.9
The SS20 has 2 shares mounted to /export/jeff and
/export/chris (using SMBFS) from two Windows 2000 workstations on the 'outside'
network. This makes the two Windows 2000 workstations' entire hard drives
visible within those two directories. The two Windows 2000 machines have a
specific user login created on them for the purpose of this share and
permissions.
I then use Samba to share those 2 directories to
the 'inside' network via the names "jeff" and "chris". I'm using Samba in
USER security mode and also have 'outside' HP printers shared via Samba printer
shares. It all works beautifully (and surprisingly fast) immediately after the
system boots. The printers work without any problems (once I got the Cups
drivers all figured out right!)
Problem: Within a day after starting the system,
the 2 mounted network directories become inaccessible. Even when logged
into the SS20, you cannot navigate to those subdirectories (/export/jeff or
/export/chris). You get a file system I/O error of some sort. The security
logs on the Windows 2000 machines show nothing wrong. The Samba logs just show
an I/O error when trying to read those directories via the Samba shares.
Even doing an ' ls /export ' shows the other directories but gives error when it
gets to those two mounted subdirectories.
I suspect the problem is within the SMBFS mounts
themselves. But how to debug those mounts? They work for at least
the first couple hours, then stop working, even from Unix prompt. I've
heard that Windows 2000 shares timeout after ??? minutes/hours. Is this
true? Any way around that?
|
