SMB shares

[uwiep]

Hallo,

I have a problem with shared folders on an SMB server - at my office we have several shared folders on a single SMB volume, say "projects" , "graphics" , and "backup". I can connect to all three shares in Finder (and access them just fine), but whenever I try to access one of the shares in Forklift, Forklift always jumps to the first shared folder that I connected to. So for instance if I connected to "projects" first, clicking on "graphics" or "backup" in Forklift will jump me to the "projects" shared folder, and I can never access the other two shared folders in Forklift (so I have to go through Finder, which is a bit of a pain). Another user reported the same issue in the the blog, but I was wondering if there is a workaround or some kind of resolution.

thanks.

[csaba]

Hi,

We are aware of this bug, and are about to release an update which we hope will correct the problem.
If not, we will need some more thorough and direct help from you, and other users who've experiences such problems, for testing this out.

Please let us know if the problem is resolved after this upcoming update.

[uwiep]

Hello,

Thanks for the quick response! I'd be happy to report the results after the next update and help out further if needed.

[ono]

Also there are 2 other bugs:

1) When navigate SMB server, Finder shows mapped and all available shares, Forklift shows only mapped shares, why not all available as Finder?

2) Going up back from share we land in /Volumes, but shouldn't we land back in SMB server share list?

[uwiep]

Hello,

This problem unfortunately hasn't been resolved with the 1.5.2 update. I've tried disconnecting, reconnecting with the shares, restarting Forklift, restarting the computer, tried a different order of connecting to the shares, but Forklift still always jumps to the first share on an SMB volume. Should there be something else that I should try, or is there more information I can collect for you guys? I'm running OS X 10.5.2 on a 2ghz Core 2 Duo Macbook.

[csaba]

OK uwiep

So we'll have to keep working for this.
But, we will probably need your help in this, because we're unable to reproduce the problem here. Please post a bugreport on our Support page so we have your address - it will be easier to do this in email.
Mudi says it will be even better if you could send us an iChat or msn account.

[fromoze]

I have a problem with shared folders on an SMB server - at my office we have several shared folders on a single SMB volume, say "projects" , "graphics" , and "backup". I can connect to all three shares in Finder (and access them just fine), but whenever I try to access one of the shares in Forklift, Forklift always jumps to the first shared folder that I connected to. So for instance if I connected to "projects" first, clicking on "graphics" or "backup" in Forklift will jump me to the "projects" shared folder, and I can never access the other two shared folders in Forklift (so I have to go through Finder, which is a bit of a pain). Another user reported the same issue in the the blog, but I was wondering if there is a workaround or some kind of resolution.



So we'll have to keep working for this.
But, we will probably need your help in this, because we're unable to reproduce the problem here. Please post a bugreport on our Support page so we have your address - it will be easier to do this in email.
Mudi says it will be even better if you could send us an iChat or msn account.



Try to activate Leopard's Firewall. I've had the same problem until I disconnect it and I can reproduce it again when active :)

[csaba]

Fromoze,

We have tried playing with the Firewall, and what we experienced, is that the Firewall setting will affect the visibility of the shares, not whether they are mounted correctly.

Still, we could not reproduce uwiep's problem with the shared folders not being mounted properly. We would still be interested in some help with this, as we are unable to reproduce the problem here, on our local network.

[fromoze]

Still, we could not reproduce uwiep's problem with the shared folders not being mounted properly. We would still be interested in some help with this, as we are unable to reproduce the problem here, on our local network.

May be it's something about our networks... mine is a mixed one; 2 linux boxes and my macbook 2.1 connected by a Linksys wrtgs.

Can the problem affect only non-mac shared folders or only macbooks or only Linksys ??

[alekksa]

Hello,

This problem unfortunately hasn't been resolved with the 1.5.2 update. I've tried disconnecting, reconnecting with the shares, restarting Forklift, restarting the computer, tried a different order of connecting to the shares, but Forklift still always jumps to the first share on an SMB volume. Should there be something else that I should try, or is there more information I can collect for you guys? I'm running OS X 10.5.2 on a 2ghz Core 2 Duo Macbook.

The problem is not resolved with 1.5.2. I have same problem. I have 2 windows based computer, 2 Mac (tiger and leopard, Forklift is on Leopard computer) 1 linux computer and one FreeBSD computer. And there is also NAS box on the network. Forklift does not work with any of samba shares, no matter which share I click, Forklift always connect to the first mapped share.

I almoust bought Forklift (I am evaluating it at the moment) when I dicovered this bug. Then I came here and I see that this bug is already posted.

I am looking a replacement for Diskorder and I thought Forklift will do the job. But I work a lot on smb shares so Forklift is out of the question right now. Shame, because all other features are really good.

[ono]

Yeah it doesn't work at all as desired in 10.5.3 (neither was working in 10.5.2).
I believe it is possible to make it work as in Finder. Correct me if I'm wrong, but Finder is just a regular Mac application using regular Cocoa or Carbon API, so everything that's possible in Finder should be possible in other application.

I'm keeping my fingers crossed for making FL work with SMB shares and finally to see Cmd+K Samba option for share mapping and favorites....

[csaba]

Good news everyone :)

It seems that we have finally nailed this problem, at least we think we did. Bela's been working on this and testing it for the past month and he says it's now rocksteady.

We are preparing to make a release in the coming week, so we'll see.

As for the Cmd+K Samba, we'll promise we'll get it ready not for the next release, but the one after that.

[alekksa]

Good news everyone :)

It seems that we have finally nailed this problem, at least we think we did. Bela's been working on this and testing it for the past month and he says it's now rocksteady.

We are preparing to make a release in the coming week, so we'll see.

As for the Cmd+K Samba, we'll promise we'll get it ready not for the next release, but the one after that.

Any news about this "fixed" release? Please let us know.

[alekksa]

I am jumping off this ship. I can't no longer wait for any news about update. I will go with another file manager.

[tomkruk]

You say release in "the comming week".. Now its much later and not even a peep.
I'm really dissapointed because I use lots of windows shares, including accessing shares on VMWare Fusion all of which are visible in Finder.

I've been waiting quietly. Nothing. Too bad I am back to Finder.

[csaba]

Absolutely right here guys. We've left you without a fix for way too long.
We bow our heads and ask for your forgiveness.

What happened is that we wanted to include some components in the next release, but we fell way behind schedule with these.

I hope we'll be able to make it up to you guys by building a quick release that contains the fixes that are already good and tested, while we leave the other stuff for the release after that.

So keep an eye on our blog for a post on the 1.5.3 update, coming very soon.

see you later

[csaba]

OK everybody.

We've put out 1.5.3 yesterday, and it looks like it did fix the problems with shares, as bugreports have ceased to come in, and no one says otherwise.

Is this right? If not, please post your bug here.

[alekksa]

OK everybody.

We've put out 1.5.3 yesterday, and it looks like it did fix the problems with shares, as bugreports have ceased to come in, and no one says otherwise.

Is this right? If not, please post your bug here.

I thought I can give Forklift one more try. But sadly my trial period is over. So I can't give any feedback.

[csaba]

alekksa, write me an email through our support page, and I'll help you get another trial period.