Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 4 subscribers
  • Views 27320 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Strange behavior with smart tv

GuidoCraenen

Hello,

I have a Sony smart tv running in my network that's connected to the internet, can run apps, Netflix, etc. I'm encountering something strange with it since yesterday. To make sure I can run the apps and Netflix I've made a fixed netwerk entry from the DHCP server list and added that to Web Protection > Filering Options > Misc > Skip Transparant Mode ... This worked for a while (a bit more then a week), but suddenly stopped working and all apps disappeared, app connections where not possible and Netflix from the smart tv can not be reached.

When I removed the fixed entry from network definitions, I got a warning message stating the same entry was also fixed (I guess it means the mac address) to a different IP address from the internal network. But I cannot find that IP address in my network lists (also cannot ping it), and a lookup on the smart tv revealed that this ip address is not used from the tv too. After removing the fixed entry the smart tv can reach and install all apps and Netflix starts, but hangs on 25% when loading something. The same behavior I found before I added it to Skip Transparant etc.

After making a new fixed entry in network definitions, I'm getting the same behavior as  described above. I'm stumped, it looks like the mac address of the smart tv is somehow stuck on a non existing IP address?? Is there a way to flush things so it's not stuck anymore?



This thread was automatically locked due to age.
Parents
  • 0
    When you gave the TV a static IP, was it one that was outside the scope offered by the DHCP server instance? From the Help/Admin guide:

    Note – To avoid an IP address clash between regularly assigned addresses from the DHCP pool and those statically mapped make sure that the latter are not in the scope of the DHCP pool. For example, a static mapping of 192.168.0.200 could result in two systems receiving the same IP address if the DHCP pool is 192.168.0.100 – 192.168.0.210.
    __________________
    ACE v8/SCA v9.3

    ...still have a v5 install disk in a box somewhere.

    http://xkcd.com
    http://www.tedgoff.com/mb
    http://www.projectcartoon.com/cartoon/1
Reply
  • 0
    When you gave the TV a static IP, was it one that was outside the scope offered by the DHCP server instance? From the Help/Admin guide:

    Note – To avoid an IP address clash between regularly assigned addresses from the DHCP pool and those statically mapped make sure that the latter are not in the scope of the DHCP pool. For example, a static mapping of 192.168.0.200 could result in two systems receiving the same IP address if the DHCP pool is 192.168.0.100 – 192.168.0.210.
    __________________
    ACE v8/SCA v9.3

    ...still have a v5 install disk in a box somewhere.

    http://xkcd.com
    http://www.tedgoff.com/mb
    http://www.projectcartoon.com/cartoon/1
Children
Unfiltered HTML