Network browsers no longer displaying other T2s IP address.

Chrilynn2 · Post by **Chrilynn2** » Fri Aug 20, 2021 20:46

I have two T2s. After recent issues with one I had both working well.
I have the latest beta firmware installed.
Both connected fully to my network, and the internet.
They were talking to each other, and sharing files fine.
One T2 is wired to the modem.
The other through a WiFi extender, to which it is wired.
All was well until a recent power outage.
After the power came back, both T2s successfully rebooted, and reconnected to the network, and internet.
Unfortunately, I now have a significant problem.
Although both T2s are connected to the network, they cannot see each other.
Neither shows up on the other’s network browser, and therefore cannot mount a share, after several rescans.
I cannot see what has changed, since the power out.
They can both see my NAS, and read the files, but they can’t see each other.
I can’t think which settings may not have reset correctly, but They cannot access each other’s files.
Could anyone offer any advice, or suggestion relating to this problem.
Thank you in advance.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Aug 20, 2021 21:00

Did their IP addresses change after the power outage?

Chrilynn2 · Post by **Chrilynn2** » Fri Aug 20, 2021 21:13

Yes they did.

Chrilynn2 · Post by **Chrilynn2** » Fri Aug 20, 2021 21:36

Not sure if it’s relevant but in menu settings for network:
SAMBA. Shows enabled, running:
FTP. Shows enabled, running:
NFS, Shows disabled, stopped.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Aug 20, 2021 22:04

Chrilynn2 wrote: ↑
Fri Aug 20, 2021 21:13
Yes they did.

And what are they?

MrQuade · Post by **MrQuade** » Fri Aug 20, 2021 22:04

Chrilynn2 wrote: ↑
Fri Aug 20, 2021 21:13
Yes they did.

Network mounts are done via the IP address.

Since the addresses of the T2s changed, you will need to re-create the mounts on each.

To save this happening again, set a fixed IP address in the T2s either via a static assignment in the T2 Network settings, or you can configure your router to always give the T2s the same address (one of your choosing).

Chrilynn2 · Post by **Chrilynn2** » Fri Aug 20, 2021 22:23

Sorry Grumpy_Geoff, I thought you were just establishing that they had changed, not what they had changed too.
The T2 wired to the modem is:
192.168.1.118,
The T2 wired to the WiFi extender is:
192.168.1.110.
Neither of these shows up on the other’s Network Browser.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Aug 20, 2021 22:29

If you delete the mount, reboot, rescan, does this change things?
The Mount definition is held in /etc/auto.network file.

peteru · Post by **peteru** » Fri Aug 20, 2021 23:33

The problem is with your network infrastructure. If your DHCP server assigns a different IP, the old mount definitions on your Beyonwizes will become invalid. You need to instruct your DHCP server to always assign the same IP address to each device. Usually this can be done by associating a specific MAC (hardware) address with an IP address.

Once you have fixed this DHCP issue, delete all network mounts on each of your Beyonwizes and then reboot them. After the reboot, create new mounts on each of your Beyonwizes. After that, all should be good. Your network will reliably reassign the same IP addresses, even after unexpected outages, and your mounts will remain valid.

P.S. - The deletion of mounts and reboots are important. Just changing the mounts can lead to issues as there are some edge cases that cause problems.

MrQuade · Post by **MrQuade** » Fri Aug 20, 2021 23:35

Chrilynn2 wrote: ↑
Fri Aug 20, 2021 22:23
Neither of these shows up on the other’s Network Browser.

Ahh sorry, I missed that bit somehow.

If you telnet/SSH into the T2s can they ping eachother?

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 00:34

Thanks peteru, Mr Quade.
I need to process some of the information in the responses above but, does all this mean that the new T2 IP addresses will not show up in a Network Browser scan?

MrQuade · Post by **MrQuade** » Sat Aug 21, 2021 01:30

