Reply to thread

Message

<blockquote data-quote="doveman" data-source="post: 853927" data-attributes="member: 67412">I don't normally use Windows Firewall but want to keep this machine I'm building as clutter free as possible, so thought I'd give it a go. I had it disabled when installing MP so it didn't autocreate any rules.&nbsp;I've now created a rule for each of Incoming and Outgoing set to Allow, All Profiles, Any Program, Any Protocol, Any Port, Local Address Any, Remote Address 192.168.1.64-192.168.1.70 (this PC is 192.168.1.68), 192.168.2.1 (I use the Loopback Adapter), 127.0.01 and local subnet. I added some of these after it didn't work with less. I should think these rules would allow all traffic on the LAN.&nbsp;However, when loading MP config or TV Server config I still get a Windows Firewall popup saying it's blocked some features of the program and inviting me to allow traffic on the Private Network and when I OK this it creates four new rules in Incoming (for each program), two to allow UDP and TCP on Private and two to block UDP and TCP on Public. I don't understand why this is necessary unless they need to communicate to extra Remote addresses that aren't covered by my Allow All on LAN rule. I like to keep things tidy and understand why things aren't working, so would appreciate some advice.</blockquote>

[QUOTE="doveman, post: 853927, member: 67412"] I don't normally use Windows Firewall but want to keep this machine I'm building as clutter free as possible, so thought I'd give it a go. I had it disabled when installing MP so it didn't autocreate any rules. I've now created a rule for each of Incoming and Outgoing set to Allow, All Profiles, Any Program, Any Protocol, Any Port, Local Address Any, Remote Address 192.168.1.64-192.168.1.70 (this PC is 192.168.1.68), 192.168.2.1 (I use the Loopback Adapter), 127.0.01 and local subnet. I added some of these after it didn't work with less. I should think these rules would allow all traffic on the LAN. However, when loading MP config or TV Server config I still get a Windows Firewall popup saying it's blocked some features of the program and inviting me to allow traffic on the Private Network and when I OK this it creates four new rules in Incoming (for each program), two to allow UDP and TCP on Private and two to block UDP and TCP on Public. I don't understand why this is necessary unless they need to communicate to extra Remote addresses that aren't covered by my Allow All on LAN rule. I like to keep things tidy and understand why things aren't working, so would appreciate some advice. [/QUOTE]

Verification