zerowalker 0 Posted April 21, 2020 Share Posted April 21, 2020 Stupid question but i just can't get any policies to work that tries to allow connections. I have tried making Miracast work by allowing port 7236. Tried making Powershell Remoting work by allowing port 5985 etc. I do set the port on both Local/Remote, and i tried using with and without ip ranges. Could someone provide an example perhaps, i am most likely missing something very obvious. Thanks! Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,130 Posted May 21, 2020 ESET Moderators Share Posted May 21, 2020 Hello @zerowalker, On 4/21/2020 at 9:39 PM, zerowalker said: I do set the port on both Local/Remote, and i tried using with and without ip ranges. I guess that might be the issue as the one port should be static, but the second one is usually generated randomly so make sure you put the port number to the correct destination i.e. local / remote. Or if the Miracast has an static IP you may allow all traffic from it... Peter Link to comment Share on other sites More sharing options...
zerowalker 0 Posted June 17, 2020 Author Share Posted June 17, 2020 Having some difficulties still, but i think the main issue was that the policies seemed to overwrite the firewall rules by default or something? Couldn't quite figure it out, but if i had multiple policies, it would mess things up, if i had one, it seems to work. I don't quite get the part where you allow something in the firewall, but it can still be blocked via the IDS, is that supposed to happen? Link to comment Share on other sites More sharing options...
Recommended Posts