Accessing WindowsXP share from Omniclient

I always have problems doing this.

I’ve set up a shared directory on my windows xp machine called “rpi”, with no password. The Windows machine’s IP address is 192.168.2.53.

I can access it from a Linux box using:

I can ping the windows box from my Iyonix, but I can’t access the share, using either LanManFS or LanMan98.

From the Iyonix:
*lanman:lmconnect eee 192.168.2.53 rpi
Connection rejected by server

or
*connect98 eee 192.168.2.53 rpi
Session refused (NetBIOS name not present)

What am I doing wrong?

edit – realised my thread topic is misleading – the examples above don’t use Omniclient but I get exactly the same results if I try this through Omniclient’s interface rather than the command line.

Maybe LanMan (LM) Password Hashing is disabled on your WinXP box?
LM is deprecated and prone to password hacking attacks, which is why it has been disabled in Samba for quite some time. While I found no evidence of it being disabled in WinXP by default, there might be some security suite around that disabled it.
Here’s a link that might be of help: http://www.oit.umn.edu/security/tools/lanman-hash/index.htm

Rik: Have you checked that your User name under LM98 is /exactly/ replicated in the WinXP sharing permissions dialogue? (i.e., Guest/Guest or Everyone/Everyone but NOT e.g. Guest/Everyone). I use LanMan98 to connect RPCEmu089/4.02 running on Win7/64 to a WinXP laptop and it works well, as did its predecessor, an Iyonix running 5.17 also using LM98 to connect to the same laptop.

Apologies if this is noise, but I don’t remember ever getting that kind of login to work without a password. ie I always had to give the account a password to be able to connect from RISC OS.

LM98 connects to both WinXP and Win7/64 shared folders on my network here without using passwords, and this was also the case with my Iyo LM98 setup: Local name, Server, Share and User name are the fields in use, Password is left blank, No types is ticked.

LM98 connects to both WinXP and Win7/64 shared folders on my network here without using passwords, and this was also the case with my Iyo LM98 setup: Local name, Server, Share and User name are the fields in use, Password is left blank, No types is ticked.

Either the share was created with no password or you have the Guest account enabled. If you have wireless networking the data in that share is probably more accessile than you would like.

Thanks for the heads-up, but there’s only me and the missus with access to the network, the router is password-protected and the Windows firewall (behind which RPCEmu is presumably running) is in place – I’ve always assumed therefore that password protection for LM98 was redundant. But quite happy to be proved wrong (it wouldn’t be a ‘first’…!).

Thanks for all the suggestions, but I still can’t get the bloody thing working! I think one complication is that the PC has got XP Pro, and the sharing options are different.

Oh well, I’ll report back if I get it working!

Thanks for all the suggestions, but I still can’t get the bloody thing working! I think one complication is that the PC has got XP Pro, and the sharing options are different.

I use XP pro on a couple of machines like that at home – no access to the home version and the machines came from work in the first place (with Pro)

I will work through the settings I used and scribble some notes. IIRC the name resolve is important, not just pointing at the IP.

I’ve always managed to get it working but recently I can’t. I’ve read thousands of webpages, modified thousand of files, looked and looked things over until I got sore eyes.

I’m quite frankly getting sick of it! It’s ALWAYS the same. I can logon to my windows-shares with everything I have in my house (Symbian phones, Android phones and tablets, linux boxes, RPI under kodi etc…) but under RISCOS it bloody never works!

I remember that it was only a matter of setting authentication to plain passwords with that particular HKLM/control/services/lanmanworkstation/parameters on the PC side. And login into the proper workgroup on RISCOS using *lanman and *lmlogon WORKGROUP user-name pass.

I recently saw that RISCOS doesn’t supply the proper username when there’s a space in it. It used to work using "" thus LMlogon HOME “User X” user123
But LMinfo shows that only the part before the X is used. The same with LMconnect. I can’t seem to properly log on to my server or workgroup anymore. It either puts everything in caps (while usernames are mixed letters) or only uses the part before the space. Nonetheless the shares are shown on the iconbar. I can even see how much free storage I have but when I try to open their main directory I always get Access Denied. Now here’s the funny thing. I can PRINT from RISCOS to my omniclient connected printer perfectly!?!?!?! WTF!
(Ooh BTW, why isn’t the PDumperPCL module NOT supplied while the PCL-Duplex PDF IS supplied which actually NEEDS that module! Either put a readme- in the printers-folder to make people aware that some modules are not supplied or supply the damn thing)

