SMB limitation (bug)???
Yesterday I was attempting to connect to a share on my office's network (Windows network) and my Mac could not *see* 1 of the 4 shares that were available off of a particular server. After some messing around I determined that the problem was a *space* that was in the share name (i.e. "shared folder"). Because of that space, I couldn't see it or mount it. As soon as the space was removed, I could now *see* it.
So my questions are:
Is this issue a limitation of SMB, or is it a bug in the implementation in OS X 10.2.5?
Regardless of the answer above, does anyone expect that this will be corrected in the future?
So my questions are:
Is this issue a limitation of SMB, or is it a bug in the implementation in OS X 10.2.5?
Regardless of the answer above, does anyone expect that this will be corrected in the future?
Comments
"5. You cannot type spaces as part of the share name when connecting. In place of any space in the share name, type: %20"
However, it doesn't state anywhere whether or not you should be able to *see* the share prior to connecting to it. For instance, if I do "smb://someserver" I then log in and get a list of potential shares that are available. The ones with spaces don't show up, and this FAQ doesn't discuss that.
Thought this was interesting:
"6. You cannot connect to a share with a name that contains a hyphen. Resolve the issue by giving the share a name that does not contain a hyphen."
And the following finally explains why I had one of my few kernel panics (I didn't put 2 and 2 together myself, granted I only did this once):
"7. Connecting to (mounting) two or more SMB volumes simultaneously may cause a kernel panic. Drag one volume to the Trash to eject it before connecting to another."
I'd still like to know if the ability to *see* share names that have spaces in them is simply a limitation of SMB (that could be improved) or a bug (which should be fixed). If anyone has any knowledge, I'd appreciate it.
Thanks!