Chrilynn2 wrote: ↑
Sat Aug 21, 2021 00:34
Thanks peteru, Mr Quade.
I need to process some of the information in the responses above but, does all this mean that the new T2 IP addresses will not show up in a Network Browser scan?

No, the browser scan should find them as long as they are on the same network subnet no matter if the IP changed or not. This is a bit odd.

The ping test that I mentioned should verify if the two T2's can see each-other on the network at a basic level. If the pings don't work then there is something screwy on your network. If the pings work, and the Network browser is still not working, then the problem is related to the T2s somehow, though I am at a loss to think what that could be.

The scan doesn't throw up an error does it? It finds your NAS, and just doesn't find the other T2?
You've used the YELLOW rescan button when you say you say you have done several scans?

Have you rebooted the T2s again (one at a time) to see if that helps?

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 17:50

I have tried to address some of the issues, and suggestions with mixed results.
Firstly, I deleted all the mounts in, using Mount points Management.
I did a reboot of the T2s ( I realised I had not done a manual reboot on one of them after the forced power out reboot).
A rescan in Network Browser ( yellow button) successfully showed each T2s IP address this time.
I attempted to mount each T2 by expanding the IP, and saving.
It appeared to work but I got an error message when I attempted to access the files in media.
“Directory ‘/media/autofs/1921681118/_Movie/‘does not exist.”
With regard to setting a static IP as a separate issue, I’m not quite sure what the steps are in the T2s menus.
I couldn’t work out how to ping the T2s in SSH, but I can see them in my modem dashboard, and ping them in a third party network app.
Do I need to enable the NFS option in the network menu? This seems to be the only option not enabled and running ( SAMBA, and FTP, are enabled).
Sadly, my technical understanding goes just so far, but I am happy to try all options if I can see a clear path.
Thank you, as ever, for your ongoing interest.

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 17:54

By the way MrQuade, using the yellow rescan button does not throw up an error.
( I have been unable to set up, and use, SSH on my Windows 10 laptop)

prl · Post by **prl** » Sat Aug 21, 2021 17:57

Chrilynn2 wrote: ↑
Sat Aug 21, 2021 17:50
Do I need to enable the NFS option in the network menu?

That enables the PVRs as NFS servers. There's no mechanism to configure the NFS servers to do anything useful without using the T2's command-line interface, and they're only of any use if you have devices that can be NFS clients.

tl;dr: No.

MrQuade · Post by **MrQuade** » Sat Aug 21, 2021 17:58

It sounds like a simple reboot has fixed the immediate issue.

The ping test is no longer necessary as the two T2s can now see each other. Pinging from a separate device would not have been a valid test since we were trying to establish if the T2s could ping each other.

As for a static address, all you need to do is go into the network setup menu and disable the DHCP option for getting an Automatic address. You can then manually plug in the address, subnet and gateway info. Better to do that in the router, however that does require extra steps and those steps depend on what sort of router you have.

The NFS option is not required. Thats for an entirely different file sharing protocol.

As for the "does not exist" error, this is telling us that the mount has not completed successfully for some reason.

Thats going to need a bit more digging.

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 17:59

I found the “ /etc/auto.network file” but could not read it on the T2 ( is there a plug-in, or do I need to copy it and read it externally?).

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 18:06

Thanks for the updates Peter, and MrQuade.
Is there a step by step process for mounting shares?
I may be doing it wrong, but I was successful previously, before the power outage.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sat Aug 21, 2021 18:17

So that's on the T2 connected to the wireless extender I take it?
Please show the contents of the /etc/auto.network file from that T2.
You can download it using a browser with - http://192.168.1.110/file?file=/etc/auto.network

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 21:56

It is that T2 Grumpy_Geoff.
The download I get is:
Auto.network
Document
954 bytes
Presumably I have not done this correctly

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sat Aug 21, 2021 22:14

Chrilynn2 wrote: ↑
Sat Aug 21, 2021 21:56
Presumably I have not done this correctly

Your browser should've downloaded the file, or ask you where to download it to.

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 22:49

