Hi all,

Question?

Running pcAnywhere 10 as a host behind STN.  I know that pcAnywhere 10 uses
TCP 5631 and UDP 5632.

So, when I checked the box under  inbound services to pcAnywhere to IP
192.168.0.116 that wouldn't work.

So, then I used the selected inbound services and I checked two entries,
"tcp" 5631 and "udp" 5631 for port 192.168.0.116.  I also tried two entries,
"both" 5631 and "both" 5632 for port 192.168.0.116.  These didn't work.  But
they did appeared configured under the status settings.  (But I didn't try
four settings, "tcp" 5631, "tcp" 563, "udp" 5631, "udp" 5632 , could that
work?)

So, then I added to Manual override (which I found at some other Linux related
site relating to pcAnywhere: http://www.nerdsnetwork.com/IPAUTOFW.TXT)

ipautofw -A -r tcp 5631 5632 -h 192.168.0.116
ipautofw -A -r udp 5631 5632 -h 192.168.0.116

But this didn't work either.  Is the ipautofw the way to go and do I have
something wrong for this version of Linux.

I've done this with flowpoint routers using:

remote addserver <ip of PC> tcp 5631 5631 <remote name>
remote addserver <ip of PC> udp 5632 5632 <remote name>

and got multiple session of pcAnywhere running, by changing tcp and udp ports
routing to different IP.  One then changes this on the remote under (I think)
advanced button on properties of the remote item and you can selectively
control each machine from outside on the net.

One more thing, at this site (
http://w3.one.net/~jweirich/clug/tech-list/msg00482.html ) this fellow notes:

          I would like to post this for others to see.  Maybe you can tell me
where to
          post it.  I had to look at the tcp dumps from the IP address of the
machine
          that I was using for pcANYWHERE.  pcANYWHERE sends the request out
on port
          ssh and fulfills the request over udp 5632 and tcp 5631.  Here is
the
          addition to the script.

           # pcAnywhere
           /sbin/ipchains -A my-chain -p tcp -s 10.1.0.0/23 1024: -d 0.0.0.0/0
5631 -j
                            ACCEPT
           /sbin/ipchains -A my-chain -p udp -s 10.1.0.0/23 1024: -d 0.0.0.0/0
5632 -j
                            ACCEPT
           /sbin/ipchains -A my-chain -p udp -s 10.1.0.0/23 1024: -d 0.0.0.0/0
ssh -j
                            ACCEPT
           /sbin/ipchains -A my-chain -p tcp -s 10.1.0.0/23 1024: -d 0.0.0.0/0
ssh -j
                            ACCEPT

           Insert it before you DENY everything else.

I'm not too Linux aware, but does STN use ipchains and do I need these lines
in Manual Override too.

One more thing, when I followed the instructions on the STN site for
configuring dialpad (which didn't work at first), that worked just fine after
the changes.

Any help would be appreciated.

Thanks
Arnie

============================================================
Summertime Fun Sweepstakes-Win a Corvette Convertible!
You're automatically entered to WIN your own Corvette
Convertible when you activate your free MyPoints account!
http://click.topica.com/caaadewbz8Rp2bAfyICf/MyPoints
============================================================

--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
To Unsubscribe send email to: [EMAIL PROTECTED] 

==^================================================================
EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rp2.bAfyIC
Or send an email To: [EMAIL PROTECTED]
This email was sent to: [email protected]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================



Reply via email to