PC Anywhere Outbound

From: Cyskon (cyskon_at_msn.com)
Date: 11/16/04


Date: Tue, 16 Nov 2004 09:03:41 -0500

Hello Group,

I would appreciate some help is resolving this one.

I am trying to create an Access Rule to allow my PC Anywhere program to
connect to PC Anywhere hosts that I have setup.

Now it works fine for machines that are on my LAN, however, I have a machine
at an external office that I need to be able to connect to and manage.

I have created a protocol in the Toolbox with the following information:

PRIMARY CONNECTIONS
    Port Range = 5631-5632
    Protocol Type = TCP
    Direction = Outbound

SECONDARY CONNECTIONS
    Port Range = 5631-5632
    Protocol Type = UDP
    Direction = Receive Send

I then create a new Access Rule that Allows the Protocol from Internal (LAN)
sources to External (Net) sources.

Now when I go to monitoring, and try to access the host at the external
office, I see where it first starts out by saying Unidentified IP Traffic
(port 5631), then it shows the protocol information that I created and in
the Actions column says that it has initiated connection, then immediately
says closed connection. These are both on the port 5632.

Appreciate some expert intervention :)

Thanks.



Relevant Pages

  • PC Anywhere Outbound
    ... I have created a protocol in the Toolbox with the following information: ... SECONDARY CONNECTIONS ... I then create a new Access Rule that Allows the Protocol from Internal ... These are both on the port 5632. ...
    (microsoft.public.isaserver)
  • PC Anywhere Outbound
    ... I have created a protocol in the Toolbox with the following information: ... SECONDARY CONNECTIONS ... I then create a new Access Rule that Allows the Protocol from Internal ... These are both on the port 5632. ...
    (microsoft.public.isa)
  • PC Anywhere Outbound
    ... I have created a protocol in the Toolbox with the following information: ... SECONDARY CONNECTIONS ... I then create a new Access Rule that Allows the Protocol from Internal ... These are both on the port 5632. ...
    (microsoft.public.isa.configuration)
  • PC Anywhere Outbound
    ... I have created a protocol in the Toolbox with the following information: ... SECONDARY CONNECTIONS ... I then create a new Access Rule that Allows the Protocol from Internal ... These are both on the port 5632. ...
    (microsoft.public.isa.publishing)
  • PC Anywhere Outbound
    ... I have created a protocol in the Toolbox with the following information: ... SECONDARY CONNECTIONS ... I then create a new Access Rule that Allows the Protocol from Internal ... These are both on the port 5632. ...
    (microsoft.public.isa.vpn)

Loading