Updated SMBFS Now Available for OS3 and OS4

[Daedalus]

Version 1.102 of SMBFS has been released and is available on Sourceforge here. This version includes a number of fixes for long-standing bugs, and enables connection to Windows Vista and 7 shared folders. It's also reported to work with Windows 10 shares.

This is great update for me and means I no longer have to use FTP servers or a Linux box as a middle-man to transfer files between my Windows 7 machines and my Amigas.

Many thanks to Olaf Barthel for his hard work on this update, and to the MorphOS team for passing their code changes on for reintegration in this version.

[vulture]

It's not April 1st is it?

That's beyond awesome!

[gazj82]

It is, luckily I connect to a Linux samba server, but in the past I have tried to connect to a modern windows machine and failed. It's great to know it can now be done.

Just updated, all seems to be working fine

[Jope]

Wonderful! This is an indispensable tool.

Thanks for your continued efforts, Olaf, if you are reading this. :-D

[SkulleateR]

Using this for a long time, can´t wait to try out with my Win10 machine

Keep´em coming

[Locutus]

Thanks!

[nogginthenog]

Nice! Hopefully it fixes the bug with corrupt files sometimes (Win 10 related?)

[Sir_Lucas]

This is a really great news!!!

[demolition]

Very nice to get this updated - I will try it out some time.

[SnkBitten]

Works great on WinUAE and accessing my NAS box storage. I need to try it on my Amithlon system next. I like that you don't need to install the full smb services, just this app and it works well.

copied smbfs to c:, added my NAS ip and name to the hosts file under Amitcp:/db/ and created a script that executes run >NIL: smbfs with my required parameters and I have workbench icons pop up for both of my shared volumes.

[patrik]

Originally Posted by SnkBitten

I like that you don't need to install the full smb services, just this app and it works well.

This is a very logical behavior - smbfs is a smb/cifs client implementation, smbd and nmbd is a smb/cifs server implementation and they should not depend on each other being present on the same machine to be able to talk to their counterparts on other machines.

[Daedalus]

Originally Posted by nogginthenog

Nice! Hopefully it fixes the bug with corrupt files sometimes (Win 10 related?)

Yep, it should indeed. The corruption was also happening for me with Windows 7 shares, but it works fine now.

[clebin]

Originally Posted by Daedalus

Yep, it should indeed. The corruption was also happening for me with Windows 7 shares, but it works fine now.

This is superb news - I'll try it with OS X soon. Between Google Drive, Dropbox, Netsurf and this, the Amiga feels more connected than it has in years...

[nogginthenog]

Originally Posted by Daedalus

Yep, it should indeed. The corruption was also happening for me with Windows 7 shares, but it works fine now.

It definitely seems better. I'm not getting corruptions on lha / zip files.

However, I still have a problem. Trying to copy 1 particular lha returns:

Error in reading - packet request type unknown

But if I make a copy of the file in Windows it copies (and extracts) OK. Can't see any special security rights on this file.

Using a X-Surf-100 with MiamiDx. I can live with this!

Gonna do some more testing.

[nogginthenog]

I've just lha'd my entire boot partition to a Windows 10 SMB share. Worked fine and a 'lha t' reports everything is OK.

Yet again Olaf has done some amazing work! The guy needs medal!

[trixster]

I'm having trouble getting smbfs to connect to either my PC or NAS.

I've been happily using SMB-Handler and that works fine with both Windows 10 and Linux NAS shares. Assuming I can get smbfs to work correctly, is there any merit to using it over smb-handler?

[modrobert]

I tested smbfs-1.102-68k on my A1200 (details in sig), works fine against new/modern SMB servers.

However, still need smbfs-1.74-68k against my ancient samba server (V2.2.12). I tried using the 'NETBIOS' option in smbfs-1.102-68k and it fails anyway, keep getting "smbfs: Could not connect to server (61, Connection refused)".

[drluking]

hello,
I have a problem with SMBFS (1.102 version and 1.74 version); if I try to connect to an host OSX Macintosh 10.5.8 no problem (the mount It's OK!), if I try to connect to an host OSX Macintosh 10.11.6 or 10.10.5 I have always this error:

smbfs: Cannot connect to server (61, Connection refused).
smbfs: Could not connect to server (61, Connection refused).

I have also tried to disable SMB server signing in OSX https://support.apple.com/en-us/HT205926 (but nothing is changed ...)

Choose Apple menu > System Preferences, then click Sharing.
Clear the File Sharing checkbox, then close the Sharing pane.
In Terminal, use this command:
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server SigningRequired -bool FALSE
Choose Apple menu > System Preferences, then click Sharing.
Select the File Sharing checkbox, then close the Sharing pane.


the command used is this (perfectly woring in OSX 10.5.8!):

smbfs cache=500 volume=mac Workgroup=WORKGROUP User=admin Password=test Service=//macbookpro/data

HELP !
thanks for the support

[MagerValp]

@drluking: You can try switching the Mac's SMB server to SMB1 mode:

$ sudo scutil --prefs com.apple.smb.server.plist
Password: 
> get /
> d.add ProtocolVersionMap # 1
> set /
> commit 
> apply
> quit

To restore the default setting, use "d.remove ProtocolVersionMap"

Please note that there are security and performance implications of switching to SMB1, so I don't recommend using it except for testing.

[demolition]

Originally Posted by MagerValp

Please note that there are security and performance implications of switching to SMB1, so I don't recommend using it except for testing.

When you wrote SMB1, I immediately thought about that due to the whole WannaCry thing:
https://redmondmag.com/articles/2017...ows-smb-1.aspx