Nightmare on Network Street

[Altimes]

Short story. Cannot reliably gain cross access between U4 and T4. Both wired. Symptons, select MovieBeyonWiz[TU]4 after pressing yellow Location from media list, spinner for a few seconds followed by "Directory '/media/autofs/MovieBeyonWiz[TU]4/' does not exist" error popup. Problem exists in both directions (hence the [TU] bit).

Long story. Acquired a Synology NAS to act as alway on file server, backup repository, video store, etc, etc. Blundering my way through setup of it, a few false steps but getting there. OK, read some notes that advise that M$ have deprecated SMBv1 and that we should all be turning it off. OK, located appropriate section on the the NAS and set the lowest SMB to be V2. Sometime later, one of the household Win10 systems couldn't see the bits of the network (ie net view came back with system error 1231....), later still Wizen start giving out the same message about the NAS as they are about each other.

OK, so putting the NAS SMB to a minimum of V2 wasn't the only "tidying up" that I had been doing that day...... So, the cause and effect were not quite so close together.

So, I started investigating what I had stuffed up and finally got back to letting the NAS do SMB1 and the (critical) Wizen access has been restored.

During the investigation I started looking for utilities to help diagnose the problem. I found smbclient on the Wizen and smbutil on the Mac that do similar things.

On the T4 I get:

Code: Select all

root@beyonwizt4:/mnt/autofs# smbclient -N -L beyonwizu4

	Sharename       Type      Comment
	---------       ----      -------
	Movie           Disk      /hdd/movie
	IPC$            IPC       IPC Service (beyonwizu4 Samba server)

	Server               Comment
	---------            -------

	Workgroup            Master
	---------            -------
	WORKGROUP            NAS
root@beyonwizt4:/mnt/autofs# ls /mnt/autofs/MovieBEYONWIZU4/
ls: /mnt/autofs/MovieBEYONWIZU4/: No such file or directory

Surprisingly, to me anyway, it takes about 6 seconds to display the share list and then another 6 seconds to complete the master browser info.

Also, note that subsequent of the smbclient saying all OK, the ls of the autofs directory is failing.....

The Mac similarly shows:

Code: Select all

Alans-MacBook-Pro:~ alanf$ smbutil view -G -N //BEYONWIZU4
Share                                           Type    Comments
-------------------------------
Movie                                           Disk    /hdd/movie
IPC$                                            Pipe    IPC Service (beyonwizu4 Samba server)

2 shares listed

Now I have completely removed mounts, rebooted and added them back by using the network browser several times.
I have checked the automounts.xml and auto.network files and they look the same to me..... but a second set of eyes would be appreciated.

Code: Select all

root@beyonwizt4:/etc/enigma2# cat automounts.xml
<?xml version="1.0" ?>
<mountmanager>
<autofs>
 <cifs>
  <mount>
   <active>True</active>
   <hdd_replacement>False</hdd_replacement>
   <ip>192.168.1.24</ip>
   <sharename>MovieBEYONWIZU4</sharename>
   <sharedir>Movie</sharedir>
   <options>rw,utf8</options>
   <username></username>
   <password></password>
  </mount>
 </cifs>
</autofs>
<autofs>
 <cifs>
  <mount>
   <active>True</active>
   <hdd_replacement>False</hdd_replacement>
   <ip>192.168.1.30</ip>
   <sharename>WizVideoNAS</sharename>
   <sharedir>WizVideo</sharedir>
   <options>rw,utf8</options>
   <username>blotted</username>
   <password>blotted</password>
  </mount>
 </cifs>
</autofs>
</mountmanager>

Code: Select all

root@beyonwizt4:/etc# cat auto.network 
# automounter configuration
MovieBEYONWIZU4 -fstype=cifs,user=,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.24/Movie
WizVideoNAS -fstype=cifs,user=blotted,pass=blotted,rw,iocharset=utf8,cache=loose ://192.168.1.30/WizVideo

So if anyone can throw any light on why the two Wizen are not talking to each other it would be much appreciated.

