Date: Tue, 5 Dec 2000 11:41:06 -0800 From: George Chung <gchung@microsoft.com> To: Joe Schwartz <rjoe@sierrahill.com>, freebsd-net@FreeBSD.ORG Subject: RE: pc anywhere & natd Message-ID: <3393DB26DFC047419FEDA98FA76479110179A227@red-msg-05.redmond.corp.microsoft.com>
next in thread | raw e-mail | index | archive | help
i don't know if this helps, but...
i have the exact same situation. but i use ssh port forwarding to get to the
private machine on the two pcanywhere ports.
i wasn't able to get this to work until i found an obscure knowledge base
article on symantec's site on how to get pcanywhere to use tcp instead of
udp on those ports.
-----Original Message-----
From: Joe Schwartz [mailto:rjoe@sierrahill.com]
Sent: Tuesday, December 05, 2000 9:16 AM
To: freebsd-net@FreeBSD.ORG
Subject: pc anywhere & natd
There is a PC running pcanywhere with a public IP address
attempting to get to a PC on a private network. The FreeBSD
server is running natd and I used the option -redirect_address
to attempt a conduit through the FreeBSD machine to the PC on the
private net. The PC on the public net pointed the pcanywhere client
to the IP public IP address of the FreeBSD machine.
It didn't work.
Should I expect it to?
Suggestions?
Alternate approaches?
/usr/sbin/natd -redirect_address 192.168.1.54 24.??.??.??? -n vx0
24.??.??.??? 192.168.1.??
public natd private
PC ------------ FreeBSD ----------------PC
Thanks,
Joe
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3393DB26DFC047419FEDA98FA76479110179A227>