I have been building raspberry pie based projects for some time using
the official OS from their website. Last September the OS was called
"buster" and you could edit /etc/samaba/smb.conf and add...
client min protocol=NT1
ntlm auth=yes
This enabled SMB1 so that Lanman98 could connect.
I've tried that today with "bullseye" the latest OS and that config
no longer works. However, my W10 PC connects no problem. It looks to
me as though the doors are now closed on SMB1 and Lanman98.
Anyone got any ideas suggestions, google doesn't mention this
specific issue.
Bob Latham <bob@sick-of-spam.invalid> wrote:
I have been building raspberry pie based projects for some time
using the official OS from their website. Last September the OS
was called "buster" and you could edit /etc/samaba/smb.conf and
add...
client min protocol=NT1 ntlm auth=yes
This enabled SMB1 so that Lanman98 could connect.
I've tried that today with "bullseye" the latest OS and that
config no longer works. However, my W10 PC connects no problem.
It looks to me as though the doors are now closed on SMB1 and
Lanman98.
Anyone got any ideas suggestions, google doesn't mention this
specific issue.
What version of Samba are you running on the Pi?
I had a skim through the release notes of various major releases of
Samba (I didn't go through all the point releases). The only thing
I note, from 4.13.0, is deprecation of ntlm authentication:
SMBv1 only protocol options deprecated
--------------------------------------
A number of smb.conf parameters for less-secure authentication
methods which are only possible over SMBv1 are deprecated in this
release.
REMOVED FEATURES
================
smb.conf changes
================
Parameter Name Description Default
-------------- ----------- -------
ldap ssl ads Removed
smb2 disable lock sequence checking Added No
smb2 disable oplock break retry Added No
domain logons Deprecated no
raw NTLMv2 auth Deprecated no
client plaintext auth Deprecated no
client NTLMv2 auth Deprecated yes
client lanman auth Deprecated no
client use spnego Deprecated yes
server require schannel:COMPUTER Added
but 'deprecated' shouldn't mean 'removed'.
Also, on my travels, I saw a note that Windows disables SMB1 if it
hasn't been used for 30 days. Which might explain why people have
problems with LanManFS/98 randomly stopping working, depending on
when they last used it.
Theo
In article <ABe*a4SEy@news.chiark.greenend.org.uk>,
Theo <theom+news@chiark.greenend.org.uk> wrote:
Bob Latham <bob@sick-of-spam.invalid> wrote:
What version of Samba are you running on the Pi?
I've never attempted to use a different version to the one that gets installed for the OS you're running, is that even possible?
At the moment I've been trying to find the most recent OS that still
allows SMB1 with the added code mentioned before. The last I've found
is version 4.9.5-Debian which is the default for "buster 2021-12-02"
OS. That is still available for download at the moment.
Could I install SAMBA 4.9.5 on the later bullseye OS?
How might I go about that?
client plaintext auth Deprecated no
client NTLMv2 auth Deprecated yes
client lanman auth Deprecated no
client use spnego Deprecated yes
but 'deprecated' shouldn't mean 'removed'.
And yet it doesn't function, how might I change that, is it possible
to change that??
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <ABe*a4SEy@news.chiark.greenend.org.uk>,
Theo <theom+news@chiark.greenend.org.uk> wrote:
Bob Latham <bob@sick-of-spam.invalid> wrote:
What version of Samba are you running on the Pi?
I've never attempted to use a different version to the one that
gets installed for the OS you're running, is that even possible?
Possibly, but even if it wasn't, I don't have your system in front
of me - 'the one in bullseye' doesn't help if I don't know what
that is.
The one in *Debian* is 2:4.13.13+dfsg-1~deb11u2 (ie
4.13.13 with their tweaks)
https://packages.debian.org/bullseye/samba but I don't know if the
Pi people have changed things (I don't know of a packages.raspios
site).
I'd use sudo dpkg --list | grep samba to tell you versions of all
the packages with 'samba' in the name.
At the moment I've been trying to find the most recent OS that
still allows SMB1 with the added code mentioned before. The last
I've found is version 4.9.5-Debian which is the default for
"buster 2021-12-02" OS. That is still available for download at
the moment.
Could I install SAMBA 4.9.5 on the later bullseye OS? How might I
go about that?
Yes. Assuming you were on Debian (and this might still work for
PiOS, since they're related), go here: https://packages.debian.org/buster/samba and you can download the
'armhf' package for Samba.
Then you can do:
sudo dpkg --install samba_4.9.5+dfsg-5+deb10u2_armhf.deb
It may well complain about missing dependencies, in which case go
back to the Samba page, find what it needs, and download those .deb
files.
*Beware* that it's possible to get your system in a mess if you
install packages this way that conflict with others that the
packaging system can't resolve. I'd take a backup of your system
before trying this.
but 'deprecated' shouldn't mean 'removed'.
And yet it doesn't function, how might I change that, is it
possible to change that??
Have you confirmed that it's NTLM at fault, rather than something
else?
I don't think we know what's causing it not to work, just
that it doesn't.
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <ABe*a4SEy@news.chiark.greenend.org.uk>,
Theo <theom+news@chiark.greenend.org.uk> wrote:
Bob Latham <bob@sick-of-spam.invalid> wrote:
What version of Samba are you running on the Pi?
I've never attempted to use a different version to the one that
gets installed for the OS you're running, is that even possible?
Possibly, but even if it wasn't, I don't have your system in front
of me - 'the one in bullseye' doesn't help if I don't know what
that is. The one in *Debian* is 2:4.13.13+dfsg-1~deb11u2 (ie
4.13.13 with their tweaks)
https://packages.debian.org/bullseye/samba but I don't know if the
Pi people have changed things (I don't know of a packages.raspios
site).
I'd use sudo dpkg --list | grep samba to tell you versions of all
the packages with 'samba' in the name.
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <ABe*a4SEy@news.chiark.greenend.org.uk>,
Theo <theom+news@chiark.greenend.org.uk> wrote:
Bob Latham <bob@sick-of-spam.invalid> wrote:
Could I install SAMBA 4.9.5 on the later bullseye OS?
How might I go about that?
Yes. Assuming you were on Debian (and this might still work for
PiOS, since they're related), go here: https://packages.debian.org/buster/samba and you can download the
'armhf' package for Samba.
Then you can do:
sudo dpkg --install samba_4.9.5+dfsg-5+deb10u2_armhf.deb
It may well complain about missing dependencies, in which case go
back to the Samba page, find what it needs, and download those .deb
files.
*Beware* that it's possible to get your system in a mess if you
install packages this way that conflict with others that the
packaging system can't resolve. I'd take a backup of your system
before trying this.
I have been building raspberry pie based projects for some time using
the official OS from their website. Last September the OS was called
"buster" and you could edit /etc/samaba/smb.conf and add...
client min protocol=NT1
ntlm auth=yes
This enabled SMB1 so that Lanman98 could connect.
I've tried that today with "bullseye" the latest OS and that config
no longer works. However, my W10 PC connects no problem. It looks to
me as though the doors are now closed on SMB1 and Lanman98.
Anyone got any ideas suggestions, google doesn't mention this
specific issue.
In message <59ae53a42cbob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:
I have been building raspberry pie based projects for some time
using the official OS from their website. Last September the OS
was called "buster" and you could edit /etc/samaba/smb.conf and
add...
client min protocol=NT1 ntlm auth=yes
This enabled SMB1 so that Lanman98 could connect.
I've tried that today with "bullseye" the latest OS and that
config no longer works. However, my W10 PC connects no problem.
It looks to me as though the doors are now closed on SMB1 and
Lanman98.
Anyone got any ideas suggestions, google doesn't mention this
specific issue.
The following in the global section of /etc/samba/smb.conf worked
just fine here on Raspberry Pi OS bullseye 32bit and 64bit.
server min protocol = LANMAN1
In article <dee93abe59.pittdj+@iyonix.home>,
David Pitt <news2@pittdj.co.uk> wrote:
In message <59ae53a42cbob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:
I was told they've made it more difficult as a
warning that they intend to end SMB1 imminently.
In message <59be5b26d9bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <dee93abe59.pittdj+@iyonix.home>,
David Pitt <news2@pittdj.co.uk> wrote:
In message <59ae53a42cbob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:
[snip - enabling SMB1]
I was told they've made it more difficult as a
warning that they intend to end SMB1 imminently.
We should be OK for a bit longer, SMB1 is not slated for removal in
the next upcoming samba release 4.16. Debian bullseye and
Raspberry Pi OS bullseye are in any case a bit behind the sharp
end at samba 4.13.
https://wiki.samba.org/index.php/Samba_Release_Planning
(Link works in Iris.)
By way of belt and braces I have set up an NFS server on Raspberry
OS bullseye. Sunfish will connect to it but the Mac won't.
However, the folders you get in sunfish do my head in and I avoid
at all cost because of that.
On 22 Feb, Bob Latham wrote in message
<59bedb854bbob@sick-of-spam.invalid>:
However, the folders you get in sunfish do my head in and I avoid
at all cost because of that.
Eh? Folders?
In article <mpro.r7py2n00nwttx03ey.news@stevefryatt.org.uk>,
Steve Fryatt <news@stevefryatt.org.uk> wrote:
On 22 Feb, Bob Latham wrote in message
<59bedb854bbob@sick-of-spam.invalid>:
However, the folders you get in sunfish do my head in and I avoid
at all cost because of that.
Eh? Folders?
I'm unsure what you question, the term or the meaning?
For very nearly 40 years everywhere I worked Windows was king and the
term was folders, too old to worry about that.
I mean the menu structure full of folders/directories I find baffling
before you even look at the network shared disc. LM98 better in every
way (while it works) except some of the character mappings.
In message <59bf301accbob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <mpro.r7py2n00nwttx03ey.news@stevefryatt.org.uk>,
Steve Fryatt <news@stevefryatt.org.uk> wrote:
On 22 Feb, Bob Latham wrote in message
<59bedb854bbob@sick-of-spam.invalid>:
However, the folders you get in sunfish do my head in and I
avoid at all cost because of that.
Eh? Folders?
I'm unsure what you question, the term or the meaning?
For very nearly 40 years everywhere I worked Windows was king and
the term was folders, too old to worry about that.
I mean the menu structure full of folders/directories I find
baffling before you even look at the network shared disc. LM98
better in every way (while it works) except some of the character
mappings.
I think Steve was asking what your issue was with folders? I am
also intrigued to know as well, you can navigate them just the same
as LM98.
As for naming issues, you have to remember that all OS's have some
characters are resticted in each OS for different reasons. like /
in Windows and Linux is a folder separator whereas RISC OS uses a .
for that purpose. things like #@#$& etc can be restricted as
different OS's use them for certain OS operations, also some OS's
do not like space and a-acute, some programs treat a space as a
delimiter and chop the rest of the text after it off/ignore it.
I think Steve was asking what your issue was with folders?
With LM98 you have one file, that file has all the setting for one
connection to a network share. Double click that file and you're
connected.
Indeed the name of the file then appears on the icon bar, excellent.
Passwords whilst admittedly still SMB1 are plain and simple user name password combinations.
Not like the UID, GID, umask etc. with NFS, which is no doubt standard
Linux
but after LM98 all quite odd, and seems to rely on ip addresses.
I'm not saying I can't use Sunfish, I can but I don't like it due to its complexity in comparison to LM98.
I'm not saying I can't use Sunfish, I can but I don't like it due to
its complexity in comparison to LM98.
In article <59bf65b7d4news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
https://www.filebase.org.uk/software/communications/network/935
Bob.
On 23 Feb, Bob Latham wrote in message
<59bf4c3780bob@sick-of-spam.invalid>:
I think Steve was asking what your issue was with folders?
I was indeed. The statement "all the folders you get in sunfish"
made absolutely no sense, from the perspective of someone who uses
Sunfish to access all of the work that I do on RISC OS.
In article <59bf4c3780bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
I'm not saying I can't use Sunfish, I can but I don't like it due to
its complexity in comparison to LM98.
I tried it many years ago... I'm saying I couldn't use it because it
wouldn't work.
Obviously my problem with the configs, so I went back to LM98.
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
Thanks
News@
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
In article <59bf65b7d4news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
https://www.filebase.org.uk/software/communications/network/935
In article <mpro.r7rtu901sf86g03of.news@stevefryatt.org.uk>,
Steve Fryatt <news@stevefryatt.org.uk> wrote:
I was indeed. The statement "all the folders you get in sunfish" made absolutely no sense, from the perspective of someone who uses Sunfish to access all of the work that I do on RISC OS.
Well from my perspective they are very different.
I've just run sunfish and icon bar - browse. Folder or window 1
Click on NFS server red Another folder window 2
Then you get menus
I don't yet have a drive on the ibar.
In article <59bf6fa2cabob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <59bf65b7d4news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
https://www.filebase.org.uk/software/communications/network/935
Bob.
Thanks, I already have 2.05 installed.
Not that it makes any difference as you'll note from my recent post. :-(
Dave
In message <59bf7150f8news@triffid.co.uk>
Dave <news@triffid.co.uk> wrote:
In article <59bf6fa2cabob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <59bf65b7d4news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
So with the future in mind, and Steve seems to think it's so easy to
setup, where might a chap get this Sunfish app.
https://www.filebase.org.uk/software/communications/network/935
Bob.
Thanks, I already have 2.05 installed.
Not that it makes any difference as you'll note from my recent post. :-(
Dave
I'd suggest that you obtain a copy via Packman or:
http://riscos.info/packages/arm/Disc/Sunfish_2.05-2.zip
And then getting the FrontEnd ARMV7 compliant !RunImage from:
https://www.riscosports.co.uk/downloads.html
Works here on ARMX6 etc.
Thanks for those URL.
Again the app runs to the icon bar but is still incapable of finding any
Host or IP address. (Icon bar menu- Browse-Search for Host...
VRPC-DL RISC OS 6.20
IP address is 192.168.0.4 and the Host (Windows computer) is blackfan.
Dave
LM98 has no problem seeing and connecting with that.
Server: blackfan
Share: C
D.
In article <59bfa2f053news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
Thanks for those URL.
Again the app runs to the icon bar but is still incapable of finding
any Host or IP address. (Icon bar menu- Browse-Search for Host...
VRPC-DL RISC OS 6.20
IP address is 192.168.0.4 and the Host (Windows computer) is blackfan.
Dave
LM98 has no problem seeing and connecting with that.
Server: blackfan
Share: C
D.
Are you running a NFS server on your target machine? (Moonfish on RISC
OS, you may have to obtain one for Windows, however it is part of Linux)
Richard Darby.
In article <59bfb99995news@rjdarby.co.uk>,
Richard Darby (news) <news@rjdarby.co.uk> wrote:
In article <59bfa2f053news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
Thanks for those URL.
Again the app runs to the icon bar but is still incapable of finding
any Host or IP address. (Icon bar menu- Browse-Search for Host...
VRPC-DL RISC OS 6.20
IP address is 192.168.0.4 and the Host (Windows computer) is
blackfan.
Dave
LM98 has no problem seeing and connecting with that.
Server: blackfan Share: C
D.
Are you running a NFS server on your target machine? (Moonfish on
RISC OS, you may have to obtain one for Windows, however it is part of Linux)
Richard Darby.
Thanks for the thought Richard. TBH. I have no idea what any of that
means...
At present I have LM98, I configure the Servers and Shares in the
required files and it works between this machine, and other machine on
the LAN.
Mr Fryatt seems to think Sunfish is so easy to setup, obviously it is
Not!
Dave
In article <59bfb99995news@rjdarby.co.uk>,
Richard Darby (news) <news@rjdarby.co.uk> wrote:
In article <59bfa2f053news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
Thanks for those URL.
Again the app runs to the icon bar but is still incapable of
finding any Host or IP address. (Icon bar menu- Browse-Search
for Host...
VRPC-DL RISC OS 6.20
IP address is 192.168.0.4 and the Host (Windows computer) is
blackfan.
Dave
LM98 has no problem seeing and connecting with that.
Server: blackfan Share: C
D.
Are you running a NFS server on your target machine? (Moonfish
on RISC OS, you may have to obtain one for Windows, however it is
part of Linux)
Richard Darby.
Thanks for the thought Richard. TBH. I have no idea what any of
that means...
At present I have LM98, I configure the Servers and Shares in the
required files and it works between this machine, and other machine
on the LAN.
Mr Fryatt seems to think Sunfish is so easy to setup, obviously it
is Not!
Are you running a NFS server on your target machine? (Moonfish on RISC
OS, you may have to obtain one for Windows, however it is part of Linux)
Richard Darby.
Thanks for the thought Richard.
TBH. I have no idea what any of that means...
In article <59bfb99995news@rjdarby.co.uk>,
Richard Darby (news) <news@rjdarby.co.uk> wrote:
In article <59bfa2f053news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
Thanks for those URL.
Again the app runs to the icon bar but is still incapable of finding
any Host or IP address. (Icon bar menu- Browse-Search for Host...
VRPC-DL RISC OS 6.20
IP address is 192.168.0.4 and the Host (Windows computer) is blackfan.
Dave
LM98 has no problem seeing and connecting with that.
Server: blackfan
Share: C
D.
Are you running a NFS server on your target machine? (Moonfish on RISC
OS, you may have to obtain one for Windows, however it is part of Linux)
Richard Darby.
Thanks for the thought Richard.
TBH. I have no idea what any of that means...
At present I have LM98, I configure the Servers and Shares in the required files and it works between this machine, and other machine on the LAN.
Mr Fryatt seems to think Sunfish is so easy to setup, obviously it is Not!
IIRC you have a an old Synology NAS Dave?
If so log in,
Control panel
File Services
First tab SMB/AFP/NFS
Scroll down to the bottom..
Enable NFS - Apply.
Bob.
Indeed I do Bob,
Unfortunately, these days I hardly ever use it and I certainly
wouldn't want to have it in action for every day use, it's just
soooooo damn slow to do anything.
Found Sunfish 2.05 put it in my VRPC-DL RISC OS 6.20
Did the Search for Host and tried with both Hostname and IP address... Nothing except an error.
** WimpError ** from Sunfish
Error : &00000000
Message: Error when sending or receiving data (Operation timed out)
Apart from the obvious... I've no idea what that means.
?
So it seems, to get this easy to set up and use thing working, I need
Sunfish and something called Moonfish installed on RISC OS.
IIRC you have a an old Synology NAS Dave?
If so log in,
Control panel
File Services
First tab SMB/AFP/NFS
Scroll down to the bottom..
Enable NFS - Apply.
Unfortunately, in my family, folks seem to hang on until in the late 80s.
In article <59bfc842cabob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
IIRC you have a an old Synology NAS Dave?
If so log in, Control panel File Services First tab SMB/AFP/NFS Scroll
down to the bottom.. Enable NFS - Apply.
Thanks for that Bob, Did that, and got a Diskstation icon in the Sunfish
NFS servers window.
But that's it, nothing else, when clicked it just brings up a small new
empty filer window.
No idea how it would show the files on the NAS. (Yes lots of files on the NAS)
Best of all... When I did "Search for host" it totally froze RISC OS, and I mean totally, requiring an exit by naughty methods.
In article <59bff2b897news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
Unfortunately, in my family, folks seem to hang on until in the late 80s.
I'm happy to read that Dave, as I enjoy reading your posts.
As a result of this thread, I also downloaded Sunfish on my Pi4. It runs,
it finds one single map on my QNAP NAS automatically, and I even managed to write a file to it. But whatever I do next, even just a mouse click, it
will invariably crash Sunfish with a postmortem. Although this is still a
bit better than your experience, it hardly can be called useful.
So, you're not alone.
In article <59bfc842cabob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
IIRC you have a an old Synology NAS Dave?
If so log in,
Control panel
File Services
First tab SMB/AFP/NFS
Scroll down to the bottom..
Enable NFS - Apply.
Thanks for that Bob, Did that, and got a Diskstation icon in the
Sunfish NFS servers window.
But that's it, nothing else, when clicked it just brings up a small
new empty filer window.
No idea how it would show the files on the NAS. (Yes lots of files
on the NAS)
I have not used Sunfish myself, but I do have a Synology box which I
can connect to using the NFS that is part of a modern OmniClient.
To do that I have to define a mount to NFS which includes
- Name for display on RISC OS
- Server name (ie DiskStation or whetever)
- Directory name, which is the shared folder name on the Synology
- User Name/password for read/write access to that shared folder.
Ie very similar to LanMan[98]
I assume that similar details have to be set in Sunfish for it to
display the mounted folder.
But I also have no bother directly accessing my shared folders on
Win10pro using LanMan98!
In article <59bff2b...@triffid.co.uk>,
Dave <ne...@triffid.co.uk> wrote:
In article <59bfc8...@sick-of-spam.invalid>,
Bob Latham <b...@sick-of-spam.invalid> wrote:
IIRC you have a an old Synology NAS Dave?
I have not used Sunfish myself, but I do have a Synology box which I
can connect to using the NFS that is part of a modern OmniClient.
To do that I have to define a mount to NFS which includes
- Name for display on RISC OS
- Server name (ie DiskStation or whetever)
- Directory name, which is the shared folder name on the Synology
- User Name/password for read/write access to that shared folder.
Check that it's Info box says
2.05 (08 Jun 2013)
In article <59bfc842cabob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
IIRC you have a an old Synology NAS Dave?
If so log in,
Control panel
File Services
First tab SMB/AFP/NFS
Scroll down to the bottom..
Enable NFS - Apply.
Thanks for that Bob,
Did that, and got a Diskstation icon in the Sunfish NFS servers
window.
But that's it, nothing else, when clicked it just brings up a small
new empty filer window.
No idea how it would show the files on the NAS. (Yes lots of files
on the NAS)
In article <63df4320-7c95-4672-970f-46f47e6c8aben@googlegroups.com>,
Sprow <news@sprow.co.uk> wrote:
SetEval Omni$NFS
My former post crossed yours. Setting Omni$NFS to 1 enables the
extra options indeed. But unfotunately, it doesn't change anything
about the horrible and continuous crashes.
SetEval Omni$NFS
It does. (I already followed your download instructions.)
Although it does make contact to one particular directory on my QNAP NAS,
and although I'm able to read and write from/to that directory, there's nothing else that I can do that doesn't crash Sunfish immediately. It seems as if half of the menu entries are missing. For example, 'Edit entry' just isn't there, nor is the 'name mount window'. The help file talks about options that I just can't find, while the continuous crashes discourage me from trying again and again. Could it be the Pi4 (4té actually), that is
too advanced for a program that hasn't been updated for 9 years?
On Thursday, February 24, 2022 at 11:44:54 PM UTC, Martin wrote:
In article <59bff2b...@triffid.co.uk>,
Dave <ne...@triffid.co.uk> wrote:
In article <59bfc8...@sick-of-spam.invalid>,
Bob Latham <b...@sick-of-spam.invalid> wrote:
IIRC you have a an old Synology NAS Dave?
I have not used Sunfish myself, but I do have a Synology box which I
can connect to using the NFS that is part of a modern OmniClient.
To do that I have to define a mount to NFS which includes
- Name for display on RISC OS
- Server name (ie DiskStation or whetever)
- Directory name, which is the shared folder name on the Synology
- User Name/password for read/write access to that shared folder.
If you find Sunfish crashy, it's worth giving the NFS client included with RISC OS 5 (though it's not specific to RISC OS 5) a look in as Martin
says.
The one bit of instruction he's missed though is that it's turned off in OmniClient by default. To enable it change the line
SetEval Omni$NFS
to 1 in the !Omni.Files.Startup obey file. That causes the NFS client to
be loaded after which you can enter the mount details along the lines described above,
Could it be the Pi4 (4té actually), that is
too advanced for a program that hasn't been updated for 9 years?
Ok so if you have browsed for a NFS server it will be in the SunFish
window that has a title like NFS Servers.
You will see the actual server s you can see there most likely with a IP address.
Select mouse one of them and then hit the Menu mouse button and then
Browse 'IP address' and you can set if the transport is UDP/TCP and also
the NFS level.
If you double click select mouse on the server you then have another
window with a picture of a directory including the sunfish icon in it.
Select that and then mouse menu and edit 'directory name' and you can :
Name export - what it is called
Filename and filetype choices
Connection choices
User id choices
All this is covered in the help file within Sunfish.
What is crashing horribly?
And how?
I get the message "RPC communication failed on the mount" in an error box.
Omniclient 2.28 (15 Mar 18) and NFS 0.71 (29 Jan 18)
The other thing is my Pi4 is running RISCOS 5.29 (6 Feb 2022) version.
There was some issues in earlier ROM's that caused system crashes on use
of menu which have been fixed in recent beta's.
In message <8e0841c059.chris@mytarbis.plus.com>
Chris Hughes <news13@noonehere.co.uk> wrote:
I get the message "RPC communication failed on the mount" in an error box.
Omniclient 2.28 (15 Mar 18) and NFS 0.71 (29 Jan 18)
Most likely you have not enter the correct details.
Just tried it to Moonfish running on another machine here:
Server Name - Used IP address or can use it's name
Directory Path - Put in the directory name that is being exported in this case 'NFS'
User name - used 'nobody'
And it is connected but you don't get the same flexibility that SunFish provides on NFS versions/transport type udp/TCP etc
I have tried this on an ARMX6 and RaspberryPi4 and no crashes :-)
If you find Sunfish crashy, it's worth giving the NFS client included with RISC OS 5 (though it's not specific to RISC OS 5) a look in as Martin
says.
The one bit of instruction he's missed though is that it's turned off in OmniClient by default. To enable it change the line
SetEval Omni$NFS
to 1 in the !Omni.Files.Startup obey file. That causes the NFS client to
be loaded after which you can enter the mount details along the lines described above,
Tried that but the module is not present here - RO 5.28 on Titanium.
Error from (unknown): File '<Omni$Dir>.RMStore.NFS' not found
Any idea where I can get the file?
On 25 Feb, Sprow <news@sprow.co.uk> wrote:
If you find Sunfish crashy, it's worth giving the NFS client included with >> RISC OS 5 (though it's not specific to RISC OS 5) a look in as Martin
says.
The one bit of instruction he's missed though is that it's turned off in
OmniClient by default. To enable it change the line
SetEval Omni$NFS
to 1 in the !Omni.Files.Startup obey file. That causes the NFS client to
be loaded after which you can enter the mount details along the lines
described above,
Tried that but the module is not present here - RO 5.28 on Titanium.
Error from (unknown): File '<Omni$Dir>.RMStore.NFS' not found
Any idea where I can get the file?
Try here:
<https://www.riscosopen.org/content/downloads/common>
HardDisc4 Inside the apps directory.
Thanks - I have it now and just need a bit of time to have a play
with it. Got it connecting to my Synology NAS box so far.
I get the message "RPC communication failed on the mount" in an error box. Omniclient 2.28 (15 Mar 18) and NFS 0.71 (29 Jan 18)
In message <1f1b62c059...@bhowlett.plus.net> Brian Howlett <news-s...@brianhowlett.me.uk> wrote:
Error from (unknown): File '<Omni$Dir>.RMStore.NFS' not foundTry here:
Any idea where I can get the file?
https://www.riscosopen.org/content/downloads/common
HardDisc4 Inside the apps directory.
I've got sunfish working but not Omni.
There doesn't appear to be any useful help information within the app.
Both failed with "Insufficient Access".
In article <59c0b576b1bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
I've got sunfish working but not Omni.
There doesn't appear to be any useful help information within the app.
I can only describe how I managed to get an NFS connection with
Omni: From the iconbar menu go to Mounts -> Protocols -> NFS Now
enter...
Name: <the name that you want to see on the iconbar> Server name:
<the IP adress of your NAS> Directory path: <the directory name,
without slashes. Mine is Public>
... and leave all other entries blanc. I then get a special NFS
icon on the iconbar that connects me to the Public directory on the
NAS.
In article <59c0c32341bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
Both failed with "Insufficient Access".
This should be answered by someone with a lot more knowledge than
me (mine is close to zero), but "Insufficient Access" sounds like a restriction from the NAS, rather than from Omni. Perhaps you need
to enable special rights on the NAS, or something like that (as I
may have written before, my knowledge is close to zero).
** WimpError ** from OmniClient Error : &00012112 Message: RPC
communication failed on mount (RPC Service not available on remote
host (not registered))
No idea what that means either.
In article <59c0c888c9news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
** WimpError ** from OmniClient Error : &00012112 Message: RPC
communication failed on mount (RPC Service not available on remote
host (not registered))
No idea what that means either.
One assumes an NFS server is not running on the remote machine.
In message <8e0841c0...@mytarbis.plus.com> Chris Hughes <new...@noonehere.co.uk> wrote:
I get the message "RPC communication failed on the mount" in an error box. >> Omniclient 2.28 (15 Mar 18) and NFS 0.71 (29 Jan 18)
Those are oddly old versions, maybe you missed an update? I'd have
expected OmniNFS 0.73 (Jan 2020). OmniNFS doesn't do much, the real work
is done by 'RMStore.NFS' which is also needed...
In message <1f1b62c059...@bhowlett.plus.net> Brian Howlett
<news-s...@brianhowlett.me.uk> wrote:
Error from (unknown): File '<Omni$Dir>.RMStore.NFS' not foundTry here:
Any idea where I can get the file?
https://www.riscosopen.org/content/downloads/common
HardDisc4 Inside the apps directory.
The standard set of ROOL apps (aside from !Boot) are also packaged as individual ZIPs, so you can avoid downloading the entire disc image by
going to
https://packages.riscosopen.org/rool/ABCIndex.html
In article <63df4320-7c95-4672-970f-46f47e6c8aben@googlegroups.com>,
Sprow <news@sprow.co.uk> wrote:
SetEval Omni$NFS
My former post crossed yours. Setting Omni$NFS to 1 enables the extra
options indeed. But unfotunately, it doesn't change anything about the horrible and continuous crashes.
In message <59c0ce9082chrisjohnson@spamcop.net>
News <chrisjohnson@spamcop.net> wrote:
In article <59c0c888c9news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
** WimpError ** from OmniClient Error : &00012112 Message: RPC communication failed on mount (RPC Service not available on remote host (not registered))
No idea what that means either.
One assumes an NFS server is not running on the remote machine.
I have had the same message and it is running on the Synology NAS.
Got it working now with Sunfish, but not with Omni(NFS) - I get the above message when using Omni(NFS)
But unfotunately, it doesn't change anything about the
horrible and continuous crashes.
Try turning alignment exceptions off.
I have had the same message and it is running on the Synology NAS.
Got it working now with Sunfish, but not with Omni(NFS) - I get the
above message when using Omni(NFS)
Note I have update version Of !Omni after Sprow's comments made no difference.
In message <b2d8d1c059.chris@mytarbis.plus.com>
Chris Hughes <news13@noonehere.co.uk> wrote:
In message <59c0ce9082chrisjohnson@spamcop.net>
News <chrisjohnson@spamcop.net> wrote:
In article <59c0c888c9news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
** WimpError ** from OmniClient Error : &00012112 Message: RPC
communication failed on mount (RPC Service not available on remote host >>>> (not registered))
No idea what that means either.
One assumes an NFS server is not running on the remote machine.
I have had the same message and it is running on the Synology NAS.
Got it working now with Sunfish, but not with Omni(NFS) - I get the above
message when using Omni(NFS)
Same here. There is definitely a difference in the implementation of the protocol between Sunfish and Omni.
I can get a connection and see the share via Omni and NFS if I leave the username as "nobody" and leave the password blank, but it's read only -
I cannot write anything to it.
I used Wiresalmon last night to look at the difference between what was
sent using "nobody/(blank)" and "user/password", and IIRC the latter
made an RPC call to pcnfsd, which doesn't seem to be running on my NAS (OpenMediaVault). I must have another look tonight, and also look at how Sunfish does it.
In article <59c0c888c9news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
** WimpError ** from OmniClient Error : &00012112 Message: RPC communication failed on mount (RPC Service not available on remote
host (not registered))
No idea what that means either.
One assumes an NFS server is not running on the remote machine.
I agree, any idea where Omni stores its mount files?
I agree, any idea where Omni stores its mount files?
In article <59c0c888c9news@triffid.co.uk>,
Dave <news@triffid.co.uk> wrote:
** WimpError ** from OmniClient Error : &00012112 Message: RPC communication failed on mount (RPC Service not available on remote host (not registered))
No idea what that means either.
One assumes an NFS server is not running on the remote machine.
It's most definitely running on my NAS too, as witnessed by Sunfish's
ability to access its drives.
I think the error message is misleading. It says the RPC Service is
not available, which would lead one to think that RPC as a whole is
not working (and inevitably make one suspect no NFS server at all).
But I suspect it means that the particular service that has been
requested via RPC is not available, and I think it's pcnfsd. Then
the next question is why Omni wants to use something that Sunfish
clearly doesn't need to.
David Higton <dave@davehigton.me.uk> wrote:
It's most definitely running on my NAS too, as witnessed by Sunfish's ability to access its drives.
I think the error message is misleading. It says the RPC Service is not available, which would lead one to think that RPC as a whole is not
working (and inevitably make one suspect no NFS server at all). But I suspect it means that the particular service that has been requested via RPC is not available, and I think it's pcnfsd. Then the next question is why Omni wants to use something that Sunfish clearly doesn't need to.
PCNFS is a separate service to authenticate username/password, which is not part of the bare NFS protocol. It's old (1980s) and modern NFS servers
don't use it. I don't know if it's something Omni requires but Sunfish doesn't care about - Sunfish postdates the era where pcnfs was in use.
ISTR pcnfsd being removed from Debian something like 20 years ago, for example.
I'm not familiar with Omni, but perhaps if you remove any mention of
username and password it won't try and use pcnfs?
It's most definitely running on my NAS too, as witnessed by Sunfish's
ability to access its drives.
In message <mLf*kV4Hy@news.chiark.greenend.org.uk>
Theo <theom+news@chiark.greenend.org.uk> wrote:
David Higton <dave@davehigton.me.uk> wrote:
It's most definitely running on my NAS too, as witnessed by Sunfish's ability to access its drives.
I think the error message is misleading. It says the RPC Service is not available, which would lead one to think that RPC as a whole is not working (and inevitably make one suspect no NFS server at all). But I suspect it means that the particular service that has been requested via RPC is not available, and I think it's pcnfsd. Then the next question is why Omni wants to use something that Sunfish clearly doesn't need to.
PCNFS is a separate service to authenticate username/password, which is not part of the bare NFS protocol. It's old (1980s) and modern NFS servers don't use it. I don't know if it's something Omni requires but Sunfish doesn't care about - Sunfish postdates the era where pcnfs was in use.
ISTR pcnfsd being removed from Debian something like 20 years ago, for example.
I'm not familiar with Omni, but perhaps if you remove any mention of username and password it won't try and use pcnfs?
Isn't that a paraphrasing of what I said? The problem being that you
then get read-only access.
On 26/02/2022 23:21, David Higton wrote:
It's most definitely running on my NAS too, as witnessed by Sunfish's ability to access its drives.
The issue is probably a weird NFS setup on your NAS, which it may or ay
not be easy to solve. An alternative would be to use a Linux Raspberry Pi
as a file server for your RISC OS machine, as SunFish works perfectly with the Rasbian's NFSd. You don't even need move the storage on to the Pi,
just mount the NAS shares on the Pi, and reshare using NFSd to RISC OS.
David Higton <da...@davehigton.me.uk> wrote:
It's most definitely running on my NAS too, as witnessed by Sunfish's ability to access its drives.
I'm not familiar with Omni, but perhaps if you remove any mention of
username and password it won't try and use pcnfs?
On Tuesday, March 1, 2022 at 2:35:23 PM UTC, Theo wrote:
David Higton <da...@davehigton.me.uk> wrote:
It's most definitely running on my NAS too, as witnessed by Sunfish's ability to access its drives.
I'm not familiar with Omni, but perhaps if you remove any mention of username and password it won't try and use pcnfs?The username/password authentication is only attempted if there's a server entered in the "Authenticator" field in Omni. See page 180 of the RISC OS 5.28 User Guide for details. Using
Server = 10.0.0.99 (its IP address)
Dir = /home/myname
Username = nobody (and a blank password)
OmniClient connects to a FreeBSD NFS mount just fine. Since I trust myself at both ends I then map the user "nobody" to have read/write permissions, otherwise that user ID is stuck being read-only,
Sprow.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 27:04:50 |
| Calls: | 6,646 |
| Calls today: | 1 |
| Files: | 12,193 |
| Messages: | 5,328,055 |