OK, we know how to open ports tcp 5631 and udp 5632, and we can connect
to PCAnywhere hosts behind LRP-CD -- from the Internet in general.
However, specifically, when site A is behind LRP-CD(A) and site B is
behind LRP-CD(B) and we are inside site B, we *cannot* connect to
PCAnywhere hosts
OK, we know how to open ports tcp 5631 and udp 5632, and we can connect
to PCAnywhere hosts behind LRP-CD -- from the Internet in general.
However, specifically, when site A is behind LRP-CD(A) and site B is
behind LRP-CD(B) and we are inside site B, we *cannot* connect to
PCAnywhere hosts
Charles Steinkuehler wrote:
OK, we know how to open ports tcp 5631 and udp 5632, and we can connect
to PCAnywhere hosts behind LRP-CD -- from the Internet in general.
However, specifically, when site A is behind LRP-CD(A) and site B is
behind LRP-CD(B) and we are inside site B, we
Charles Steinkuehler wrote:
Check your firewall logs on both LRP-CD systems looking for denied
packets.
I'd bet you're dropping some traffic PCAnywhere needs to function...
Yes, our first thoughts also -- however, neither side has anything in
/var/log/kern.log . . .
Only
Dan wrote:
Anybody tried VNC?
Yes. I have tried VNC to both Windows and Linux machines thru my system
(also based on the LRP-CD scripts). It works very well, but provides no
security on its own. I'd like to hear other's comments on the best way to
configure external access to internal
Michael D. Schleif wrote:
Let's recap:
OK: wintel(A) - PCAnywhere - Internet - LRP-CD(B) - wintel(B)
NOT: wintel(A) - PCAnywhere - LRP-CD(A) - Internet - LRP-CD(B) -
wintel(B)
So, it appears that there is something other than ports tcp 5631 and udp
5632 required -- on the
