!Omni

When mounting my NAS drive, it randomly doesn’t connect.
Since the latest updates to 5.21 and disc image, it rarely connects. (pandaboard ES)
Lan Manager 2.42 (04-Oct-13)
Sometimes I get “Cannot find given server” when it can see the NAS server and the folders inside it and attempt to Connect.
This is on a saved share that used to work….
Other times I get a “Message from OmniClient” saying “Network driver is not DCI-4 compatible”.
Also generally when it is connecting the hourglass appears for either a second or two or for minutes if it is having problems.
Would it be possible not to block on the initial connect, as it is frustrating.

Now it’s randomly working again, most bizarre behaviour – is there some windows compatibility pack in there somewhere ;-)

On A Raspberry Pi with OmniClient 2.18 and Lan Manager 2.42

Cannot find given server

Calling the server by name only or a mis-spelled password gets that error here. I can connect to my NAS, it all seems to work as expected, but the NAS has a fixed IP, and must be called by IP number or there must be an entry in the Hosts file.

No such luck trying to connect to two Windows 7 PCs, “Already connected to this drive on this server”. it says!

Network driver is not DCI-4 compatible

Got that one on attempting to connect to the Mac. I have not been able to connect to the Mac since apple rolled its own Samba.

Well I’ve ordered a book on cifs….guess that’s my next project

There’s an element of error message obfuscation here because the author has assumed in a couple of places that the only possible cause of a duff connection is X when there’s also Y and Z to consider.

“Already connected to this drive on this server” = NetBIOS session was refused, you probably haven’t got NetBIOS enabled on the Windows end.
“Network driver is not DCI-4 compatible” = Couldn’t open a socket to that server, your network might be flakey, or the machine at the other end might not accept requests from your IP address.

The configure setting LMNameServer is worth a look. I have a reasonably simple network here so I just point that at the PC since I know it’ll always win the name server browser election. If you have several PCs it could be that that one isn’t online or it lost a browser election. Browser elections are worth reading up on, they’re a nightmare – for institutions with more than 2 PCs you probably want DNS.

Well, I can confirm that the networking isn’t flakey – unless its the pandaboard and it only affects Omni and nothing else.
I’ve deliberately simplified my network recently, there isn’t anything much to go wrong now.
It’s not down to elections as there is only one that is in the election (the NAS).

The issues just aren’t repeatable from any other client, ever.
Android, windows or linux all connect first time, reliably.

I suspect Omni is knackering the networking somewhere – that I have found isn’t difficult.

unless its the pandaboard and it only affects Omni and nothing else

By “nothing else”, do you mean other RISC OS software, or other operating systems?

It’s not down to elections

That still leaves love and chocolate. ;-) {*}

I suspect Omni is knackering the networking somewhere

Do you have any sort of network tracing or traffic dumping software that will allow you to look in at what is actually happening on the network?

When you say the NAS doesn’t connect / knackers the network, is this affecting all of the machines, or only the RISC OS one?

By “nothing else” I mean other RISC OS software and other operating systems.

As long as it’s treacle toffee…mmmmm

Yeah I can put a bridge in I suppose and get a tcp dump, I may need another NIC in my desktop – I’ll have to check.

Ah sorry! What I mean’t by “knackers the network”, I meant the RISC OS network stack.
That was as clear as mud!

There is the third option, that’s I’ve knackered my RISC OS setup…and quite a possibility, it’s weird it just affects omni though.
I’ll recheck my setup.