I have initiated the download several times.
After the download the option is open in.
I’ve tried downloads, notes, and save to files.
When I try to import the file as an attachment to this , it is not selectable.
Do not get an option to download it to.

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 22:50

I have initiated the download several times.
After the download the option is open in.
I’ve tried downloads, notes, and save to files.
When I try to import the file as an attachment to this , it is not selectable.
Do not get an option to download it to.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sat Aug 21, 2021 23:10

Chrilynn2 wrote: ↑
Sat Aug 21, 2021 22:49
I have initiated the download several times.

View it on the T2 using File Commander, then take a screenshot.

Chrilynn2 · Post by **Chrilynn2** » Sat Aug 21, 2021 23:43

I just get an an error message:
“No viewer installed for this file type:auto.network”

Chrilynn2 · Post by **Chrilynn2** » Sun Aug 22, 2021 00:43

# automounter configuration
-fstype=cifs,user=,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.118/
1921681107_SmartWare -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/SmartWare
1921681107_Public -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/Public
1921681107_nfs -fstype=nfs,rw,nolock,tcp,nfsvers=3,rsize=8192,wsize=8192,timeo=14,soft 192.168.1.107:/nfs
1921681118_Logs -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.118/Logs
1921681107_External_HDD -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/External_HDD
1921681118_Movie -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.118/Movie
1921681107_Chris -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/Chris
1921681107_TimeMachineBackup -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/TimeMachineBackup

finally managed to download the file on my laptop, and view it on wordpad.
hope this helps.
192.168.1.118 is the current IP for the other T2, which is the one I am trying to mount.
107 is my NAS.

MrQuade · Post by **MrQuade** » Sun Aug 22, 2021 02:47

So the first mount is missing a name, which doesn't seem good.

And you have entries there for every share on your NAS which look to be unnecessary too.
Do those mounts actually show up in your T2's mount manager?

You should probably delete that mount to the T2 and recreate it. It should have a name.

Chrilynn2 · Post by **Chrilynn2** » Sun Aug 22, 2021 12:12

Hi MrQuade, thanks for your input.
I did delete the mounts before remounting them, after a reboot.
I did mount all the items on the expanded view of my NAS. I wasn’t sure if that was a requirement ( network browser scan).
I will reduce that to the ones with files.
No idea why the first item , which has the IP address of my other T2, has no name. Presumably it should show “movie”.
I don’t rename them when I mount , and save, them.
Is the mount procedure:
Menu, network, network browser, rescan, click ok to expand, click required item, save?(ignoring the name/password option).
At some point after the procedure, something goes wrong when I try to access the files in media, and I get the error message.
Is there a plug-in to read the auto.network files on the T2.
I just get a message that there is no viewer.
Cheers
Chris

Chrilynn2 · Post by **Chrilynn2** » Sun Aug 22, 2021 12:18

this is the auto.network file from the other T2:

# automounter configuration
1921681107_Public -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/Public
1921681107_Chris -fstype=cifs,user=,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/Chris
1921681107_SmartWare -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.107/SmartWare
1921681110_Movie -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.110/Movie

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Aug 23, 2021 15:35

Chrilynn2 wrote: ↑
Sun Aug 22, 2021 12:12
Is there a plug-in to read the auto.network files on the T2.
I just get a message that there is no viewer.

Press TEXT in File Commander.

What names have you given each T2. I'm just wondering why the "server" component of the local share name is the numbers from the server's IP address?

MrQuade · Post by **MrQuade** » Mon Aug 23, 2021 15:42

Grumpy_Geoff wrote: ↑
Mon Aug 23, 2021 15:35
What names have you given each T2. I'm just wondering why the "server" component of the local share name is the numbers from the server's IP address?

Maybe the LAN devices are not using the local DNS server to resolve addresses, but rather using the ISP, or some other third party DNS (kiddy filter?).

Chrilynn2 · Post by **Chrilynn2** » Mon Aug 23, 2021 16:53

