SMBFS now working with Windows 7 (?)

Workgroup is the name of the PC and in service I've typed "service=//name_of_pc/d" and D is the partition that I've shared in Windows.

My username is the e-mail address to hotmail/live and the same regarding password.

@Raziel Ah you found the issue, sweet! Time for some relaxing gaming then :)

@hotrod

Yeah, thanks for the hint

It's dog slow on writing to the windows share though.
Copied a music album of roughly 55 MB

Takes 35 seconds to copy to a router based NAS (writing)
Takes 25 seconds to copy it back to ram: (reading)

On the PC it's far worse

Takes 14 minutes 33 seconds to copy to the windows share (writing)
Takes 1 minute 53 seconds to copy it back to ram: (reading)

The data is fine though, can play it back perfectly from the windows and amiga side

@Raziel

glad you've figured it out! I know it's fairly simple to work it out manually, but as I had a similar problem to yours, sambamatic really came through for me and did it right automatically until I finally fixed it in my script as well by correcting some typo (iirc). Yes, it's slow to write right now, but Olaf is working on it and he has already found the culprit.

Can't get it working here, trying to connect to a Windows 10 system. It times out after about a minute. (60, Operation timed out). I can't use an IP address in place of the computer name either.

Edit: If I go into the Hosts tab in SYS:Prefs/Internet, and set a host for it, then it gets further but says "(5, Input/output error)". If I put in a wrong username or password, it says "(13, Permission denied)".

Edit2: I solved it. The host I added in the internet prefs has to match the PC name.

@MickJT Quote:
(edit) Odd, I didn't need to do that. I was able to just use the NetBIOS "full computer name".

@ChrisH

Are you using the NETBIOS switch?

I previously set up a host called "test" that resolved to the PC's IP. Until I renamed it to the PC's full computer name, it had an Input/Output error when connecting.

It looks like some people don't have to set up any hosts at all though, but if I don't do that I get a timeout after 60 secs when trying to connect, whether I use the NETBIOS switch or not.

@MickJT Quote:
No. Sorry for the confusion, by mentioning NETBIOS (although I believe what I said is technically true for historical reasons).

Maybe the PC's "SMB host name" needs to be short to work with SMBFS? Mine is 11 characters long, and the old (Windows) NETBIOS limit is apparently 15 characters.

Mine is 15 characters long, with some random characters that Win 10 added. I might change it later and see what happens.

Hi, trying to use latest smbfs V1.102 with my external networked HDD (WD NAS) I got this error:

#samba:bin/SMBFS workgroup=GRUPO user=*** password=*** service=//WDRED/PUBLIC DEVICE=SMBFS0: VOLUME=WDRED TRANSLATE=L:FileSystem_Trans/INTL.crossdos
SMBFS: Cannot connect to server (61, Connection refused).
SMBFS: Could not connect to server (61, Connection refused).

Using "old" smbfs 1v1.74 no problems:
#samba:bin/smbfs174 workgroup=GRUPO user=*** password=*** service=//WDRED/PUBLIC DEVICE=SMBFS0: VOLUME=WDRED TRANSLATE=L:FileSystem_Trans/INTL.crossdos
Connected '//WDRED/PUBLIC' to 'WDRED:'; "Break 2" or [Ctrl-C] to stop...


Any log I can generate/see and find what I'm doing wrong with latest smbfs?

TIA

@jabirulo
From a quick glance at the manual, you need to use the DEBUG option with a value greater than 0 (the higher the value the more verbose it is). This gets output to OS4's debug buffer, so before running SMBFS you will want to clear the debug buffer:

DumpDebugBuffer CLEAR

And then after using SMBFS you can see what is in the debug buffer:

DumpDebugBuffer

@jabirulo

You might want to try the NETBIOS switch on your samba exec line.

from the readme:

NETBIOS/S

smbfs versions prior to 1.76 (10.12.2012) would use the "SMB over
NetBIOS"" data transport method which was deprecated by 2006 as
part of "Windows Vista". smbfs now uses "SMB over TCP" transport
by default. This may cause problems with older file servers. When
in doubt, try again with the NETBIOS switch.

Tried the DEBUG option but dumpdebugbuffer doesn't show anything about smbfs (do I need kernel.debug loaded too???)

NETBIOS option/switch tried too and get error on loading/launching smbfs V1.102:
#samba:bin/SMBFS workgroup=GRUPO user=*** password=*** service=//WDRED/PUBLIC DEVICE=SMBFS0: VOLUME=WDRED TRANSLATE=L:FileSystem_Trans/INTL.crossdos NETBIOS
SMBFS: Cannot connect to server (5, Input/output error).
SMBFS: Could not connect to server (5, Input/output error).

(BTW although error is different [5 vs 61] with/without NETBIOS switch)

Seems I have to stick with smbfs V1.74 with my old WD-NAS THX @all for helping

@jabirulo

Drop the TRANSLATE switch and add UTF8 switch.

Also, iirc smbfs is much more case-aware than before.
e.g. my pendrive is called "MyPenDrive" and i have to exactly give that to the SERVICE switch to make it work, otherwise it won't see it.

I know that the old version sometimes also struggled with wrong cases in names, but the updated one now seems to rely on the right case.
SERVICE=//MyPenDrive/Share/

Are all your NAS dirs upper-case?

There are two switches you could try aswell, CHANGECASE and CASE=CASESENSITIVE (no description in the readme for now)

@jabirulo Quote:
No, kernel.debug is for debugging OS4 itself .

I don't understand why the debug buffer is empty after using SMBFS, as Olaf's docs seem to indicate that is where debug stuff should go. Did you set try setting the DEBUG option to a high value, e.g. DEBUG=99 ?

Tried with V1.102 CASE,CHANGECASE,DEBUG=99 to no avail.
So it must be my NAS, maybe is too "old" for such new smbfs version

BTW my WD-NAS is 'western-digital-my-book-world-edition-blue-rings'
http://support.wdc.com/product.aspx?ID=106&lang=en

@ChrisH
Quote:
It could be because of a problem I reported in the Hyperion forums back in Oct 2013 (Debug output bug). For years the debug output went to the memory buffer by default. An OS4 update in late 2013 changed how it worked. With the default CFE/UBOOT settings, the debug output goes to the memory buffer when you first turn on the computer or perform a hard reset. After you perform a warm reboot the debug output no longer goes to the memory buffer and "dumpdebugbuffer" becomes useless. You can test this for yourself by compiling a small command to send debug output from a shell command line. I wrote such a command that I named "Debug" and entering 'Debug "testing debug output" ' will send the quoted text to to debug output.

After a warm reboot, enter: ' KDebug "console memory" ' and the debug output will once again go to the memory buffer and can be displayed with 'dumpdebugbuffer'.