I’m completely out of ideas. I am about to format that RISCOS crap and go Raspian on it (or use that Pi as a doorstop/coffee-heater/desk-ornament). It’s ridiculous why such a trivial thing on ANY other non-windows platform has become so easy to do but so goddamn hard on RISCOS! Isn’t RISCOS supposed to be the userfriendly OS?

Oh, I apologize in advance IF I accidentally step on peoples toes using my bold tone of writing and grammatically incorrect English. I’m not a native English speaker/writer nor very patient! Thanks in advance for the people who knows WTH I did wrong this time!

I use a RPI Model B using RISCOS 5.19, Printers 1.77, Omniclient 2.17, LanManFS-module 2.38. PC and RPI are connected with cabled connections through a Level-One router/ADSL2-modem (WBR6600). My Windows box(Windows 7 ultimate 32-bits) has its internal firewall disabled.

I’m completely out of ideas. I am about to format that RISCOS crap and go Raspian on it (or use that Pi as a doorstop/coffee-heater/desk-ornament). It’s ridiculous why such a trivial thing on ANY other non-windows platform has become so easy to do but so goddamn hard on RISCOS! Isn’t RISCOS supposed to be the userfriendly OS?

Oh, I apologize in advance IF I accidentally step on peoples toes using my bold tone of writing and grammatically incorrect English. I’m not a native English speaker/writer nor very patient! Thanks in advance for the people who knows WTH I did wrong this time!

Manu – find a brown paper bag and breathe gently and regularly in and out into it.

When you are finally calm, just sleep. You know you want to!

When you awake, there may be some guidance available.

Not, I’m afraid, from me – as I don’t use the spawn of the devil – but …

PS. if so agitated, WTH should be WTF (for emphasis!).

Firstly – the English is just fine.

I recently saw that RISCOS doesn’t supply the proper username when there’s a space in it. It used to work using "" thus LMlogon HOME “User X” user123

As a Unix colleague at work would point out “spaces are delimiters” not part of a name (of a file or anything else)

Now here’s the funny thing. I can PRINT from RISCOS to my omniclient connected printer perfectly!?!?!?! WTF!

Print shares have different security.

BTW. There is a test build with improved LanmanFS done by Colin check the thread here it apparently works with the standard encryption in Windows 8

Hope that helps.

There is a test build with improved LanmanFS done by Colin check the thread here it apparently works with the standard encryption in Windows 8

Which reminds me, while it is understandable that the USB and LanManFS changes might not have been able to be included in v5.21 (and hence v5.22 stable) perhaps someone from ROOL could put the changes into a build of 5.23 sometime soon so that they get a thorough thrashing by all the users of the nightly builds and thus 5.24 stable will be usable for accessing file shares on recent Windows builds.

Hi Manu, the “LanManFS is hopelessly out of date”-problem has recently been tackled by Colin, but it is not yet available from ROOL. Before that, the answer was “buy LanMan98” – you might remember that from the similar “DOSFS is hopelessly out of date”-problem, which could be solved by “buy Win95FS”.

The PCL-Duplex problem is indeed strange, no idea why PDumperPCL is not properly packaged. You can download it here: http://www.gag.de/software/PDumperPCL/

Anyway, I would recommend to update RISC OS and the boot structure – RISC OS 5.19 is now really old and many cool new stuff is available in the most recent versions.

Keep the faith in RISC OS – there has been a lot of good work in the past few years: CDFS now supports Joliet, DOSFS supports long filenames (VFAT), Fat32FS is available for really large USB sticks/hds/sd cards, LanManFS supports long filenames and recent password protocols, the USB stack supports isochronous mode, DHCP is much better than it was, Filecore supports 2k and 4k sectors natively, NetSurf gets better every day, ADFFS brings back the old games, and maybe we even get a nice shiny WebKit port soon. Add to that the shiny new hardware (RPi 2, ARMX6, IGEPv5) which is so powerful and still cheap – compare the current situation to the situation 10 years ago and you just can’t stop smiling.

Rik.

Use the remote computers name not the number. I don’t think you should have problems connecting to XP.

Manu

Try my PiRom from the omap4 network thread it connects no problem to Windows 8.1 pro. Hopefully the change will be added to RISC OS soon.