Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Term Serv connection - help

0 views
Skip to first unread message

Dan Dotson

unread,
Oct 8, 2003, 6:22:59 AM10/8/03
to
I was hoping for some help. I am trying to get to term serv on our W2K
server from the internet for remote admin. We go through an ISA server for
security. The organization that provides the internet service currently
term serves into their ISA server, then runs the term serv client on the ISA
server to connect to any other machine on the inside of the network. They
decided that they did not want to grant me access to the ISA server so that
I could reach our server.

They host our website. Is there any way that they could forward a request
like www.organization.com/terminalservices to our server? Or what about the
ActiveX version? If I put up a page with that activeX control, could I get
to our server?

The gist of the question is, how do I get my server which is on the inside
of an ISA protected network?

Thanks.


Matthew Harris [MVP]

unread,
Oct 8, 2003, 4:52:33 PM10/8/03
to
Hmm...so does your computer have a private IP address (the
ISA server is acting like a firewall/proxy server)?

If so, are those ISA admins willing to forward you a
specific port? If they are, you can change the port that
terminal services works on, and then connect to that
custom port on the ISA server, which the ISA server will
then forward to the port on your computer.

-M

>.
>

Dan Dotson

unread,
Oct 8, 2003, 5:38:18 PM10/8/03
to
Our server does have a private IP address. ISA server is acting like a
firewall/proxy.

So I simply tell my server to listen for terminal services requests on that
new port?

Dan

"Matthew Harris [MVP]" <har...@crocker.ucdavis.edu> wrote in message
news:04be01c38dde$18aea260$a301...@phx.gbl...

Matthew Harris [MVP]

unread,
Oct 8, 2003, 8:50:24 PM10/8/03
to
Yup..just change the port that TS listens on. But...this
assumes that the ISA admins will allow a port on their
firewall to be forewarded to your server.

An alternative is to have them forward port 3389 on a
different IP address assigned to the firewall. That's how
I do it. I have a main IP address on the firewall that
allows RDP access from the Internet to the firewall. The
firewall has been assigned numerous other IP addresses on
its external interface, so if I need to access a server on
the internal side, I just use a different IP address on
the firewall and forward port 3389 to the internal server.

-M

>.
>

Victor Davenport+

unread,
Oct 9, 2003, 8:46:12 AM10/9/03
to
Is there any way to tell the Microsoft remote Desktop
Connection to call the IP address and communicate on a
port other than 3389?
>.
>

Matthew Harris [MVP]

unread,
Oct 9, 2003, 2:34:03 PM10/9/03
to
Check this aticle out:

support.microsoft.com/default.aspx?scid=kb;en-
us;187623&Product=win2000

On the command line, type mstsc /?, it'll tell you how to
specify the port you are trying to connect to.

-M

>.
>

0 new messages