Curiously, in getting the firmware details from Webif I just noticed

Code: Select all

MovieBEYONWIZT4:	SMBv1.0 using autofs: //192.168.1.20/Movie (192.168.1.20)
WizVideoNAS:	SMBv1.0 using autofs: //192.168.1.30/WizVideo (192.168.1.30)

So it would seem the Wizen are explicitly using the deprecated SMBv1.0....

T4:
System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190207 (17.5-819-gdd3f1fa)
Kernel / Drivers: 3.14.2 / 20180416

U4:
System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190207 (17.5-819-gdd3f1fa)
Kernel / Drivers: 4.9.51 / 180411-16.4

[Grumpy_Geoff]

Code: Select all

root@beyonwizt4:/etc# cat auto.network 
# automounter configuration
MovieBEYONWIZU4 -fstype=cifs,user=,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.24/Movie
WizVideoNAS -fstype=cifs,user=blotted,pass=blotted,rw,iocharset=utf8,cache=loose ://192.168.1.30/WizVideo

My U4 and T4 have user of 'guest'
user=guest
<username>guest</username>
e.g.
From T4:

Code: Select all

U4 -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.64/Movie
MovieBEYONWIZT2 -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.63/Movie

From U4:

Code: Select all

MovieBEYONWIZT4 -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.62/Movie
Movie_T2 -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.63/Movie

[Altimes]

Thanks GG,

I added in guest with no password, sadly no positive effect. I seem to be completely unable to cross reference the two Wizen (completely broken is better than intermittent ), although both can now reference the NAS, so one step forward.

Looking around in enigma2, on the U4, I notice a number of .cache files does anyone know if they can be deleted with impunity ? Do not want to make things worse if I can avoid it....

Code: Select all

root@beyonwizu4:/etc/enigma2# ls -sal *.cache
     4 -rw-r--r--    1 root     root            41 Jul  3 16:11 BEYONWIZT4.cache
     4 -rw-r--r--    1 root     root            48 Jan  9 15:30 FOA-WK5.cache
     4 -rw-r--r--    1 root     root            48 Jan  9 15:37 FOA-WK8.cache
     4 -rw-r--r--    1 root     root            47 Jun 14 15:59 NAS.cache
     4 -rw-r--r--    1 root     root           806 Jul  1 22:22 networkbrowser.cache

They seem to contain, at least, some username password information for the corresponding systems.

Some of them date from some time before I created my network woes. I wonder if it somehow referencing stale information ?

Alan.

[Altimes]

I have done some more investigation and I am getting a little more information. Following a suggestion found on the net, I killed the automount daemon and restarted it as a verbose foreground process.

That showed the failure

Code: Select all

mount(generic): failed to mount //192.168.1.24/Movie (type cifs) on /media/autofs/MovieBEYONWIZU4
failed to mount /media/autofs/MovieBEYONWIZU4
re-reading map for /media/autofs

Which at least shows that the automount is trying and failing if not why.

I then manually mounted the U4 share

Code: Select all

root@beyonwizt4:~# cd /mnt
root@beyonwizt4:/mnt# mkdir u4
root@beyonwizt4:/mnt# mount -t cifs -o user=guest //192.168.1.24/Movie /mnt/u4
root@beyonwizt4:/mnt# cd /mnt/u4

Which succeeded without complaint and listing the directory confirmed its success. Now trying the automount from the WIZ GUI gave

Code: Select all

attempting to mount entry /media/autofs/MovieBEYONWIZU4
mounted /media/autofs/MovieBEYONWIZU4
re-reading map for /media/autofs
1 remaining in /media/autofs
1 remaining in /media/autofs
1 remaining in /media/autofs
expiring path /media/autofs/MovieBEYONWIZU4
expired /media/autofs/MovieBEYONWIZU4

Now there is no reference to a "mount (generic)"

I am now confused, manual mount is just fine and then automount succeeds. Anyone have any ideas ?

Reflash and start again?

Alan