>>>>>>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.
>>>
>>>If you're using a specialized product which requires modifications to your local firewall rules, it will be best by far to talk to SecureLink tech support.
>>
>>I have had many, many exchanges with the SecureLink tech support. So far, no positive outcome.
>
>If the product needs to be "installed" on your computer, you could ask them if they have a "complete" uninstaller which can wipe any traces of the program from your computer, then install it again from scratch. You might want to manually remove any firewall rules related to it which may remain after running the "complete" uninstaller (prior to reinstallation).
>
>If you know roughly when the product was last working, as a somewhat nuclear option, you could use System Restore to go back to that time. Note that may roll back other app or configuration changes you made since then.
>
>I haven't mentioned it yet but you really should move away from Win7, it's been out of support for over 2 years now.

I do have Windows 11 (was 10) computer that works well with SecureLinkCM. I was just hoping that I can revive the Windows 7 (which I still use for VFP development).