Hi Grumpy_Geoff, thanks for coming back, and thanks for the tip for reading the file, worked perfectly.
Attached is the latest screen dump of the auto.network file.
Interestingly, I deleted all mounts, and mounted only the public, and Chris, of my NAS (192,168.1.107), plus the other T2 movie, which doesn’t show here (192.168.1.112).
118 was the old IP address of the other T2 before I updated firmware, and rebooted.
I have done mounts and deletes, and reboots, a number of times ( I’ve now got the IP addresses static).
The network browser rescans are now showing each T2 fine, and I have used these to mount them but they still
show an error when trying to assess them through media, location.
The correct ones show up in mount manager.
When I look at media, location, some of the listed items are the old deleted mounts?
I am still processing MrQuade’s comments.

Chrilynn2 · Post by **Chrilynn2** » Mon Aug 23, 2021 17:23

I don’t really understand the issues with DNS/ISP but I do not have any parental controls set.
These issues only came about since the power outage, everything else is as it was, before that, other than resetting IP addresses.
I have never manually set names.
All the mounts were just auto settings.
All the defunct mount information seems to be carryover, despite deleting mounts.
Maybe I am not following the correct procedure for mounting, I can’t find a procedure sequence anywhere.

MrQuade · Post by **MrQuade** » Mon Aug 23, 2021 17:55

Chrilynn2 wrote: ↑
Mon Aug 23, 2021 17:23
I don’t really understand the issues with DNS/ISP but I do not have any parental controls set.

No worries.
My speculation was that perhaps your T2 is not using your router as its DNS server.
Can you check your network settings and tell us what the following details are for your T2:
IP Address
Subnet Mask
Gateway Address
DNS Server address

(The last two will often, and in your case, ideally be the same).

One thing though, when you perform a scan in the network browser, so you just see a list of IP addresses, or do you see the device names, eg. "beyonwizt2"? You *should* see the names of the devices.

Also, you can take screenshots of your Wiz screen more easily via the T2's web interface. You can control the T2 from your PC's web browser and save a screenshot at any point without needing to use a camera.

Chrilynn2 · Post by **Chrilynn2** » Mon Aug 23, 2021 19:04

Hi MrQuade.
My network browser just lists the IP addresses:

Here is the wiz screenshot of the network settings
.

Chrilynn2 · Post by **Chrilynn2** » Mon Aug 23, 2021 19:17

Network Browser

MrQuade · Post by **MrQuade** » Mon Aug 23, 2021 19:42

Chrilynn2 wrote: ↑
Mon Aug 23, 2021 19:04
Here is the wiz screenshot of the network settings

Thanks for that, and good work on the screenshots

It looks like your router might be handing out those IP address strings instead of the proper DNS names, or else it is not providing any names at all, and the Wiz is just filling in as best it can.

The list should look more like this one:

Either way, that explains the odd names being assigned in the automount file.

