MasterTB
November 21st, 2009, 08:09 PM
I have a home network and unless I completely disable ESS's Firewall I cannot use WMP12 Remote Control feature.
The machines simply don't see each others WMP to controll.
The issue Is with Windows 7 and it has been checked. Using the Windows firewall works like a charm.
Edit: The firewall log says it is blocking ICSLAP Outgoing Requests (UNPnP) to the WMP and From the WMP
ok, there is no mistake here, it is a deliberate rule in ESS that prevents the comunication.
WHY ON EARTH WOULD YOU PUT THAT RULE THERE? ARE YOU TRYING TO MAKE US ALL ANGRY AT YOU?
there is a default rule in the firewall that says "BLOCK OUTGOING (AND INCOMING) ICSLAP (UNPnP) CONNECTIONS" but it is not limited to untrusted zones, NO it is a GENERAL BLOCK ALL RULE FOR ICSLAP...
where is the danger that you made the rule block ALL TRUSTED AND UNTRUSTED? WHY NOT LIMIT IT TO UNTRUSTED AT LEAST?
I really don't understand you guys.
The machines simply don't see each others WMP to controll.
The issue Is with Windows 7 and it has been checked. Using the Windows firewall works like a charm.
Edit: The firewall log says it is blocking ICSLAP Outgoing Requests (UNPnP) to the WMP and From the WMP
ok, there is no mistake here, it is a deliberate rule in ESS that prevents the comunication.
WHY ON EARTH WOULD YOU PUT THAT RULE THERE? ARE YOU TRYING TO MAKE US ALL ANGRY AT YOU?
there is a default rule in the firewall that says "BLOCK OUTGOING (AND INCOMING) ICSLAP (UNPnP) CONNECTIONS" but it is not limited to untrusted zones, NO it is a GENERAL BLOCK ALL RULE FOR ICSLAP...
where is the danger that you made the rule block ALL TRUSTED AND UNTRUSTED? WHY NOT LIMIT IT TO UNTRUSTED AT LEAST?
I really don't understand you guys.