evilivor - that you posted you could get 901/903 indicates your DNS can resolve correctly.
As I mentioned, it's not an area I know much about, I just hoped it could reset the settings or some such.
Ivor
My Humax Forum » Freesat HD » HDR 1000, 1010, 1100S
help - unable to use ondemand or showcase
(935 posts)-
| Wed 15 Oct 2014 19:10:13 #511 |
-
evilivor - 56 minutes ago »
evilivor - that you posted you could get 901/903 indicates your DNS can resolve correctly.
As I mentioned, it's not an area I know much about, I just hoped it could reset the settings or some such.
IvorOk, go to settings>system information>Network info
-write doen your IP address , Netmask, gateway address and Primary DNS
-Now connect your humax box to someother network port, ie on the back of tv or your laptop....so one end of your network cable should be on the back of your humax box and other end should be on a running laptop or TV in a powered on state.
-You should see the message of 'Lan cable plugged' or something like that on the top of the screen
-now go to Settings>Network connections> connect automatically
-The box will struggle to connect and then will give you an option to connect manually.
-in manual connection,use same IP address, netmask (should be 255.255.255.0) and gateway. However use primary DNS as 8.8.8.8
-click connect
-unplug the cable from back of TV or laptop and connect it back to router.
-check that the new DNS is shown in settings>system information>Network infowatch TV for sometime like that and I think showcase and ondemand should appear with that..
keep us updated.
| Wed 15 Oct 2014 20:18:07 #512 | -
Slightly strange instructions, but basically - provide network connection at Ethernet level but no DHCP server. (save as turning off DHCP server on router for a time.
Replicate settings changing DNS to Google.
Should be slightly slower, unless ISP configured server, not good.
| Wed 15 Oct 2014 20:38:24 #513 | -
REPASSAC - 1 hour ago »
Slightly strange instructionsDoesn't really matter so long as it works. Busy households won't want to disable dhcp on router for a time so this is a good work around.
Shouldn't be slower either, the Humax should cache the dns and even if it doesn't the Humax isn't going to be doing many lookups and in the event that the ISP's dns is causing a problem it makes perfect sense to point the Humax to one that doesn't. Only the Humax's dns has changed, not the router, so it won't affect anything else and if it fixes the problem then that can only be good.What stands out a mile here is if Humax/Freesat hadn't locked down the box so much, making it impossible to diagnose the most simplest of faults, then other members here would have been able to diagnose, flush cache, manually assign, trace etc. etc. and this would have been diagnosed by page 2 and not still limping along at page 52! Are we going for a record here?
| Wed 15 Oct 2014 22:29:26 #514 | -
h-man - 2 hours ago »
-in manual connection,use same IP address, netmask (should be 255.255.255.0) and gateway. However use primary DNS as 8.8.8.8Why are you suggesting using the same IP address? Surely that opens the possibility of the router allocating the IP address to another device and two devices with the same IP address will definitely cause problems. I would suggest giving a unique IP address outside the range of addresses used by the DHCP server on the router.
| Wed 15 Oct 2014 23:20:35 #515 | -
I stated in an earlier post that I have switched off my HDR 1000 at the plug every night for the past 18 months but since this problem started I now have to switch off and unplug both my Humax box and TV in order for showcase and on demand to work.
For some reason if I just unplug my HDR 1000 and plug it back in then I still don't have showcase or on demand except via 901/903
So now before I go to bed I unplug both HDR 1000 and TV and after plugging back in the following day I have both showcase and on demand working. This is now my new nightly routine.
| Wed 15 Oct 2014 23:37:54 #516 | -
Martin Liddle - 1 hour ago »
h-man - 2 hours ago »
-in manual connection,use same IP address, netmask (should be 255.255.255.0) and gateway. However use primary DNS as 8.8.8.8Why are you suggesting using the same IP address? Surely that opens the possibility of the router allocating the IP address to another device and two devices with the same IP address will definitely cause problems. I would suggest giving a unique IP address outside the range of addresses used by the DHCP server on the router.
Some people have a lot of knowledge, some a little and some none at all. I mainly use manual addresses; however my router has a pool of 30 dhcp and won't release any until after 10 days of non use and even then it round robbins the addresses so the chances of my router allocating the same ip address within the next couple of years is slim, it also keeps a record of ip and mac addresses and I've not tested it as I can't be bothered, but I've no idea whether it would re-allocate an active address to a different device or not.
There is a problem if an ip address is plucked out of the air and allocated manually and this clashes with a dhcp allocated address; however in this example the dhcp has already allocated the ip address to the Humax, it's not then going to allocate the same address to another device until it's been released.People with some knowledge will be able to allocate a free address themselves, but how do you explain to somebody with no knowledge how they find the dhcp pool, release times, access profiles based on mac addresses etc. etc. on a vanilla router. The last thing they should be doing is poking about in the router config.
You're right though, long term a unique ip address outside of dhcp should be allocated, I'm just not sure how that can be universally conveyed to Joe Bloggs with a vanilla router and pool size and config that none of us know the workings of.
I've no idea whether dns is actually causing a problem; however for those that want to try/test a dns change the method h-man proposed is a good place to start. If it works then it points to a dns problem, if it doesn't then revert back to dhcp@tonegee
presumably if it's switched off overnight it's not been/being updated? Regardless..., it's wierd, assuming your TV isn't smart and not connected in any way to the network then I can only imagine CEC and/or hdmi syncing is having an affect. Your TV's likely to be waking up and checking for software in the background overnight and if it's smart it could be doing anything. It's not a bad thing to be switching off the TV every night anyway, but if it's a chore then I'd be double checking CEC, AnyNet, easylink (whatever your TV calls CEC) settings on the TV and disabling them if possible. If that didn't work and there's no network or any other connection between the Humax and TV apart from the hdmi lead then I'd be tempted to go through a cheap hdmi switch; however if you're happy with unplugging then so be it.| Thu 16 Oct 2014 2:08:15 #517 | -
tonegee - 7 hours ago »
I stated in an earlier post that I have switched off my HDR 1000 at the plug every night for the past 18 months but since this problem started I now have to switch off and unplug both my Humax box and TV in order for showcase and on demand to work.
For some reason if I just unplug my HDR 1000 and plug it back in then I still don't have showcase or on demand except via 901/903
So now before I go to bed I unplug both HDR 1000 and TV and after plugging back in the following day I have both showcase and on demand working. This is now my new nightly routine.Why not just leave the HDR1000s plugged in as its designed to be? If it was a power hungry device then I'd understand, but it uses so little power while in stanby it shouldn't be major concern.
| Thu 16 Oct 2014 6:58:52 #518 | -
Switching off my TV, set top box, PC and monitor is something I've just done for years out of habit. However, ironically I stand corrected this morning as my HDR1000s was showing the same message as before stating that I need an internet connection.
Going to try your suggestion of leaving it plugged in but in standby. Need to do a cold reboot first to try to get showcase back.
| Thu 16 Oct 2014 7:49:18 #519 | -
damian - Most routers hold details of DHCP leases in volatile RAM and a power cut will cause the server to start re-issuing them.
That 901/903 work indicates a working DNS that presumably also works fine for other devices in the network.
DHCP is there to make life easy and is why Humax do not make it easy to manually configure it.| Thu 16 Oct 2014 8:09:59 #520 |
Reply »
You must log in to post.
