I am experiencing two network issues that I believe are Samba related, but I am unsure. Because I use a multi-boot environment I use Samba regardless of the operating system. I do not use NFS and at this stage, I do not know how. I'm using Slackware 11.0, 2.4.33.3 kernel, and Samba 3.0.23c.

1. When I browse the /opt/kde/share/icons directory of another box, the local box seems unable to distinguish between the Locolor and locolor directories. Yes, the directories are spelled the same, but the casing is different. When trying to browse locolor (lower case) I always see the contents of Locolor (upper case). When viewing those same directories locally there is no confusion. The problem is not X/KDE related, because I experience the same problem from the command line, from within Midnight Commander, etc. I configured Samba to be case aware, but the problem persists.

2. When I view directories on a Windows box, the directory sizes are displayed as 4096 bytes in size. I realize this is not the actual directory size but is the block or inode size, or something like that. However, when I browse a 'nix directory tree of another box, the directory sizes are all shown as zero. The directories all display as 4096 bytes when viewed locally. Samba unix extensions are enabled (by default) and I do not know what other parameters to test or what else to troubleshoot.

Both problems also appear in my Slackware 10.2 partitions, which uses the 2.4.31 kernel and Samba 3.0.20.

Any ideas or help is appreciated.

Thanks again.

I know you say you configured case in samba, but since you didn't post exactly which parameters you configures, here's the way I think they should be configured.

You should have the following in smb.conf

NOTE: Also make sure you don't have parameters listed multiple times. Sometimes parameters can be listed globally, and also specific to a share (in which case it overrides the global setting).

Then restart samba and try again.

If that doesn't work, then I would rename the directory that starts with a capital, restart samba, and see if then you are able to access the lowercase directory. If not, then samba just isn't seeing it and you can be sure it's not a case-sensitivity issue. If after you move the Uppercase dir, you can now access the lowercase dir, then it sounds like a samba case-sensitivity issue and we can keep pursuing it as such.

let us know

Cheers

Checked.

Checked.

I did this and I can browse the affected directories with no problems. Restore the original names and something gets confused.

I performed the same test from a Windows client. Windows is infamous for not distinguishing between upper and lower case, but in Windows my Explorer saw two different directories. However, like from within Slackware, Explorer could not correctly display the file contents of both directories.

On a whim I temporarily disabled unix extensions and the problem remained.

I enabled vsftpd on one box. Through FTP I had no problem distinguishing between uppercase Locolor and lowercase locolor. I accessed the FTP server through both Slackware and Windows.

So again Samba seems to be the focal point. I am inclined to say only on the Samba server side and not related to smbmount because the problem exists with a Windows client too. However, I still do not know if this is a case sensitivity issue or something else. Could this be a charset problem? Or simply a genuine bug in Samba?

I don't have NFS installed and don't really want to spend time learning the basics of NFS. Further, I doubt NFS would prove anything because the FTP test correctly displayed the directories. The common point seems to be the Samba server.

Any additional help is appreciated!