Pardon me if this question has been asked before, but I stumbled upon a very interesting issue recently, and was just curious why samba does what it does.

I have a couple of users connected to a samba file server in our office, and recently, one approached me about commas in filenames. I wouldn't know because I don't use commas in filenames.

Anyway, samba 2.x doesn't allow me to create files with commas in them. I can create and edit files files with such filenames via the console (vi), etc. IF I create a file with commas in the filename via the command line and then open the files up in windows via samba, I get strange behavior (app lockups, connection errors (on that file), etc).

This isn't a big deal (training), but I was just curious if anyone knew why samba does this, or if there is a way to turn it off.

Thanks

AFAIK windows doesn't accept commas in file names so I think it is a security message on the samba side.

But windows does allow commas in filenames.........at least 2000/XP does. Win 95/98 might be another story.

Security doesn't make sense to me. Perhaps rigid conformity to industry standards are to blame. Sometimes Microsoft likes to stretch things a bit (add their own "features").

I was hoping someone might know why exactly.

I'm not sure of their exact function. But in Windows comma's appear to be used as DLL and EXE entry points. e.g user32.exe,LockWorkstation

They are also used to identify icons in icon libraries. I'd imagain a file with comma's in its name would cause some Windows App's a fair bit of confusion.

All I know is that I have several users that use commas in their filenames all the time. They have for years. It has become commonplace for them. Yes, commas can seperate parameters passed to DLL's, but apparently they are used more than that. NT/2000/XP doesn't mind commas.

Just wanted to add to this message. Samba 3.0.2a allows commas in filenames. Must be a character set issue.

Samba 3 fixed the problem.