Unable to connect my T4 to the internet

[Robert_M]

I am no longer able to connect T4 to the internet and then iceTV
Error messages, in part:
I get a login failure: The IceTV server cannot be reached
Max retries exceeded with url: /login?api key=<long string of characters>
ConnectTimeoutError

Recent info, no changes to connections at home.
Using V17 software, would upgrading to V19 be helpful, though sceptical.
Network test 4 from 5 green ticks but IP Address is red and unconfirmed!
Auto DHCP
Have moved the T4 via a short cable to the modem and no change
Do not have WiFi dongle to test what I suspect is the T4’s network functionality failure

Anybody, any clues,
many thanks in advance, Robert

[raymondjpg]

Auto DHCP
Have moved the T4 via a short cable to the modem and no change
Do not have WiFi dongle to test what I suspect is the T4’s network functionality failure

Anybody, any clues,

Is it possible that you have a conflict with 10.1.1.4 assigned to some other device in the LAN?

I would try rebooting the router that assigns the DHCP addresses. It appears that would be the modem that you talk about. If there is no provision to reboot the router via a GUI then power it off for 30 seconds then power on again.

[MrQuade]

I don't think it will help this particular issue, but you should update to 19.3 regardless.


The issue is a strange one indeed.

As raymondjpg says, a router reboot would be a good first step.

I'd use your PC and see if you can ping the Wiz.

try
ping 10.1.1.4

also try
ping beyonwizt4

the second one will attempt to resolve the IP address from its DNS name, which should tell us what the router thinks the Wiz's address is.

[prl]

This discussion continues from a topic in the IceTV forum (as everyone seems to agree that the problem has nothing to do with the IceTV servers).

Please post here rather than on the IceTV forum to keep the discussion in the one place as much as possible.

[prl]

Hi, Robert.

Thanks for posting the screenshot of the MENU>Information>Network screens. That confirms what I thought - your T4 seems to be configuring its network adapter correctly, but it doesn't seem to be able to reach the wider internet.

MrQuade's suggestions are probably the ones to try first. Rebooting the router as raymondjpg suggests may or may not help.

Do you use DHCP to configure all the devices on your home network, or do some have IP addresses assigned by the device itself? If you don't know the answer to the last part of the question, it probably means that the devices are all configured using DHCP. This question is related to the tests that MrQuade has asked you to try.

[Grumpy_Geoff]

try
ping 10.1.1.4

or perhaps a ping -a 10.1.1.4 to see what device name responds.

[Paul_oz53]

Hi, Robert.

Thanks for posting the screenshot of the MENU>Information>Network screens. That confirms what I thought - your T4 seems to be configuring its network adapter correctly, but it doesn't seem to be able to reach the wider internet.

MrQuade's suggestions are probably the ones to try first. Rebooting the router as raymondjpg suggests may or may not help.

Do you use DHCP to configure all the devices on your home network, or do some have IP addresses assigned by the device itself? If you don't know the answer to the last part of the question, it probably means that the devices are all configured using DHCP. This question is related to the tests that MrQuade has asked you to try.

My T4 did something very similar recently. Internal network performance suddenly dropped for no apparent reason to unusable for watching movies on another Wiz and it was unable to access the internet for the online update. A USB update to the 19.3 20200328 did not fix it until I switched off at the power switch and waited a minute or so to reboot it. All is good now.

Strongly recommend the 19.3 update. It has no apparent problems.

[prl]

Yes, a full power cycle may also help. The problem with things like that and the suggested router reboot is that even if they work, we don't know much more about the cause.

[Robert_M]

Thanks everyone for your help,
I'll reply to the correct people, I hope as I'm new to forums

MrQuade: suggestion to upgrade noted, will do anyway in the next day or so, want to try to sort this first.
Pinging. I use a MAC. using Safari I type "ping 10.1.1.4" with no suitable result. using Terminal "ping 10.1.1.4" results with a Request timeout for imp_seq . Further another Terminal ping -a 10.1.1.4 did the same.