Does your router have an option that looks like "Forward local domain queries to upstream DNS" or similar (That's what it is called on my Asus router). If so, then you most likely want to turn that option off.

All of that aside, it shouldn't stop the mount from working.

It does look as if there is some leftover stuff in your automounts file which may be causing issues. However, I am not really up to speed on configuring automount let alone how it interacts with the Beyonwiz mount definitions. I don't really know what might or might need cleaning up or repairing

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Aug 23, 2021 19:53

I think you should give each T2 a unique name - MENU>>Setup>>Network>>Mount manager>>Change hostname.
Then use File Commander to rename /etc/auto.network and /etc/enigma2/automounts.xml to start afresh with new mount definitions.
Then reboot and run the network browser again.

Chrilynn2 · Post by **Chrilynn2** » Mon Aug 23, 2021 22:30

Wow, thanks guys.
Looks like a bit of think time.
Will review all, and report back.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 09:59

It never rains but it pours.
I switched on the T2 to check, and update the suggestions by Grumpy_Geoff and there was a new online software update message,
so I ran that first.
All went well until the splash screen came on.
It’s now been 30 minutes, and the screen is still up, interspersed with periods of a black screen for a few minutes.
Currently it’s the blue, bubbles, Wizos screen.
Either this is a particularly long update, or something’s gone wrong.
It’s now blacked out again.

Hopefully it’s not a problem, and/or it doesn’t do it for you.
I signed up for the beta auto updates, and the previous 2 updates worked fine.
By the way MrQuade, I couldn’t find those router settings on my TpLink /Archer VR1600v , dashboard, or manual.
Not sure what the equivalent would be, or if it has them.

MrQuade · Post by **MrQuade** » Tue Aug 24, 2021 10:36

Chrilynn2 wrote: ↑
Tue Aug 24, 2021 09:59
It’s now been 30 minutes, and the screen is still up, interspersed with periods of a black screen for a few minutes.
Currently it’s the blue, bubbles, Wizos screen.

The boot time after an update shouldn't take much longer than a normal boot (a few extra seconds at most).

Chrilynn2 wrote: ↑
Tue Aug 24, 2021 09:59
Hopefully it’s not a problem, and/or it doesn’t do it for you.
I signed up for the beta auto updates, and the previous 2 updates worked fine.

The latest update is the first one that is using a new update method, and if you did not perform some specific manual steps after the last update, it might be that this new update broke something for you.

Best bet is to download the latest beta USB image and just re-install from USB. You can then safely restore your settings in the setup wizard and you will be back up and working.

Chrilynn2 wrote: ↑
Tue Aug 24, 2021 09:59
By the way MrQuade, I couldn’t find those router settings on my TpLink /Archer VR1600v , dashboard, or manual.
Not sure what the equivalent would be, or if it has them.

No worries. I had a quick look at the manual for that router, and couldn't see any such setting either.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 10:57

Thanks MrQuade.
The T2 still hasn’t finalised.
I’ve still got the blue splash screen, interspersed with a black screen.
It’s been over an hour since I started it.
I did the beta firmware update, and installed the online update script, as per beta update instructions.
At the time I did it there was an immediate online update, which worked successfully.
There was another on Saturday night, which was also successful
This new one had 35 components, which also seemed to work ok, and I got the reboot message.
This seemed to work ok, until it got stuck on the blue splash screen/black screen loop.
I believe that if you have to reflash the beta firmware again from USB, you also have to reinstall the online update script.
I am a bit loath to switch on the other T2, and run the update, until I know all is well.
Still showing the blue screen, after nearly 1.5 hours!

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 11:01

PS,
I think it’s safe to say something has gone wrong,so, I might just try a shutdown, reboot first, to see what happens?

MrQuade · Post by **MrQuade** » Tue Aug 24, 2021 11:04

Chrilynn2 wrote: ↑
Tue Aug 24, 2021 10:57
I believe that if you have to reflash the beta firmware again from USB, you also have to reinstall the online update script.
I am a bit loath to switch on the other T2, and run the update, until I know all is well.

Correct. However, you want to download the NEW USB update file. Don't use the one you downloaded previously.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 11:22

Thanks, I just checked the beta forum feed, and can see the update.
Interestingly it was dated Sat.
I got the online update Saturday night, which seemed to work ok.
Clearly this mornings didn’t.
I’ll do the full download, after checking with a reboot.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 11:36

I just did a reboot.
All I got was the initial start up screen, and now it's gone black.
I am doing a download of the new firmware, to install from USB.
Fingers crossed.

peteru · Post by **peteru** » Tue Aug 24, 2021 11:56

When it goes black, press the OK button on the remote. If you get the infobar, it just means you are not tuned to any service. If that is the case, press the MENU button and rescan to get a new set of services.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 12:02

Just to confirm, all I got on reboot was the initial screen, blue bubbles screen, and occasionally a black screen.
Just about to start a USB update.

Chrilynn2 · Post by **Chrilynn2** » Tue Aug 24, 2021 12:04

Oops, just seen peteru’s message.
I’ll try that first.

About the Forum

Join us