Re: 2008 TS Web
- From: "Rob Leitman [MS]" <robleit@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Apr 2008 14:48:06 -0700
I'm not sure I understand what you're describing. I'll go over how things are supposed to work, and you can explain where there's a mismatch.
TS Web Access is a website that shows the list of RemoteApp programs:
IE < -- > IIS /TSWA
(port 80)
(can be reconfigured to use HTTPS / port 443)
When you publish a RemoteApp program, you can configure it to use TS Gateway, or not.
If there's no TS Gateway, and you click on a RemoteApp, you get:
IE/MsTscAx <--> TS
(port 3389)
If there is a TS Gateway, and you click on a RemoteApp, you get:
IE/MsTscAx <--> TS Gateway <--> TS
(port 443) (port 3389)
Does that help?
Rob
"Richard@dt" <Richarddt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:09E60A76-F8B2-4B55-AEF0-7E8FE123768C@xxxxxxxxxxxxxxxx
Hi
I have depoyed a 2008 Server, and have configured TS Web access and TS
Gateway.
According to the product notes, 2008 should (PAT) https from the front end
to 3389 at the back-end. When I look at the packet captures, we authenticate
on 443, but use 3389 to the back-end TS Server?
I have searched high and low at MS and via Google, and so far nothing? I
must be doing something fundamentally wrong?
Any help gratefully appreciated
.
- Follow-Ups:
- Re: 2008 TS Web
- From: Richard@dt
- Re: 2008 TS Web
- References:
- 2008 TS Web
- From: Richard@dt
- 2008 TS Web
- Prev by Date: Re: determining machine name
- Next by Date: RE: Installing Software and Permissions
- Previous by thread: 2008 TS Web
- Next by thread: Re: 2008 TS Web
- Index(es):
Relevant Pages
|