Remote Desktop Web Connection

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Could you give details on how it doesn't work - no web page, or web page and
no TS connection? And what ports did you redirect to where?

Jason Rosolowski wrote:
> I have a Terminal Server Farm that I want to give our users access to
> from the internet.
>
> What do you think is the best way to accomplish this?
>
> Here's the idea I was hoping to run with, but it's been giving me some
> problems. I was going to put a Windows 2003 with IIS 6 Web Server in
> our DMZ with the "Remote Desktop Web Connection" software from
> Microsoft on it. Well, I have most of it working. I opened up, what I
> think are the proper ports from the DMZ->Internal Network and also from
> the External Network->DMZ. I can get it to work fine from our Internet
> Network. Brings up the page, I put the server name I would like to
> connect to, and it connects. When I try the same thing from the
> External Network (the internet), it won't connect. The only thing I
> can think of is it might be a DNS issue. I was hoping the server in
> the DMZ would resolve the addresses, as that server is pointed to our
> Internal Network DNS server.
>
> Anyone have ideas about this? Also, is there a better solution? We'd
> like to allow access to them from virtually anywhere, that way, if one
> of our users is at a kiosk, they will still be able to get to the TS
> Farm.

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Jason Rosolowski wrote:
> With some help from an outside source, I think I've figured out my
> problem.
>
> The goal was to have the Terminal Server traffic flow through our DMZ
> and then into the Internal network. Here's my theory. The ActiveX
> control that gets downloaded from the Remote Desktop Web Connection
> doesn't actually run through the web server after it's downloaded, it
> just trys to connect directly to the Terminal Server. So basically, I
> would need to have port 3389 open from the External network to our
> Internal network for the ActiveX control to work, which would defeat
> the purpose.

Absolutely correct. The control is essentially a "portable" TS client; all
the web server does is hand it to you. Connection otherwise is standard TS,
direct client<->communication.

> We are looking at some alternate ways to do this, including a Citrix
> solution. We're not sure how we are going to go yet though.
>
> Thank you!
> Jason Rosolowski
> "Alex K. Angelopoulos [MVP]" <aka-at-mvps-dot-org> wrote in message
> news:%23hELPh1eEHA.3556@TK2MSFTNGP12.phx.gbl...
>> Could you give details on how it doesn't work - no web page, or web
>> page and no TS connection? And what ports did you redirect to where?
>>
>> Jason Rosolowski wrote:
>>> I have a Terminal Server Farm that I want to give our users access to
>>> from the internet.
>>>
>>> What do you think is the best way to accomplish this?
>>>
>>> Here's the idea I was hoping to run with, but it's been giving me some
>>> problems. I was going to put a Windows 2003 with IIS 6 Web Server in
>>> our DMZ with the "Remote Desktop Web Connection" software from
>>> Microsoft on it. Well, I have most of it working. I opened up, what I
>>> think are the proper ports from the DMZ->Internal Network and also
>>> from the External Network->DMZ. I can get it to work fine from our
>>> Internet Network. Brings up the page, I put the server name I would
>>> like to connect to, and it connects. When I try the same thing from
>>> the External Network (the internet), it won't connect. The only
>>> thing I can think of is it might be a DNS issue. I was hoping the
>>> server in the DMZ would resolve the addresses, as that server is
>>> pointed to our Internal Network DNS server.
>>>
>>> Anyone have ideas about this? Also, is there a better solution? We'd
>>> like to allow access to them from virtually anywhere, that way, if one
>>> of our users is at a kiosk, they will still be able to get to the TS
>>> Farm.