PDA

View Full Version : Mezzmo & Kodi - Plugin not seeing server but Kodi does



Roofus
08-03-2016, 09:46 AM
For some reason Kodi on Windows 10 PC can see my server and plays etc. but the Plug in cannot see the server.

On my iPOD, Andoid etc running Kodi the plugin is working fine but not on the Windows PC.

Playback does stock occasionally but I don't believe this is related.

I have tested using Kodi 16 (Using latest version of Mezzmo and bundled plugin).

PC is a clean install of Windows 10 and only has Mezzmo Kodi installed.

Re-tested with re-install of Kodi 16 and also tested with Kodi 17

I have even switched firewalls and AV with no difference (reason unrelated but removed one more explanation).

Run out of ideas now.

Steve

Peter
08-03-2016, 10:21 AM
Hi Steve,
we had a test PC here that was showing the same behaviour. It had Kaspersky Internet Security installed but it was a trial and had expired and the Windows Firewall disabled, after uninstalling Kaspersky the Kodi addon was able to find the Mezzmo server. Possibly you have some similar software on your PC that is causing the problem, the anti-virus software may still be blocking the port even though it is turned off? The Mezzmo Kodi addon sends an M-Search multicast message on port 1900 so if anything is blocking this no servers will be found. Kodi itself listens to incoming Notify messages so even if it can't send an M-Search it will find the servers using the Notify messages but the addon does not do this.

Hashybot
08-03-2016, 08:00 PM
Thought I would chime in here...

Add an exception for the IP of your Kodi server and for both ports 1900 and 2700 via your firewall. For me I done this on Bitdefender 2015. So my settings were adding an exception for my static IP (192.168.20.20) and ports as mentioned above.

Roofus
08-03-2016, 08:30 PM
Thanks will give that ago although I have just switched to F-Secure and Windows 10 firewall and unsure where the settings are at the moment.

I take it you mean alter the firewall on the client PC not the server PC.

Earlier today i temporarily disabled windows firewall completely and it still didn't see the server.

I put into windows firewall an outbound exception allowing kodi but I am not 100% sure that's enough. Saying that when the firewall is disabled I would have expected it to work.

Roofus
08-04-2016, 08:52 AM
Ok found the source of the problem, just not 100% sure of the fix just yet. Realised my PC used just as a client is connected on my network via my wired network rather than wifi. Up till recently this went from my main router, through an unmanaged switch to the PC. This working fine. As part of swapping Broadband provider and therefore router I have just swapped the switch for a spare wireless router which I have "reconfigured" with DD-WRT to be a wireless AP and a managed switch. Looking at the FAQ's I spotter a few router settings to set and on my main hub and the only thing I had to alter was disabling UPnP (no other settings are even available on the new Virgin Hub 3!) but I expect as I have every setting in the world available with DD-WRT, something needs unblocking.

Just not sure what, any ideas bearing in mind Kodi was working without the plugin using this router, could it be simply unblocking port 1900?

Peter
08-04-2016, 09:27 AM
Hi Steve,
you can try disabling the firewall in DD-WRT to see if this resolves the problem or add an exception to allow port 1900 through. Since Kodi can see the Mezzmo server without the plugin this indicates the Notify multicast messages from the Mezzmo server are getting through but the M-Search multicast from the plugin is not getting through. The following link talks about steps to disable multicast in DD-WRT http://www.dd-wrt.com/wiki/index.php/Setting_up_IPTV_without_impact_to_LAN_and_Wireless _traffic can you please check these settings on your router to make sure they are enabled instead of disabled and also check the firewall section to see if it is blocking the multicast as discussed in the link?

Roofus
08-05-2016, 08:43 AM
Ok thanks both now sorted. My problem was my 2nd switch/AP setting. It was actually it's IP address, it was not in the correct range since I had upgraded my main router. Once I forced my PC to be in the same range I could get on, fix the IP and hey presto all now works.

Thanks for your help

Steve