No Connectivity With Shield TV, Roku, or Fire TV
-
If both those things are connected to the TP-Link just using wifi vs Ethernet it must be something the TP-Link is doing. pfSense does not see that traffic any differently and treats it all the same.
Steve
-
How would pfsense even see that traffic? Device A talking to device B on the same network pfsense has nothing to do with that..
-
@johnpoz said in No Connectivity With Shield TV, Roku, or Fire TV:
How would pfsense even see that traffic? Device A talking to device B on the same network pfsense has nothing to do with that..
Very true... But once I put my Asus router back in place, Kodi on my Shield in my living room starts talking to my server in the basement. Not sure why yet. Once I get the mental energy to look into it further, I will and I'll let you guys know what I figure out.
Thanks and have a nice holiday!
-
@thearm how are you trying to access kodi? what url or fqdn, ip how extactly do you access it http://ipaddress:port?
-
@johnpoz It is via computer name. I added the computer name to the sources list in Kodi when I got the Shield a few years ago. I could try by IP, but it would be nice to know what the problem actually is with using the PC name.
On my Win10 laptop, I can access the servers shares just fine via computer name on wifi from the TP Link AP. Granted, that is Win10 compared to Android, so maybe not a good comparison. Just an FYI.
-
@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..
-
@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.
-
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...
-
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
-
@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.
