Network access to Win10

My home network has RISC OS plus Macbook and a Win machine. Last week I updated the Win 7 to Win 10 and I now can’t access the 2Tb HDD on the Win machine.
As I get the message from RISC OS that “ACCESS denied” am I correct in believing that permissions on the Win side have changed?
Has anyone else had this problem and found a solution please? I have gone through and checked access levels and made the drives shared to no avail.

If you search for “Turn Windows features on or off” is ‘SMB 1.0/CIFS Server’ enabled?

I recently replaced my laptop with a Windows10 one. I had the same problem, and eventually discovered that SMB1 wasn’t present, rather than just disabled. Having installed it (accompanied by the dire and justified warnings about security) it works.

Having installed it (accompanied by the dire and justified warnings about security) it works.

SMB1 is known to be easily compromised, however on a private network like a home setup the security of the router on the internet connection is more of a concern.
It should also be noted that the latest patch for Win10 is addressing a major security hole in SMB3 so there’s no guarantee that the most recent version is really secure either.

Thanks for the suggestions. SMB1 was switched on.

Is your username an email address? If so it may be too long for a username in LanManFS

I’ve checked and you get ‘Access denied if your username is too long. Here’s a version of lanmanfs which will cope with long usernames.

Thanks Colin. My username is still the same as I’ve been using for years. It truncated to whatever the limit was and has happily worked with that. I forgot to mention that my networking is done via Omni – perhaps I might need to change to lanmanfs but I’m reluctant to as I’d have to go through the process of setting it up and as it’s an age since I did the networking I’m not sure of what to do.

I forgot to mention that my networking is done via Omni

Omni is just a front end. It will be using LanManFS (or possibly LanMan98 if you set that up) to do the actual transfers.

Thanks Chris – you can see that I’ve forgotten most of what I did in networking. My machine is an ARMx6 from r-comp so it will be whatever was installed. Perhaps I should ask Andrew if they have suggestions on what set-up is needed in win 10

SMB1 is known to be easily compromised, however on a private network like a home setup the security of the router on the internet connection is more of a concern.

However don’t forget that the wireless part of your router is connected to the internal (i.e. in your home) side of the network, and is accessible from outside your premises. In addition if you have a laptop, any time that is connected to a public network it is more vulnerable.

For both of these situations you need to ensure that your PC is protected. You need a good firewall (I don’t know how good the Windows built-in one is compared with commercial ones) and good anti-virus software, because that usually contains additional protection tools as well.

With Andrew Rawnsleys expertise the problem came down to (Win10) not having a user “everyone” with full permissions and with SMB1.
He also supplied an up to date copy of the recently open sourced LanMan98. This installed simply on the ARMX6 and was quickly configured.

Thanks Andrew.

recently open sourced LanMan98.

Are you sure about that? What version?

problem came down to (Win10) not having a user “everyone” with full permissions.

I don’t have user ‘everyone’ on my windows 10 share, just ‘SYSTEM’ ‘my user name’ and ‘Administrators’ so maybe you’ve cured the symptom rather then the cause.

LM98 2.06 ROD version

v2.06 was commercial. Perhaps ROD have made a deal with WSS? What evidence is there that it is ‘open source’ ?

That was stated by Andrew Rawnsley in the email he supplied it to me in.
“Opensource version of LM98 attached.”

We’ve been teasing this one since October show last year, but didn’t receive full source until after the SW show (thanks go to Robin at WSS, and Richard at ROD who organised things). We’d intended to make a public release in time for Wakefield. I guess the cat is now out of the bag :)

The reason we haven’t formally released it yet is one of presentation and packaging, and also how best to make the source available (ie. beyond supplying it with the program). Richard and I have been exceedingly busy all year, and our priorities have been with the RISC OS Direct initiative (somewhat frustrated by coronavirus preventing gatherings for distribution of SD cards!). I’m also trying to enhance the presentation/package of the next Impression-X release too, whilst finding time to complete my other R-Comp/RCI work.

We’re actually still waiting on source for something else, too, but that’ll have to wait.

Request – if someone wants to volunteer to help sort out/house a git repository or some such for the source, that’d be one less worry for me.

Request – if someone wants to volunteer to help sort out/house a git repository or some such for the source, that’d be one less worry for me.

These days, I’d have thought that one (or more) of the big name sites would be the sensible home, unless there’s a desire to use somewhere like ROOL or RISC OS.info. I’ve certainly been considering this for my own code, mainly because it moves a lot of the backup problem on to someone else.

Which site is largely down to personal preferences/prejudices, I suspect. :-)

Just out of interest, having downloaded the LanMan98 package from PlingStore, what licence is it Open Sourced under? There’s no mention anywhere in any of the documentation, as far as I can see.

I’m in the process of grudgingly moving from Windows 7 to 10 but can’t get Omniclient to connect to my Win 10 shares. The box multiboots so I still have the Win 7 installation and everything works fine still there.

I’m on the an up-to-date Windows 10 version, Windows 10 Enterprise, v 20H2, OS build 19042.789 and I ahve enabled SMBv1, both client & server.

Is this a case of an update changing things or is there something else I need to do from either Windows or RISC OS with respect to Win 10.

As I say, if I boot into Win 7, all is good again.

I downloaded LanMan98 but of course that makes no difference.

I’m a bit behind on RISC OS (5.23) if that makes a difference.

The best guide I know for “Connecting a RISC OS computer running LanMan98 to a Windows 10 PC” is Bernard Veasey’s guide available here

Also recently a lot of discussion here

Yeah, I have tried all those things. The only differences I can see/think of is that my windows machine is part of a domain as opposed to a workgroup or the version of windows itself is the problem, i.e. some new update or other.

I’ll maybe look at some other method of linking to Windows 10.

Thank you for the response.

Ok, progress. Tried another Win 10 pc (VM), not domain joined and that works as expected out of the box. Nothing changed in Advanced Sharing just SMBv1 enabled. Slightly different build (19042.746).

So, bummer.

Sunfish/Moonfish don’t seem to work here. Any other options?

Sunfish/Moonfish don’t seem to work here.

That’s too short to be only understood one way. Sunfish and Moonfish work fine between each other – that’s what I use at home here. I also use Moonfish to share the RPi’s Ram disc with the Linux box. Sunfish and Moonfish implement NFS. However, Microsoft appears to want nothing to do with NFS, so you can’t use Sunfish or Moonfish to interwork with a Windows box. I’ve heard that it’s difficult to find even an NFS add-on for Windows, although I have no direct experience because I don’t use Windows.