Humax not seen by Remote Scheduler

[Green Armchair]

Hi the Remote Scheduler is reporting that my Humax has not been seen since Thursday at 13.30. this time coincides with our broadband provider changing from TalkTalk to BT.

What do I need to do to "reset" things. Assume it's due to my external IP changing?

Thanks

 

[prpr]

Does your T2 use DHCP or static IP addressing?
Can you report the output of cat /etc/resolv.conf at the command line, or look at it using the WebIf's File Editor on the Diagnostics page.
Again, from the command line, can you ping 89.248.55.75 and ping rs.hpkg.tv ?

 

[Black Hole]

Assume it's due to my external IP changing?

No. The HDR reaches out to RS, RS does not reach in to the HDR. You need to check the HDR can still access the Internet.

 

[prpr]

@af123 It might be nice to have a diagnostic that checks stuff like this without a user having to type in commands. In the long list of diagnostic utilities, networking is notably absent.

 

[Green Armchair]

I'm using a fixed IP of 192.168.1.151, but I'm not able to resolve rs.hpkg.tv or ping 89.248.55.75:

humax# cat /etc/resolv.conf
nameserver 192.168.1.1
nameserver 192.168.1.1
nameserver 208.67.222.222

humax# ping 89.248.55.75
PING 89.248.55.75 (89.248.55.75): 56 data bytes

--- 89.248.55.75 ping statistics ---
23 packets transmitted, 0 packets received, 100% packet loss

humax# ping rs.hpkg.tv
ping: bad address 'rs.hpkg.tv'

 

[Green Armchair]

Default gateway was wrong. Corrected that and can now ping those addresses.

Thanks for the pointers