Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
media_server_settings [2017/12/20 00:12]
admin [Configure Windows Firewall]
media_server_settings [2020/12/07 02:32] (current)
admin [Run Mezzmo server as]
Line 29: Line 29:
  
 **Tip:** When running Mezzmo server as a Windows service, if you are having the issue where Mezzmo server is not listing your files on your devices or not being able to access your files on a NAS or external computer, then the reason will most likely be due to the Windows Local System account not having access rights to your files. ​ To fix this, you should change the Windows account that the Mezzmo server Windows service is running under. ​ Go to Windows Services window in Control Panel. ​ Right-click on the Mezzmo service and click Properties. ​ On the Properties dialog, adjust the Log On settings to use the same Windows user account that Mezzmo (Windows) app is running under. **Tip:** When running Mezzmo server as a Windows service, if you are having the issue where Mezzmo server is not listing your files on your devices or not being able to access your files on a NAS or external computer, then the reason will most likely be due to the Windows Local System account not having access rights to your files. ​ To fix this, you should change the Windows account that the Mezzmo server Windows service is running under. ​ Go to Windows Services window in Control Panel. ​ Right-click on the Mezzmo service and click Properties. ​ On the Properties dialog, adjust the Log On settings to use the same Windows user account that Mezzmo (Windows) app is running under.
 +
 +**Tip:** You may need to add the Logon as a service permission to your account.
 +To add "Log on as a service"​ permissions:​
 +  - Run Start > Control Panel > Administrative Tools > Local Security Policy
 +  - Select ​ Local Policies > User Rights Assignment > Log on as a service
 +  - Click Add User or Group, and then add the appropriate account to the list of accounts that possess the Log on as a service right.
  
  
Line 94: Line 100:
 After clicking the **Configure Windows Firewall** button, the button should become disabled. ​ This tells you that all firewall rules have been successfully added into your Windows firewall. ​ If the **Configure Windows Firewall** button is not disabled after clicking it, then you may have existing rules in your Windows firewall that are conflicting with the rules that Mezzmo needs to add.  Follow these steps to fix this problem: After clicking the **Configure Windows Firewall** button, the button should become disabled. ​ This tells you that all firewall rules have been successfully added into your Windows firewall. ​ If the **Configure Windows Firewall** button is not disabled after clicking it, then you may have existing rules in your Windows firewall that are conflicting with the rules that Mezzmo needs to add.  Follow these steps to fix this problem:
   - Go to your Windows Firewall window via Windows Control Panel.   - Go to your Windows Firewall window via Windows Control Panel.
-  - Click on **Inbound Rules** to view the list of rules for your firewall. +  - In the Windows Firewall window, click on **Inbound Rules** to view the list of rules for your firewall. 
-  - Click on the **Name** header column to sort the in bound rules by name. +  - Click on the **Name** header column to sort the inbound ​rules by name. 
-  - Scroll down the list to view the Mezzmo inbound rules.+  - Scroll down the list to view the Mezzmo ​and Mezzmo Server ​inbound rules.
   - Delete all rules for **Mezzmo** and **Mezzmo Server**.   - Delete all rules for **Mezzmo** and **Mezzmo Server**.
   - Display the **Media Server Settings** dialog in Mezzmo (Windows) application.   - Display the **Media Server Settings** dialog in Mezzmo (Windows) application.
   - Click the **Configure Windows Firewall** button. ​ It should become disabled now.   - Click the **Configure Windows Firewall** button. ​ It should become disabled now.