Share name not found error on FileBrowser client [SOLVED]

[Mosez]

[Moved from File Sharing section]

Could someone help me understand what exactly happens when for a share the option "Uses pool" is switched on?

The FileBrowser client I'm using on my iPad sees all shares and is able to access a share just fine, as long as I do not pool that share. If I do, FileBrowser give me the error "Could not connect to share: Share name not found" even though all shares are 'seen' by the client (pooled and not pooled). Mind you, my Win7 client browses the same shares just fine.

Thanks in advance for your concern.

[bigfoot65]

Did you check out the Shares Troubleshooter in the wiki?

http://wiki.amahi.org/index.php/Shares_troubleshooting

[Mosez]

Did you check out the Shares Troubleshooter in the wiki?

http://wiki.amahi.org/index.php/Shares_troubleshooting

I did. The problem is not so much that the share is not working at all - it works fine on my Windows clients. It's that the share isn't working on the FileBrowswer client, and *only* not when "Use Pool" is switched on.

I suspect the issue lies with the FileBrowser client. However, in order for me to explain my issue to the developers of the FileBrowser client, I'd like to understand what exactly happens on my Amahi HDA when I toggle "Use Pool" on and off for a particular share.

Thanks again.

[Mosez]

Alright, figured out what the problem was - so this one is for the knowledge base I guess.

1. First of all I was wrong - it turned out NONE of my clients where able to access the pooled shares. All non-pooled drives where fine. What threw me off was that iTunes automatically created a new library on a local disk when the share \\HDA\Music became inaccessible - without letting me know there were any issues.

2. The log was showing the error message:

Code: Select all

error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL

for all my pooled shares that I tried to access. I had manually updated Greyhole to the latest version, and was experiencing the rather well document issue where

Sometimes, the script included in the RPM can't create the Greyhole module for Samba where it should, and this will cause your Greyhole pooled shares to become unaccessible.

3. Per Guillaume Boudreau's (Mr. Greyhole) Greyhole updating Wiki: forcing the update once more with

Code: Select all

​rpm -Uvh http://www.greyhole.net/releases/rpm/`uname -i`/hda-greyhole-0.9.13-1.`uname -i`.rpm

​ did the trick. Much obliged.