Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Home/Work and Private
Message
 
 
To
09/02/2022 16:00:17
General information
Forum:
Windows
Category:
Security
Miscellaneous
Thread ID:
01683509
Message ID:
01683512
Views:
14
>>Hi,
>>
>>On Windows 7, I go to the Control Panel -> System Security -> Windows Firewall -> Allow Programs.
>>
>>Some programs have the Home/Work (Private) checked. Some have Public checked. Some have both checked.
>>
>>I am having a problem with the SecureLink on this PC. I started it (SecureLink) many times; so I see many instances of this program in this, Allow Programs, window. Some instances of the securelink have Home/Work (Private) checked. And some others Public checked.
>>
>>What is the purpose of the Home/Work and Public? And should I make both to be checked for SecureLink?
>
>In Windows networking, Home/Work are "trusted" networks, and Public is "untrusted" e.g. public Wi-Fi, internet cafe etc.
>
>On workstations Windows Firewall is primarily to prevent incoming connections, from some other computer to yours. Outgoing connections are by default not restricted. By default, firewall rules for incoming traffic are more restrictive for public than home/work networks (as one might expect).
>
>I'm not familiar with SecureLink but from a quick Google it looks like some sort of remote access utility. If the action you're trying to do with it involves initiating a connection from your computer to some other remote machine, then the firewall on your machine should not need to be adjusted. If for some reason your machine needs to accept incoming connections from SecureLink then your firewall may need to have rules allowing this. If that's the case then the incoming rules would need to be in effect for the type of network you're on at the time. For example, if you have a rule allowing SecureLink incoming traffic for home/work networks only, and you're on a public network, then the incoming traffic will be blocked.
>
>Because of issues creating incoming firewall rules, and the potential security issues that arise, most remote access/security products are architected to not require incoming firewall rules/access. If you are initiating the connection request (i.e. outgoing traffic) you should not need to do anything with Windows Firewall.
>
>Be aware that some 3rd-party antivirus/security suites include their own firewalls. If in use they usually disable the built-in Windows Firewall, so if you make any adjustments to Windows Firewall they will have no effect.

Just to add to the previous message. I know that when SecureLinkCM starts it asks the Windows if it is ok to make changes to the computer. And it stopped doing it. So, maybe, at one time I mistakenly clicked on Do Not Allow. And Windows 7 "remembers" it. So I need to find where I can revert this choice.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform