No Connectivity With Shield TV, Roku, or Fire TV

johnpoz

@thearm said in No Connectivity With Shield TV, Roku, or Fire TV:

t is via computer name.

so just a host name, not a fully qualified name with domain.tld etc..

You computer could be auto adding the domain suffix.. If not your doing a broadcast for it.. It is always better to use fully qualified domain name..

Can you access the share via IP? Or actually use what the fqdn is..

thearm

@johnpoz I'll get back to you once I put pfsense back in place. Not sure when that will be, but I will do it soon. Thanks for the help thus far.

thearm

Ok, I set it up again tonight. Kodi on the Shield, connected via hard wire to an AP with openWRT, gives an 'connection timed out' error when connecting to a share on a Windows server. I rebooted the shield and then I got an 'invalid argument' when trying to open the same share. I tried to connect to the SMB share, via PC name, and I get a 'connection refused'.

My wireless PC in the bedroom, connected to the same AP, has no trouble getting to the same share.

When I ping my server, I get an IPV6 response it seems. So I tried to diable 'Allow IPv6' which doesn't work. However, I'm going to reboot my devices and see if that changes things. IPV6 is not enabled on my Windows server that I can remember, but I'll check.

Weird...

thearm

Stand down. I think it is a Comodo software firewall rule (shown below) on my server was causing the issue. Once I deleted it, kodi can now connect. Not sure why the PC in my bedroom via wifi can get to the share but the shield could not. And, not sure why the Shield can get to it if I put my Asus router in place instead of pfsense.

Here is a pic of the rule (older version, but this is the same rule): https://help.comodo.com/uploads/Comodo%20Internet%20Security/1bca1244957cf78a78b90fc0d6acd490/5eac818f1e1c4adc19d335055b06586b/f7356b41de168af74a9f88f43cd245f1/cis_firewall_global1.png

jblkstne

@thearm Glad you figured it out. I ended up going full Omada so I haven't had any issues like I did before but obviously couldn't chime back in with any experience.