raymondjpg: I did previously have reserved IP address of 10.1.1.34 for T4, .32 for DP-P2 and .31 for DPlite but on another suggestion deleted the reservation so auto DHCP now sets to .4 >> I am confident I have no IP clashes happening.
I have rebooted the router but left it off for a ,minute or so, will try that.
I would have picked up the T4 and plugged it into the neighbour's modem and thereby isolated or confirmed the modem's fault level, BUT they are old and have to think about that one

Paul_oz53: thank you for your clue with update suggestion, but was that network connectivity still working just poor streaming from the other machines or it just failed?

PRL: I had turned the T4 off for some time, as mentioned even moving it closer to the modem, still not working.

I wrote to Beyonwiz support last Thursday, have yet to hear back from them, I understand they are somewhat busy at this time.....
But their insights should be good, but not so if the network lack of connectivity means a new main board or upgrade to a U4 etc, money I don't wish to spend now

[MrQuade]

MrQuade: suggestion to upgrade noted, will do anyway in the next day or so, want to try to sort this first.
Pinging. I use a MAC. using Safari I type "ping 10.1.1.4" with no suitable result. using Terminal "ping 10.1.1.4" results with a Request timeout for imp_seq . Further another Terminal ping -a 10.1.1.4 did the same.

Sorry, I usually just default to Windows as being the market majority .

So the lack of response to the ping does reinforce the fact that the T4 doesn't indeed have that IP address.

Did you try "ping beyonwizt4" ?

Mind you, if the T4 *thinks* its address is 10.1.1.4, then it is unlikely to have actually acquired another one via DHCP.


What about the LAN activity LEDs on your Router, and the T4?
Do you get a link LED on the T4? Does the router show something connected to that port?

Since you have already tried a new cable, it is possible that the T4's network port has just pooped itself.


BTW, the U4 is no longer sold, so the only new alternative available is the V2.

[Paul_oz53]

Thanks everyone for your help,
I'll reply to the correct people, I hope as I'm new to forums



Paul_oz53: thank you for your clue with update suggestion, but was that network connectivity still working just poor streaming from the other machines or it just failed?

...
But their insights should be good, but not so if the network lack of connectivity means a new main board or upgrade to a U4 etc, money I don't wish to spend now

I could read the file list on another Wiz but could not play a file. It had ZERO access to the internet for Ice TV. Powering off fixed it. Rebooting did not. It is an easy thing to try so give it a go. I did the USB update first and rebooted but still couldn't connect. Powering off fixed it though.

You will find repairs difficult as no spare mainboards are available - the chipmaker stopped supplying the relevant chips a while ago. Warkus at Decisive Computer Solutions is a recommended repairer. He has a limited stock off spare parts. The U4 is no longer an option. The current model is the V2,

[Grumpy_Geoff]

You will find repairs difficult as no spare mainboards are available - the chipmaker stopped supplying the relevant chips a while ago. Warkus at Decisive Computer Solutions is a recommended repairer. He has a limited stock off spare parts. The U4 is no longer an option. The current model is the V2,

For this network issue, if all of the troubleshooting steps fail, and the end result is that there is no link lights showing on the T4's network port when an ethernet cable is connected to the T4 and router, then I think the quickest and easiest solution is to use a wireless adapter.

[prl]

MrQuade: suggestion to upgrade noted, will do anyway in the next day or so, want to try to sort this first.
Pinging. I use a MAC. using Safari I type "ping 10.1.1.4" with no suitable result. using Terminal "ping 10.1.1.4" results with a Request timeout for imp_seq . Further another Terminal ping -a 10.1.1.4 did the same.

Doing the ping in the MacOS Terminal should give you this (the ^C is Control-C to stop it):

Code: Select all

prl@Xerxes ~ % ping 192.168.178.44
PING 192.168.178.44 (192.168.178.44): 56 data bytes
64 bytes from 192.168.178.44: icmp_seq=0 ttl=64 time=394.994 ms
64 bytes from 192.168.178.44: icmp_seq=1 ttl=64 time=0.683 ms
64 bytes from 192.168.178.44: icmp_seq=2 ttl=64 time=0.688 ms
64 bytes from 192.168.178.44: icmp_seq=3 ttl=64 time=0.779 ms
^C
--- 192.168.178.44 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.683/99.286/394.994/170.727 ms
prl@Xerxes ~ %

