Omni / Lanman98 setup? (oh, and IMAP)

Recent installs on Windows10 (like mine which was new in November 2019) do not have SMB1 installed. It has to be added.

Alan, Colin, Andrew and I have already stated that and provided Jasmine with details on how to do it and it has been confirmed twice now that it is set up.

Add SMB 1 server (and client perhaps, but certainly server) support to Win10 via Add/Remove Programs window (then click Add/Remove Windows Features)

Open start menu and type ‘settings: turn windows features on or off’
bq. Click on ‘Turn windows features on or off’

expand ‘SMB 1.0/CIFS file sharing support’
deselect ‘SMB 1.0/CIFS Automatic removal’
select ‘SMB 1.0/CIFS Server’
select ‘SMB 1.0/CIFS Client if you want to connect to a smb 1.0 device
from windows eg my wifi hub works as a
smb 1.0 NAS when it has a memory stick
inserted in its usb port. It’s not
necessary to just connect to the PC.

Restart the PC.

Got things set up on the Windows side (SMB server and client both added

Double checked SMB settings and all good there.

Doesn’t harm asking again as the direct IP address errors it may give a clue.

In McAfee firewall I set under Ports & System the Firewall option for Windows File sharing (NetBios) Ports 137-139 to on/use.

Yep. Just to confirm. SMB 1.0 client and server installed and active.

Firewall OK. When reset to default it blocked and caused TCP/IP timeout error. Added the port exceptions back in (in and out) and now back to refuse connection with no timeout issue.

On the plus side – Got Messenger Pro off !Store, and it’s working like a gem with Gmail! (had to the app p/w, but minimal hassle and it’s perfectly happy). Interface is a little unusual, but the documentation is solid and makes it nice and easy :) Thanks for the advice on that one, Andrew. I was debating about playing around with Pluto, but it seemed a lot more fiddly. Alas, El Cheapo post office broadband doesn’t give me “real” usenet access though, which is a shame.

I can’t speak for Windows 10, but I believe earlier versions needed extra stuff installed and a few registry hacks in order to coax the thing into talking “old insecure” SMB.

I don’t know what is going wrong but I’ve found windows 10 easy to setup for smb1 and LanMan just enable smb1 server, share folder, set permissions to full done. Absolutely nothing else needs to be done – no messing with firewall/registry/network setting. Other than enabling smb1 the rest is the same process for an smb3 connection.

Unfortunately Jasmine’s machine has decided to put up a fight.

Did we establish that Jasmine isn’t using third party antivirus software?

@Jasmine

Do you have any other devices that run a different os (linux, windows) just to test if anything can connect?

I’ve just been reading some of Microsoft’s stuff about enabling/disabling SMB1. The only thing that stood out for me was the requirement to restart the machine after making the changes.

I’d echo the suggestion to check whether third party AV/firewall is in use. That has caught me before now.

WireSalmon captures the network traffic on a RISC OS machine. Installing Wireshark on the Windows box, and transferring the capture file via a USB key, might provide some useful information.

Well, I never knew that… Microsoft provide information about “Auditing SMBv1 usage”, which applies to W10 among others. Google for it.

OK, scratch head :-)

Lets just try a couple of other things.

1. Saw a post about not having a user Everyone set up as causing same issues so perhaps make sure that is set up.

With Andrew Rawnsleys expertise the problem came down to (Win10) not having a user “everyone” with full permissions and with SMB1

2 – Set up a share on the Windows 10 machine that shares the whole C drive for everyone/user on it and then try that.

3 – Set up a new user with Admin level and try sharing via that. Keep the user name and password simple no fancy characters etc.

Update. That new user should be logged in to first as well and do there sharing from inside the new user environment.

4) Dump Windows :-) :-)

5) Try sharing using FTP or NFS to the Windows machine though you may need to install additional software.

Try this video to see how to

Two snags with that – one is if you need to change browser for some reason. The other is if the Firefox saved password file gets lost, e.g. reinstalling Windows.

That’s what a password manager is for. Sites like 1Password or LastPass come with plugins for browsers like Firefox, and usually get good feedback – with security researchers taking the view that you’re better using one than not. If you prefer a DIY approach, then the various KeePass applications seem to be well-liked.

I don’t know what most of my passwords are now, with my password manager generating a new, random 16 character string each time I need one.

There are some RISC OS options, but I’ve not looked at them in detail. Just make sure that they properly encrypt your passwords when they store them to disc, and preferably store them encrypted in memory, too.

Exactly as you have surmised, it scans through the module commands and if not found, it will evaluate Run$Path to look for a file with the same name.

Aliases fall into the list somewhere, too. Is it aliases, module commands then Run$Path, or module commands, aliases then Run$Path?

Just a small side note that it is generally easier to share a sub-folder on a drive than the “whole” drive on modern windows versions. Sharing a root folder is difficult because (if I recall) there was no quick/automated way of sorting out sub-folder permissions. I may have this wrong – it is a while since I did it. It is generally easier to just share the sub-folder. Also, don’t forget to do the “simple” share first, before diving into Advanced. This is important as the simple share seems to do most of the heavy lifting (again, if memory serves).

I will also add that contrary to some of the advice on this thread, I normally end up using LM98 to do this, as I still find LanManFS “uncomfy” although Colin, JB, and (ach, can’t remember his name – worked for Castle at one point) have done a lot of work improving LanManFS in the last few years. I think ultimately I find Omni’s menu-driven UI a bit fiddly and prefer LM98’s mini front end.

