I'm managing my firewall manually, inbound and outbound connections are not allowed until I create the specific rules. I'm using Windows Firewall Control from Binisoft to manage my firewall rules.
It seems that on every reboot Remote Assistant searches for rules containing "remote assistant.exe", deletes them (inbound AND outbound), and creates a new rule to allow an inbound connection.
While this is acceptable for an average joe, it kinda blocks itself in this more restricted environment (homelab) by not creating a rule to allow outbound connections. — Ralf B
I just switched off the two options you mentioned. The rules are still getting deleted. But if this is a predicted behaviour, why only creating an inbound connection and not an outbound connection? — Ralf B
And why deleting manually set firewall rules in the first place? This just doesnt add up, someone just messed things up in this version. — Ralf B
Every reboot i have to manually re-set those firewall rules. If im not physically at the machine at a reboot (windows updates and such) i get locked out. That cant be an expected behaviour. — Ralf B
ping localhost -n 30 "C:\Program Files\Malwarebytes\Windows Firewall Control\wfc.exe" -allow "C:\Program Files\Remote Assistant\Remote Assistant.exe"
ping localhost -n 30 netsh advfirewall firewall add rule name="RemoteAssistanceInbound" dir=in action=allow program="C:\Program Files\Remote Assistant\Remote Assistant.exe" enable=yes netsh advfirewall firewall add rule name="RemoteAssistanceOutbound" dir=out action=allow program="C:\Program Files\Remote Assistant\Remote Assistant.exe" enable=yes
Thank you for visiting! Please take a moment to register so that you can participate in discussions!