Is there a bug in Tiger's smbclient?

[Sunnz]

I just have set-up my samba server today... and I wanted to connect to it from my MacBook since I thought it would be the easiest thing to do... but it give me "Cannot complete operation" Error -50...

I searched on google and people had to use an old version of smb on their Mac or something... is there a bug in smbclient on Tiger or something?

This is making it really confusing and extremely complicated as I have no ideas which end has the problem: did I set-up samba properly on the Linux server or is it the Mac? Or is it both?

 

[nixgeek]

I've done some research on this when I experienced the same problem. It might have something to do with either a Windows 2003 server or a *nix Samba server using encrypted passwords for the samba usernames. From what I've been reading, it seems that (at least from the threads I found) that 10.3.9 didn't support encrypted passwords over Samba and it looks as though the same goes for Tiger (as I got the same error when accessing a Windows 2003 server). At this point if you're experiencing those errors and you know that everything should be configured properly, then you might want to disable password encryption within Samba or use something like DAVE or ADmit Mac from Thursby Software.

EDIT:

After doing a google search, I came across this from Apple. It seems that I might have been misinformed, although the problems I experienced were what I mentioned above (and I found said answers mentioned above from the MacinTouch Page that was listed in Google, but for some reason I can't find now ). It looks like you might have to enable encrypted passwords on your Samba box (if you're using Tiger).

 

[Sunnz]

Under further investigation, I didn't have samba server set-up properly on the Linux machine; now all my Linux and Mac machines works together like a charm! Thanks anyway!!!

BTW, is Samba a good solution for network drives if you have only Mac and Linux machines in your LAN?