Vic,
The best way to find out which app is responsible is to set app status
to manual, then go into the app manager, start the GW Toolkit, then
begin launching each app one by one until the error appears.
AppGet already uses ports 80 and 443 depending on what you are trying to
do. What is more likely happening is that Window-Eyes itself is being
blocked from accessing the network. This is something which your network
administrator will need to correct.
Regards,
Steve
On 8/12/2011 10:41 AM, [email protected] wrote:
Hello Steve
I turned app status to off.
I changed my profile back to default.
When I turn app status back on, the error keeps coming up.
If it is a specific app that is causing the error, what is the best way
to find the problem?
Also, when I turn app status on then I can use Get App. However nothing
comes up, because I suspect our firewall is blocking that specific port.
Is there some where I can change the settings so that it is using HTTP
port 80?
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
--
Stephen Clower
Product support specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