192.168.178.44 is my test Beyonwiz U4's IP address on my network. Getting a timeout on ping means that even though it looks like your networking is set up correctly on your T4, there's something wrong in your local network.

PRL: I had turned the T4 off for some time, as mentioned even moving it closer to the modem, still not working.

From the context, I assume that you power-cycled the T4 before you took the screenshot of the MENU>Information>Network?

I wrote to Beyonwiz support last Thursday, have yet to hear back from them, I understand they are somewhat busy at this time.....
But their insights should be good, but not so if the network lack of connectivity means a new main board or upgrade to a U4 etc, money I don't wish to spend now

You'll probably get timelier responses here than from Beyonwiz support. Support may well refer you here

[Paul_oz53]

For this network issue, if all of the troubleshooting steps fail, and the end result is that there is no link lights showing on the T4's network port when an ethernet cable is connected to the T4 and router, then I think the quickest and easiest solution is to use a wireless adapter.

If mine hadn't come good that was my plan. I really thought the lan port had died. I only powered it off as a last desperate measure and was relieved that it came good.

First time I didn't wait for the capacitors to discharge. Rookie mistake.

Since it came good I didn't try the wireless option.

[Robert_M]

Hello again, also thank you,
I don't know how to reply to a single person, so another collective
An extended (20min) power down of both modem and T4 changed nothing, except it's got a new IP, woo hoo 10.1.1.8 !!
How do I do a ping beyonwizt4 on a mac, same as before in Terminal?
I can, but it has to spend some 20 seconds thinking about it, see the contents of Movie folder and even download files from it and as mentioned by someone earlier, this just means the LAN is OK, just not the WAN.
I think I will before this day is out upgrade to v19.3 and see what that does as noted by paul_oz53
A question, MrQuade said that if the T4 "thinks" its address is 10.1.1.4 (now . then it is unlikely to have actually acquired another one via DHCP.
So the question is, how did the T4 get these numbers in the first place?
Also the inquiry about LAN activity LEDs in the router don't flash, the lights at the back of the T4 I had not thought of, what should I expect in a working machine?
I am still in 2 minds whether to knock on next door and connect the T4 to their router for reasons as mentioned before but it would eliminate or confirm modem fault
Then as mentioned the T4 may have pooped itself
I wonder how much a 2nd hand pre-loved T4 (bare bones preferred) or even another DP-P2 would be?

[prl]

So the question is, how did the T4 get these numbers in the first place?

The IP address on the T4 is handed to the T4 by the router as part of DHCP (Dynamic Host Configuration Protocol). The fact that the router has given the T4 a new, different, DHCP address indicates that the network seems to be working at least well enough for DHCP to work.

Also the inquiry about LAN activity LEDs in the router don't flash, the lights at the back of the T4 I had not thought of, what should I expect in a working machine?

When connected at 1Gb/s, the orange LED on right (viewed from behind) side of the clip of the Ethernet cable should flash when there's Ethernet traffic. The green one on the other side just seems to flash regularly. It may indicate connection status.

When you moved the T4 nearer the router to test it, did you use the same Ethernet cable to connect it as you normally use? I.e. have you tried using a different Ethernet cable?

[MrQuade]

An extended (20min) power down of both modem and T4 changed nothing, except it's got a new IP, woo hoo 10.1.1.8 !!
How do I do a ping beyonwizt4 on a mac, same as before in Terminal?

Yep, from terminal. Just type it out like the other pings.

I can, but it has to spend some 20 seconds thinking about it, see the contents of Movie folder and even download files from it and as mentioned by someone earlier, this just means the LAN is OK, just not the WAN.

Oh interesting, so it *is* on the network now? Was that working like that previously?

A question, MrQuade said that if the T4 "thinks" its address is 10.1.1.4 (now . then it is unlikely to have actually acquired another one via DHCP.
So the question is, how did the T4 get these numbers in the first place?

It gets these numbers from your router.
DHCP (Dynamic Host Configuration Protocol) is used to do this. When the T4 is turned on it asks the network for an address, and if there is a DHCP server present, it will tell the T4 what address to use. In this case, your router is the DHCP server.
As an added note, you must only ever have one DHCP server on your network, otherwise they will fight .

Also the inquiry about LAN activity LEDs in the router don't flash, the lights at the back of the T4 I had not thought of, what should I expect in a working machine?

You should have a solid orange light to indicate the link is up, and a flashing red light to show traffic is being received.

[raymondjpg]

An extended (20min) power down of both modem and T4 changed nothing, except it's got a new IP, woo hoo 10.1.1.8 !!
How do I do a ping beyonwizt4 on a mac, same as before in Terminal?
I can, but it has to spend some 20 seconds thinking about it, see the contents of Movie folder and even download files from it and as mentioned by someone earlier, this just means the LAN is OK, just not the WAN.
I think I will before this day is out upgrade to v19.3 and see what that does as noted by paul_oz53

Looks like the DHCP server is working OK, so that could point to something awry in the T4. When all else fails, and these new generation Beyonwiz PVRs start playing up, a reflash of the firmware (even if the most recent firmware is installed) sometimes will fix the problem, even if one can't tell what the problem was in the first place.

If upgrading from v17 to v19 firmware then you could chance backing up your settings and restoring them after flashing the new firmware. However, I'd say it would be more prudent to set up the PVR from scratch and then backup the settings when you are satisfied all is working well. If you do that you will lose scheduled timers and auto timers, but not recordings on the HDD. There may be other tweaks available to get your auto timers back, but probably fiddly.

Edit: My mistake, I see that you use IceTV, so getting timers back should be easy.

[Robert_M]

Hello again,
Faffed around too long so will upgrade to V19.3 in the morning and report outcome

Raymondjpg, thank you agreed the DHCP is working as it gave me new numbers but if it does that why then we wonder, why the network test comes back undetermined IP?

MrQuade, thanks for the ping beyonwizt4 via terminal, came back with Unknown host.
Still wondering how its issued these numbers as per above.
I will check the LAN activity LEDs tomorrow.
As for LAN connectivity, yes always, but no WAN
I also have 1 only , the router/modem, DHCP server.

PRL, interesting about the partial DHCP issuance but ......

So I'm still confused. Till tomorrow, a pleasant evincing bid to you all
Robert

[Paul_oz53]

Hello again,
Faffed around too long so will upgrade to V19.3 in the morning and report outcome

...

Hopefully, that will complete the picture. When a Wiz plays up, corrupt firmware is often at play. In my case, the two actions combined restored normality.

Save your settings tonight if you can but when you upgrade, do a setup from scratch - do NOT restore settings. This gives you the best insight into whether there is a hardware problem or not.

If all is well, then restore settings. If it then goes pear-shaped you will know its due to a setting file corruption.

[Robert_M]

Dear all,
MrQuade, raymondjpg, Paul_oz53, PRL, in particular,

THANK YOU for your kind assistance, THE UPGRADE TO V19.3 (nov edition) worked!!

Still curious why it was happily working for months then popped it's network cork!

Case can I think be considered closed

[Robert_M]

Forgot to add these pix

[raymondjpg]

Still curious why it was happily working for months then popped it's network cork!

You'd be in good company. Glad it all worked out OK

[prl]

THANK YOU for your kind assistance, THE UPGRADE TO V19.3 (nov edition) worked!!

Still curious why it was happily working for months then popped it's network cork!

Thanks. It's a pity that we didn't get to the bottom of the cause, but at least it's OK now.

BTW, now that your network is running to the T4, you can do screenshots from your browser. just enter http://beyonwizt4/ in the browser's address bar, and press ENTER (or return, depending on your keyboard). You should then connect to the Open Webif Web pages served from the Beyonwiz.

Then click on Grab Screenshot in the sidebar, and when the image appears you can use your browser to save the image to a file (e.g. in Firefox, right-clink, Save Image As...). It generally gives a cleaner and clearer image than using a camera, and may be more convenient.