Not other AVs or firewalls other than the built in Windows Defender stuff. It’s a pretty much stock windows.

Other shares all working fine:
Win10 media centre – standard windows share ethernet
Win10 laptop – standard windows share over wifi
Android phone – SMB1 share over wifi using Solid Explorer

Just a small side note that it is generally easier to share a sub-folder on a drive than the “whole” drive on modern windows versions

I agree but the MUG member concerned tried everything like Jasmine has and it was only when he shared the whole drive and for “Everyone” that it worked on the Users folders. I suspected some permissions issues.

SMB1 share over wifi using Solid Explorer

Haven’t recent versions
changed to using SMB2 and doesn’t it use Port 445.

If this is the case all the above don’t use SMB1 or Port 137/139?

I may be wrong, most likely :-)

It gives you the option of SMB1 or SMB2. Honestly don’t know what port numbers it’s using, but I set up a new share on SMB1 just to test it, and it went through fine no problems, using the same login I set up for riscos. My normal share on the phone is SMB2 and that works fine too :)

I did say I could be wrong.

I think SMB1 can use either port 139 or 445 but RISC OS Samba?lanMan/LanMan98 can only do Port 139 as it uses Netbios over IP. Though open to correction on that.

Couple of things to confirm:

1 – As Colin said earlier have you done a restart not a power down/power up on the Windows machine?

2 – Is NetBios over IP enabled. Not sure we asked this earlier?

-Open the Network Connections folder.
-Right click the local area network connection and click Properties.
-Double click Internet Protocol (TCP/IP).
-Click Advanced. Click WINS.
-Click the Enable NetBIOS Over TCP/IP button

3- You mentioned Plusnet , have you a Plusnet Hub One router and perhaps you could try a USB drive in it’s USB port and if SMB1 is working on your Windows 10 machine it will see it unless they have tightened things up again.

I find Omni’s menu-driven UI a bit fiddly and prefer LM98’s mini front end.

I agree with that but if you are having problems LanMan is easier as it eliminates authentication problems

Also, don’t forget to do the “simple” share first, before diving into Advanced. This is important as the simple share seems to do most of the heavy lifting (again, if memory serves).

I find “simple” share very unintuitive. If you are in a folder and share via the ribbon or via the folders properties creates a share that is equivalent to an Advanced share, permissions full on the ‘Users’ directory – it has little to do with the folder you were in where you created the share. The only reliable way to undo the process is to untick ‘share this folder’ in the ‘Users’ properties.

At least with advanced sharing in a folders properties you know where to look to reverse the process.

• Restart: Yep. Have restarted both win PC and riscos pi after each change, just to be safe.

• NetBios over TCP/IP: On

• I’m on Post Office, not plus net. There is a USB on my router so gave it a try and not seeing anything, though I have a feeling it’s just a diagnostic port or somesuch and not a full-blown network interface.

Error: rejected :(

It might be worth looking at the event logs on Windows. To see the useful one, you need to be logged in with an administrator account.
In the search box, type eventvwr
Select Windows Logs
Select security.
Look for any red entries at the time when you tried to connect. If there is anything, then the message might be of some help.
Note however that a lot of what appears in there is not understandable by mere mortals, and a certain amount of red messages are normal.

Another approach: I thini you said you had two windows pcs. Can you access the area you are trying to share to RISC OS from the other Windows machine? Did you need a username and password to do it? Are you using the same ones from RISC OS?

And is the sharing set up with a username that HAS a password? I’m fairly sure it won’t work for a user without a password.

is the pi plugged in to the router or the pc?

Ok lets try another tact and see if the PC can see a Samba set up on the Pi

Download “Samba Server”: http://www.gag.de/software/smbserver.html
from Thomas Milius which has some changes that may work better on the Pi.

Install that and set it up and see if your PC can see the samba share on the Pi.

If it can then the network is OK and it is something in the set up on your PC.

If you still want this working, could you download lanmandebug.zip and double click on LanManFSD and !Reporter – which is included

Then try and connect to your PC share. Debug data should appear in the reporter window. When it fails, Select Menu→save on the reporter window. If the reporter window is not clear before you try to connect can you clear the reporter window with menu→clear

Can you then sent me the saved file (it will be called ReportSave01 – the number may be different – in the ram disc) to my ftpc email address on this page. or if its only a small amount of data – which I suspect it will be – you may prefer to post it on the forum.

Hi Colin,

Excellent work and I suggest Jasmine uses your more scientific response than my Samba Server speculative one.

…and !Reporter – which is included

I am glad it might be useful … but I notice that the included version is v2.71 (04 Dec 2015), and the current version is v2.72 (15 Aug 2020).

try and connect to your PC share

Can I just add you can’t connect using a dotted server name (eg 192.168.0.34) you must use the server name.

I am glad it might be useful

I think it’s great.

Colin,

Out of interest I tried it here on my ARMX6 and it locked up the machine.

Then I remembered last night I was playing with the McAfee set up specifically the Firewall Intrusion protection option that was off and I changed it to On last night.

Anyway turning it to off allowed things to work without the lock up.

I then tried the normal LanMan98 with the Intrusion Protection on and it gave an error:

“Error when reading LanMan98#notypes::”My PC name" Connection down.

I suspect the Intrusion Protection option stops certain activities like NetBios Name , as reporter said my named PC was unknown with the option on, and or/smb1.

Anyway may or may not give extra clues as to what is happening with Jasmine’s setup.