Re: PC Anywhere Outbound

From: David Dixon (anon_at_anon.com)
Date: 12/08/04

  • Next message: chris_at_brightplanit.com: "WebDav publishing behind ISA server"
    Date: Wed, 8 Dec 2004 11:18:49 -0000
    
    

    Try this, but with you being the remote you would have to make the inbound
    an outbound.

    http://www.isaserver.org/tutorials/Publishing_a_host_using_PCAnywhere_behind_ISA.html

    -- 
    Dave Dixon
    MCAD.net (CM)
    SBS2003 Premium
    "Cyskon" <cyskon@msn.com> wrote in message
    news:O7ohbT%23yEHA.1392@tk2msftngp13.phx.gbl...
    > 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.
    >
    >
    >
    

  • Next message: chris_at_brightplanit.com: "WebDav publishing behind ISA server"

    Relevant Pages

    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa.clients)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isaserver)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa.configuration)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa.vpn)

    Loading