Session refused (NETBios name not present)

Computers don’t you just love them. I’ve been using Lanman98 no problems for a while now and this morning it doesn’t work – I get the error ‘Session refused (NETBios name not present)’. It’s not a servername problem – you get a different error with the wrong servername and I get the same error with the ip address. It’s not a password problem – I tried a disabling passwords on my laptop. The share name is ok it’s not a case sensitivity issue. Its not something I’ve done to my riscos machines I get the same error on all of them and using the 5.18 rom on the iyonix.

I haven’t changes my windows 8 laptop and can access the shared folders with my ipad.

So I’ve changed nothing and now it doesn’t work. Makes no sense to me.

Anyone any ideas?

How unbelievably annoying! I sympathise, I really do. I once had a problem trying to get my a9home (RO 4.42, LanMan98 1.22) to talk to an XP machine (Home edition, SP2). I tried:

• DHCP & static IP with both the A9 and the Windows laptop
• Adding rules to the Windows Firewall, and turning off Windows Firewall entirely
• Registry entry for plain text passwords
• Registry entry for LanMan level access
• Connecting with or without usernames / passwords
• Enabling / Disabling the guest account

Nothing worked. Eventually I went through the Windows Network Setup wizard (which I normally never use), entered all the same details as I had originally entered, and it started to work! I still have no idea what it did that I didn’t.

So, that’s no help to you whatsoever, but I share in your pain. Good luck.

It turns out it was caused by a ‘security’ update on my laptop. Uninstalling the updates from this morning made lanman98 work again. It’s a battle of wills at the moment my laptop has currently decided to reinstall the updates I uninstalled and add a few more for luck. Hopefully the ‘few more’ will fix the problem :-)

Nothing worked. Eventually I went through the Windows Network Setup wizard (which I normally never use), entered all the same details as I had originally entered, and it started to work! I still have no idea what it did that I didn’t.

On that kind of thing I have, in the past, run a registry examination tool before and after and used the compare function. Then you know which registry elements it mucks about with that are undocumented.

Phew! The latest updates fixed the problem with this mornings updates so everything is working normally. Thanks Microsoft for an educational morning.

Thanks Microsoft for an educational morning

Cause of most of the “network” problems that keep me in employment and my mortgage paid…