Connect to Terminal Server behind ISA Firewall with private IP

I have a problem connecting to a Windows 2000 Terminal Server in Admin mode.  This server is behind an ISA 2000 firewall server.  The server is configured with a static private IP address (i.e. 192.168.0.200).

On my LAN, I can connect fine because I’m on the same private IP address subnet.  However, I cannot figure out how to connect to this terminal server over the Internet because of the private IP address problem.  

Is there any way I can make this connection possible without resorting to assigning my Terminal server with a public IP?  The port number 3389 is open on the ISA server for terminal services.  

Just a thought; can I somehow map the terminal server’s private IP to a public IP address on the ISA and route any connection to this public IP to the terminal server?  Can this be done with RAS routing feature?

I also tried pcAnywhere 10.5 and ran into the same problem.

Thanks for any tips.
speedwayAsked:
Who is Participating?
 
Gabe_RiveraConnect With a Mentor Commented:
Whoops, forgot to put this article on there too.

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q294720
0
 
SysExpertCommented:
Yes you should be able.
For PC anywhere

pcAnywhere uses either of two sets of ports depending on the version of pcAnywhere you are using. One   set uses ports 65301 and 22. The second set uses the registered ports 5631 and 5632.

               2.0 tcp 65301 udp 22
               7.0 tcp 65301 udp 22
               7.50 tcp 65301 udp 22
               7.51 tcp 65301 udp 22
               CE tcp 65301 udp 22
               7.52 tcp 5631 udp 5632
               8.x tcp 5631 udp 5632
               9.0 tcp 5631 udp 5632
               9.2 tcp 5631 udp 5632

How to change the IP ports that pcAnywhere 10 uses

                   Situation:
 Some firewalls allow only a single pcAnywhere host to use an IP port. Additional pcAnywhere hosts  behind that firewall must use different ports. You want to know how to change these ports.
                  Situation:
 Some firewalls allow only a single pcAnywhere host to use an IP port. Additional pcAnywhere hosts  behind that firewall must use different ports. You want to know how to change these ports.
http://service1.symantec.com/SUPPORT/pca.nsf/docid/2001021417112312?OpenDocument
How to use pcAnywhere with a Cable or ADSL Modem
How to use pcAnywhere with a Dynamic IP Address or Domain Name Service
http://service1.symantec.com/SUPPORT/pca.nsf/docid/2001041616061412?OpenDocument
pcAnywhere and Network Address Translation
http://service1.symantec.com/SUPPORT/pca.nsf/e1aefd06d28fcec6852569e5004cef32/c22361b63e2f7bfe88256766006136e6?OpenDocument

I hope this helps !
0
 
SysExpertCommented:
ALso

http://service4.symantec.com/SUPPORT/pca.nsf/e1aefd06d28fcec6852569e5004cef32/e8421bce325eb66485256b3000697314?OpenDocument

Similarly , you should be able to get TS working.

I would check the MS site for specific info.

I hope this helps !
 
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Gabe_RiveraCommented:
Hey Speedway, I had this same problem. Check this out, I think it should be what you're looking for..

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q275210
0
 
speedwayAuthor Commented:
Thank you, Gabe.  That article contained exactly what I was looking for.  I knew I had to map the external IP on the ISA server to the internal IP on the terminal server.  Just didn’t know how to do it in the ISA console.  I actually searched Microsoft’s knowledge base all over the place.  Don’t know how I missed it.  Guess just didn’t type the right words.  Thanks a million.  Well, actually, 200 points.

SysExpert, thanks for the Symantec links.  I had already read all those information when I was trying to get pcAnywhere to work.  I knew about the ports issue.  Your second message would work if I was trying to install pcAnywhere on the ISA server.  Actually, that would be easy since the ISA server has public IP address.  I already have terminal services working on the ISA server.

Now I have another problem.  I tried to create a new Server Publishing Rule in the ISA manage MMC.  On the second screen, it asked me for the internal address of the internal server and external address on the ISA server.  I entered the internal address without problem.  However, I could not enter in or find the external address from the ISA server.  I clicked the browse button and there was nothing (no IP listed in the browse box).  How could that be?  I have 6 public IPs assigned to the external network adaptor with 3 of them free.  At the very least 1 IP should show up since I know the ISA server is working fine at routing internet services for our LAN.  Is this a bug or am I missing something?
0
 
speedwayAuthor Commented:
Solved my problem.  I needed to reboot in order for the public IP I just added to the external adaptor to show up in the server publishing wizard.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.