New version of filesysbox for AROS

[salass00]

I created a mountlist file called ENNE in DOSdrivers with the suggested lines, using this URL


Startup = "smb://Paolone:mypassword()192.168.xxx.xxx/N$"


I don't get any error message when I try to mount ENNE, however there is no way to access the share. Any help?

The "()" should be an at sign ("@") (see the README in the archive). Annoyingly AROS archives and OS4Depot censors this symbol thinking that it is an e-mail address.

Error messages are written as serial debug output so you have to use sashimi or null-modem cable to capture them.

Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.

[AMIGASYSTEM]

Hi salass00, sorry, but just to better understand the terms used on your string ?

mypc= is it the name of PC-Windows or its IP ?

myuser= is the name of the user of the PC-Windows which "sharing" ?

myshare= is it a volume or folder that the PC-Windows shares ?


Question, SMB can work if AROS is connected to the LAN Network, via a LAN Network Share with the PC

[salass00]

Host can be an IPv4 IP address or any host name that can be resolved using the gethostbyname() function. If you can "ping" it using the ping command then it should work with smb2-handler as well.

The username and password should be ones that are recognized by the samba server that you are trying to connect to.

Share is the name of the samba share you want to access, which may or may not be the same as the name of the disk/directory being shared. There is also the possibility to specify a path after the share name (path separator here should be normal slash ("/") not backslash) to only mount a specific sub-directory.

[AMIGASYSTEM]

I get this error message, where do I go wrong ?

[smb2fs] smb2_connect_share failed. smb2_service failed with : Read from socket failed, errno:104. Closing socket.

[salass00]

Errno 104 is ECONNRESET (Connection reset by peer) according to <aros/posixc/errno.h>.

[AMIGASYSTEM]

How is it resolved ?

[salass00]

Googling a little on "ECONNRESET" it could be a sign of a bad network connection. Basically the socket connection was abruptly closed from the other end.

For testing smb2-handler on AROS I've used a 32-bit x86 AROS installation inside VirtualBox to connect to a samba share on the host machine (running Ubuntu 22.04 LTS). The only connection errors I've experienced are that occasionally it times out and I have to restart the samba server ("sudo service smbd restart") to get it working again. I'm assuming that this is because there is no dismount function in AROS so I can't make the file system do a proper disconnect from the samba share (instead I just do a warm or cold reboot when I need to test a new version of the handler).

[AMIGASYSTEM]

The Connection on my "Fiber" LAN works very well on AROS One x86, I have no problem surfing the Net, also all my PCs connected on the Net have no problem with sharing

Also I noticed that on AROS x86 the Ping works endlessly without stopping and giving the sent/received packets.

I wouldn't want me to do something wrong, could you please attach your example DOSDRiver SMB2 file, maybe others need it too, thanks

[paolone]

I created a mountlist file called ENNE in DOSdrivers with the suggested lines, using this URL


Startup = "smb://Paolone:mypassword()192.168.xxx.xxx/N$"


I don't get any error message when I try to mount ENNE, however there is no way to access the share. Any help?

The "()" should be an at sign ("@") (see the README in the archive). Annoyingly AROS archives and OS4Depot censors this symbol thinking that it is an e-mail address.

Error messages are written as serial debug output so you have to use sashimi or null-modem cable to capture them.

Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.

I forgot to say I have tried @ as well, but without luck.

[Amiwell]

maybe this string is well

Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
Startup = "smb://user:password@nameserver/share directory"

[paolone]

Ok, I finally understood why it didn't work for me. I am too much accustomed to Windows' standard volume shares (HOSTNAME/x$ where 'x' is the letter of a volume) and I assumed filesysbox would have supported them, as like as it does for explicit user-made shares. So the current experience I have is


MYHOSTNAME/D$, C$ or N$ are NOT working


while


MYHOSTNAME/SHARE  is working


althoug SHARE must be something that I explicitly decided to share with Windows' own commands. So, if I create a MYHOSTNAME/DISK_C share for drive C, it will work with filesysbox.


Any hope to see Windows's standard default shares supported as well?


Moreover:

Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.

I have added the line Activate = 1 to the Dosdriver file, but I still need to access the directory some way (either with CLI or placing the volume name in Magellan's apposite field) to have the device actually mounted. Maybe I should try with the icon tooltype?

[AMIGASYSTEM]

Well I succeeded, AROS One x86 connected to Windows share, it works !!!

The Share Icons automatically appeared on Wanderer !!!

[AMIGASYSTEM]

SMB2 also works well on OS3, tomorrow I will test with AROS 68k !

[Amiwell]

a friend of mine on another forum has solved the problem soon I will post the problem

[AMIGASYSTEM]

I have already solved it, you have seen the screenshots !

---- Italiano -----

Io ho già risolto, hai visto gli screenshot !