mezzmo will not start the "start media"

When i start my home server which is running windows homeserver 2003, i get an error message that mezzmo has encountered a problem and must close. After os is up and running i open mezzmo and noticed it is not running. I try to manually start the media server and it will not start. Uninstalled the program and reinstalled with the same results. I have been using Mezzmo for a while with no problems and then this started happening. Miss my media streamer on my sony bravia tv. Any help would be most welcome.

Can you please turn on logging (see this thread: http://forum.conceiva.com/showthread...nostic-logging) then try to start the server and once it fails send us the logs to support (at) conceiva (dot) com

Turns out the if you have Hamachi installed it will disable your meezmo media server so it will not be able to connect to your network. I uninstalled Hamachi and the media server started right up. Turns out that somehow Hamachi blocks port 1900 from being accessible thus rendering the media server nonoperational. Just thought i would pass this along in case someone else runs into the same problem. Thanks again to Dennis and Adric for their quick responses and great tech support.

I too just found out Mezzmo doesn't like Hamachi and there isn't a way to tell Mezzmo to ignore the Hamachi interface. I want to use Hamachi so my workaround is to disable hamachi before starting the mezzmo service and then enable it afterwards.

I have a script to handle all that and scheduled that to run at computer start. Here's the script (start_mezzmo.cmd):

Code:

---

netsh interface set interface "hamachi" DISABLED
set stop mezzmo
call:sleep 5
net start mezzmo
call:sleep 20
netsh interface set interface "hamachi" ENABLE
goto:EOF

:sleep
set/a sleeptime=%1+1
ping -n %sleeptime% 127.0.0.1 >nul
goto:EOF

---

I've added the extra 'set stop mezzmo' so this same script can be used to restart the mezzmo service.

Now if Library Maintenance needs to stop and start the mezzmo service, then my workaround breaks.

Thanks for sharing your script.

This is quite a common issue for all DLNA servers like Mezzmo. Hamachi (for some reason) uses port 1900. However, port 1900 is required by the UPnP standard for broadcasting and, without access to it, DLNA servers cannot broadcast and be seen by DLNA devices on your home network.

So if you have Hamachi installed on your computer, you should disable it or uninstall it if you wish to stream media using DLNA servers like Mezzmo.

Thanks for the mention of upnp. In hamachi, there is a setting called 'Disable UPNP'. Setting it to YES seems to allow it to co-exist with Mezzmo. But lets see what happens tomorrow...

Please consider putting options to select the network interfaces that Mezzmo binds to. For vpn-type connections like Hamachi or my work VPN, I wouldn't want my dlna traffic to go over those interfaces.

Thanks for this feedback. Please do update us later on so we all know if "Disable UPnP" in Hamachi works. It may allow both Hamachi and DLNA servers like Mezzmo to work alongside each other.

After maintenance or a reboot, both hamachi and mezzmo are still working. So Disabling UPnP in hamachi is the way to go.

Quote:

---

Originally Posted by badbob001

After maintenance or a reboot, both hamachi and mezzmo are still working. So Disabling UPnP in hamachi is the way to go.

---

Thanks for the confirmation. We will inform Mezzmo users of this solution if they are also having the same problem.

Could this be part of the reason my Mezzmo server always crashes on startup? I don't have the problem with starting the MezzmoMediaServer.exe over RDP, but Mezzmo does still crash, without fail, on startup (reinstalled a few times).

It's hard to say for sure. Can you please send in logs of such a crash so that we could see if there's anything coming up in the logs that would give us a clue?

I sent a couple of sets of logs a while back but got no reply.

It's no hardship, I've scripted an auto restart of the relative mezzmo services after bootup which has cured the problem for me :).

Strange, someone should have replied to you. Can you please PM me your e-mail or your support case number and I'll check up on this.