Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PC Anywhere Behind ISA Server

Status
Not open for further replies.

barrycork

IS-IT--Management
Jul 25, 2002
53
GB
I am trying to connect from the Internet to a client PC in our network using PC Anywhere. I have done the following;

Defined the following protocol definitions in ISA;

PC-Anywhere-1 : 5631 TCP - Inbound
PC-Anywhere-2 : 5621 UDP - Receive-Send
PC-Anywhere-3 : 5632 TCP - Inbound
PC-Anywhere-4 : 5632 UDP - Receive-Send

Created 4 server publishing rules - one for each protocol definition entering the internal IP address of the PC Anywhere client to be controlled and the external address of the ISA server on each occasion.

As an initial test I then position a PC Anywhere control PC between my ISA server and my internet router and attempt a connection to the PC Anywhere client through the ISA server (the control PC is on the same IP address range as the ISA external NIC and the Internet router and can ping each). To do this I tell PC Anywhere to connect to the external IP of the ISA server which should route the request (if my understanding is correct) to the PC Anywhere client on my internal network. I then receive the message 'Timeout looking for connection'

Any suggestion on where I am going wrong or how I might best troubleshoot this issue would be much appreciated.

Thanks in advance.

Barry

 
Issue an NETSTAT -NA and check that ISA is actually listening for incoming traffic on those ports.

If so, next step would be to start NETMON on your Control PC, and ISA (on both external and internal interfaces) to monitor the packets. At this stage, it's important to check that your PC Anywhere client is actually requesting the ports you are listening on and that these requests are being received by your control pc.

Cheers
Knutern
 
Working now.

My problem was, that the client was not configured as a NAT Client (means I had the ISA Client program installed instead of just setting the default gateway to the ISA servers address).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top