Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 981 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PCAnywhere 10.5 and ASL 2.016

Steven Juras
Does anyone know if there are any issues with PCAnywhere 10.5 and Astaro 2.016 that would not allow a connection to take place?

While I do have about 1 day experience with Astaro, I have been involved with networks for over 5 years so I understand to concept of what I'm trying to allow.

I'm a little puzzled at the nomenclature of ASL's DNAT structure.  If I set it up to:

PreNat Destination of [SERVER running PCAnywhere] with a service of [PCAW (tcp/udp 1064:65535 5631:5632)}

PostNAT Destination of [ASL's public NIC address] with same [PCAW] service.

Is that right?  I've got the packet filter to allow the PCAW service to the public nic of the firewall.

Any thoughts???


This thread was automatically locked due to age.
Parents
  • 0
    Steven Juras,

    vice versa, the firewall's ip is the address to be
    NATted (Pre NAT) into the servers address (post NAT).
    In addition you'll need packet filters allowing
    PC-Anywhere ports to the server, e.g.
    "ANY PC-ANYWHERE_PORT INTERNAL_ADDRESS_OF_SERVER"

    read you
    o|iver
Reply
  • 0
    Steven Juras,

    vice versa, the firewall's ip is the address to be
    NATted (Pre NAT) into the servers address (post NAT).
    In addition you'll need packet filters allowing
    PC-Anywhere ports to the server, e.g.
    "ANY PC-ANYWHERE_PORT INTERNAL_ADDRESS_OF_SERVER"

    read you
    o|iver
Children