Re: Problem with FreeBSD 4.8, ipf, ipfnat and forwarding for pcAnywhere

From: Peter Risdon (peter_at_circlesquared.com)
Date: 05/10/04

  • Next message: Bill Moran: "Anyone else having trouble with Samsung 160G drives?" 
    Date: Mon, 10 May 2004 18:22:02 +0100
To: adp <dap99@i-55.com>

    adp wrote:

    >I am using telnet just to see if the port accepts connections. That test
    >works fine internally. We are not running a telnet server. Also, we are
    >telnetting to the pcAnywhere port, not the telnet port. :)
    >
    >

    I've only historical experience with PCAnywhere, nowadays sticking with
    VNC for this sort of thing, but your post made me google out of
    interest. One thread alerted me to this interesting entry in
    /usr/local/share/nmap/nmap-services - I believe it might only be
    relevant to version 10.5 (and above?)

    pcanywhere 65301/tcp

    Several sources mention port 22 as well. Then again, some don't. This
    seems a moderately well informed example of one that does:

    http://old.gallantry.com/support/technotes/tn01052403_pcaw/

    And at the foot of that page are links to several of Symantec's own
    techical help documents for this exact issue.

    This might be useful:

    http://www.eicon.com/support/helpweb/dlanen/sol7.htm

    There's some troubleshooting info there. It does seem to matter which
    version(s) of PCAnywhere you're using.

    <quote>

    Versions of pcAnywhere prior to 7.5 use non-registered TCP/IP ports. All
    later versions, including v7.5 use the following registered TCP/IP ports:

        TCP – 5631
        UDP – 5632

    You will run into problems when you are using a version of pcAnywhere
    with non-registered TCP/IP ports on one side of the connection and a
    version with registered ports on the other side of the connection.

    Symantec provide a fix for this problem on their FTP server. Please see
    the Symantec Knowledge Base for further information
    http://www.symantec.com <http://www.symantec.com/>

    </quote>

    After that, FAQs from various companies show the reasonableness of your
    approach. For non-FreeBSD-specific configuration details that might give
    a clue, see:

    http://www.netopia.com/en-us/equipment/tech/c_faq.html#ph_no_5

    and

    http://help.broadviewnet.net/support/nat-pcanywhere.htm

    I found two threads discussing a very similar problem with a Cisco
    router as a gateway, and along with the surprising information that one
    poster claims to have solved a similar issue by upgrading the drivers of
    the graphics card in the PCAnywhere host, one resolution is here:

    http://isp-lists.isp-planet.com/isp-routing/0205/msg00051.html

    and another here:

    http://www.tek-tips.com/gviewthread.cfm/pid/34/qid/832487

    HTH

    PWR.
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

  • Next message: Bill Moran: "Anyone else having trouble with Samsung 160G drives?"

    Relevant Pages

    • RE: Problem with FreeBSD 4.8, ipf, ipfnat and forwarding for pcAnywhere
      ... For your telnet test to pcanywhere ports on target Lan pc to work ... I believe pcanywhere is one of those applications that imbed the ip ... pass in quick proto udp from any to public-ip port = 5631 group 200 ...
      (freebsd-questions)
    • Re: not sure if anyone can help me
      ... >> I installed pcAnywhere on a coworker's computer so she can access her ... >> work computer from home, but it is telling me that I have to open the ... >> symantec ports on the router and I have no idea how to do that. ...
      (comp.security.firewalls)
    • Re: PCanywhere security
      ... >>> your computer via PCAnywhere ports can likely access it through other ... >>> ports and even start PcAwHost and then has access to your company data ... and the company data is now available to outsiders. ... PcAnywhere security ...
      (comp.security.firewalls)
    • Re: PCanywhere security
      ... >>> your computer via PCAnywhere ports can likely access it through other ... >>> ports and even start PcAwHost and then has access to your company data ... and the company data is now available to outsiders. ... PcAnywhere security ...
      (comp.security.firewalls)
    • Re: I have some questions about telnet/telnetd/libtelnet/tn3270 and why FreeBSD is different than ot
      ... ¥ I've had a license to punt this to ports for _years_. ... Rambler produced hits logged several years before; ... version of telnet. ... Things like 3270 terminals are ...
      (freebsd-questions)