Author Topic: Firewall blocking Android Remote app to KODI Media Center  (Read 3575 times)

0 Members and 1 Guest are viewing this topic.

Offline Wurlitzer

  • Newbie
  • *
  • Posts: 16
Firewall blocking Android Remote app to KODI Media Center
« on: December 21, 2015, 01:55:31 AM »
Have KODI [old XBMC Media Center] running on a Win 7 Home Premium 64bit works fine in local mode.

Added the official KODI Android app KORE to use my smart phone as a remote.

The app [and another called Yatse  with the exact same problem] on my phone can see the KODI media center and finds its unique name so the app can see the Win 7 machine but will not connect.

If I disable the Firewall, the app immediately connects. I have tried everything in the convoluted settings for firewalls that I can think of but only disabling the firewall allows this app to function.

From the Firewall log:     12/20/2015 6:44:29 PM   192.168.1.3   55335   192.168.1.10   9090   TCP   In   C:\Program Files (x86)\Kodi\Kodi.exe   Public/High Risk Zone

I don't understand the Public/High Risk Zone as i have set all local devices to use a much lower security setting for Private

the 192.168.1.3 is my phone and 192.168.1.10 is my Win 7 PC

In the Firewall main screen it shows KODI as a recent blocked program.

I tried adding C:\Program Files (x86)\Kodi\Kodi.exe to the exclusion list with no results.

Offline Wurlitzer

  • Newbie
  • *
  • Posts: 16
Re: Firewall blocking Android Remote app to KODI Media Center
« Reply #1 on: December 21, 2015, 07:39:43 PM »
I guess nobody else can figure out AVAST's Firewall settings.

Glad AVAST does not make aircraft flight control software as 90% functionality means certain death.

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Firewall blocking Android Remote app to KODI Media Center
« Reply #2 on: December 21, 2015, 08:04:20 PM »
I'm glad you don't make airplane tires or they all would have punctures right after production. :P
The log file clearly is telling you what is going on.

A real simple solution is setting the firewall to ask what to do when traffic is detected.