RE: PCAnywhere

  • From: "Nef Perez" <nperez@xxxxxxxxxxxxxxx>
  • To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
  • Date: Wed, 8 Oct 2003 09:47:07 -0400

I've have added the 2 protocols as you described, but I still have the
same issue.
Only by having a protocol rule that allows All IP traffic am I able to
remote control the 'public' PC via PCAnywhere, which is not a very
secure solution.

Any other thoughts?


 

 


-----Original Message-----
From: William Robertson [mailto:robertson.william@xxxxxxxxxxxxxx] 
Sent: Friday, October 03, 2003 12:45 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: PCAnywhere

http://www.ISAserver.org


Hi there

I have the reverse of what you want, but it should still apply...

I have server-published a workstation for PCAnywhere access on the
following
protocols:
TCP 5631 & TCP 5632
UDP 5631 & UDP 5632

These are the only 4 protocols that I need open. I see that you don't
have a
UDP protocol rule for 5631 & 5632, so maybe you can give this a bash?

Cheers
William R.



-----Original Message-----
From: nperez@xxxxxxxxxxxxxxx [mailto:nperez@xxxxxxxxxxxxxxx] 
Sent: 02 October 2003 22:04 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] PCAnywhere

http://www.ISAserver.org


Here's my dilemna:
I have a remote PC with a public address the I need to remote control
via
PC Anywhere.
Here are my protocols rules:

PCAnywhere
        Description : PCAnywhere Software Access
        Initial Connection Port Number : 5633
        Initial Protocol Type : TCP
        Initial Direction : Inbound
        Secondary Connections:
        ** Port Range : 5630 - 5634
           Protocol Type : TCP
           Direction : Inbound
        ** Port Range : 5630 - 5634
           Protocol Type : TCP
           Direction : Outbound
        ** Port Range : 5634 - 5634
           Protocol Type : UDP
           Direction : Receive and Then Send
        ** Port Range : 5634 - 5634
           Protocol Type : UDP
           Direction : Send and Then Receive
Then I have another protocol rule that allows all IP traffic. I have to
enable this rule in order to access the PC via PCAnywhere. When I
disable
this rule (All IP) I cannot access the PC via PCAnywhere.
It seems like there is something wrong with my PCAnywhere rule. Does
anyone what it may be?

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
robertson.william@xxxxxxxxxxxxxx
To unsubscribe send a blank email to
$subst('Email.Unsub')

---------------------------------------------------------------------
Everything in this e-mail and attachments relating to the official 
business of Columbus Stainless is proprietary to the company. It is 
confidential, legally privileged and protected by law. Columbus 
Stainless does not own and endorse any other content. Views and 
opinions are those of the sender unless clearly stated as being that 
of Columbus Stainless. The person addressed in the e-mail is the sole 
authorised recipient.  Please notify the sender immediately if it has 
unintentionally reached you and do not read, disclose or use the 
content in any way. Whilst all reasonable steps are taken to ensure 
the accuracy and integrity of information and data transmitted 
electronically and to preserve the confidentiality thereof, no 
liability or responsibility whatsoever is accepted if information or 
data is,for whatever reason, corrupted or does not reach its intended
destination.
---------------------------------------------------------------------

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=3Disalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=3DFAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
nperez@xxxxxxxxxxxxxxx
To unsubscribe send a blank email to
$subst('Email.Unsub')



Other related posts: