TSWeb and TS Gateway

  • Thread starter Thread starter RandyH
  • Start date Start date
R

RandyH

I understand TS Gateway transmits RDP traffic over port 443. So I
forwarded port 443 to my TSGateway Server and RDP doesn't work.

As soon as I forwarded port 3389, RDP started working. . .

???


Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389 need
opened to that server?

tia,
RandyH
 
Did you obtain an SSL certificate for your TS Gateway server?

Windows Server 2008 TS Gateway Server Step-by-Step Guide
http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
-2f22-462f-bcc6-72ad31713ddd1033.mspx

With TSweb, you need to open port 3389 to the TS (and port 80 to
the TSWeb server).
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
microsoft.public.windows.terminal_services:

> I understand TS Gateway transmits RDP traffic over port 443. So
> I forwarded port 443 to my TSGateway Server and RDP doesn't
> work.
>
> As soon as I forwarded port 3389, RDP started working. . .
>
> ???
>
>
> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
> need opened to that server?
>
> tia,
> RandyH
 
I did, I did...

So is that right? 3389 and 443 or 80 both need open to the server to
run tsweb?

I only have 443 open, should I open 80 too????

Thank you Vera!




Vera Noest [MVP] wrote:
> Did you obtain an SSL certificate for your TS Gateway server?
>
> Windows Server 2008 TS Gateway Server Step-by-Step Guide
> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>
> With TSweb, you need to open port 3389 to the TS (and port 80 to
> the TSWeb server).
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
> microsoft.public.windows.terminal_services:
>
>> I understand TS Gateway transmits RDP traffic over port 443. So
>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>> work.
>>
>> As soon as I forwarded port 3389, RDP started working. . .
>>
>> ???
>>
>>
>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>> need opened to that server?
>>
>> tia,
>> RandyH
>
 
If you're going through the TS Gateway, you don't need 3389 open.

Rob

"RandyH" <RHollaw@HOTmail.com> wrote in message
news:OXu783OxIHA.548@TK2MSFTNGP06.phx.gbl...
>I did, I did...
>
> So is that right? 3389 and 443 or 80 both need open to the server to run
> tsweb?
>
> I only have 443 open, should I open 80 too????
>
> Thank you Vera!
>
>
>
>
> Vera Noest [MVP] wrote:
>> Did you obtain an SSL certificate for your TS Gateway server?
>>
>> Windows Server 2008 TS Gateway Server Step-by-Step Guide
>> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
>> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>>
>> With TSweb, you need to open port 3389 to the TS (and port 80 to the
>> TSWeb server).
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
>> microsoft.public.windows.terminal_services:
>>> I understand TS Gateway transmits RDP traffic over port 443. So
>>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>>> work.
>>> As soon as I forwarded port 3389, RDP started working. . .
>>>
>>> ???
>>>
>>>
>>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>>> need opened to that server?
>>>
>>> tia,
>>> RandyH
>>
 
that's what I thought....thank you...

The TS Gateway is working internally, but not from the outside....

In allowed resources, I have allowed to all network resources.

Is there some DNS stuff I have to do?






Rob Leitman [MS] wrote:
> If you're going through the TS Gateway, you don't need 3389 open.
>
> Rob
>
> "RandyH" <RHollaw@HOTmail.com> wrote in message
> news:OXu783OxIHA.548@TK2MSFTNGP06.phx.gbl...
>> I did, I did...
>>
>> So is that right? 3389 and 443 or 80 both need open to the server to
>> run tsweb?
>>
>> I only have 443 open, should I open 80 too????
>>
>> Thank you Vera!
>>
>>
>>
>>
>> Vera Noest [MVP] wrote:
>>> Did you obtain an SSL certificate for your TS Gateway server?
>>>
>>> Windows Server 2008 TS Gateway Server Step-by-Step Guide
>>> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
>>> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>>>
>>> With TSweb, you need to open port 3389 to the TS (and port 80 to the
>>> TSWeb server).
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
>>> microsoft.public.windows.terminal_services:
>>>> I understand TS Gateway transmits RDP traffic over port 443. So
>>>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>>>> work.
>>>> As soon as I forwarded port 3389, RDP started working. . .
>>>>
>>>> ???
>>>>
>>>>
>>>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>>>> need opened to that server?
>>>>
>>>> tia,
>>>> RandyH
>>>
>
 
It's hard to tell what's stopping the connection, from what you describe.

It could be DNS, or a firewall, ...

Rob

"RandyH" <RHollaw@HOTmail.com> wrote in message
news:eh$zZFXxIHA.1936@TK2MSFTNGP04.phx.gbl...
> that's what I thought....thank you...
>
> The TS Gateway is working internally, but not from the outside....
>
> In allowed resources, I have allowed to all network resources.
>
> Is there some DNS stuff I have to do?
>
>
>
>
>
>
> Rob Leitman [MS] wrote:
>> If you're going through the TS Gateway, you don't need 3389 open.
>>
>> Rob
>>
>> "RandyH" <RHollaw@HOTmail.com> wrote in message
>> news:OXu783OxIHA.548@TK2MSFTNGP06.phx.gbl...
>>> I did, I did...
>>>
>>> So is that right? 3389 and 443 or 80 both need open to the server to
>>> run tsweb?
>>>
>>> I only have 443 open, should I open 80 too????
>>>
>>> Thank you Vera!
>>>
>>>
>>>
>>>
>>> Vera Noest [MVP] wrote:
>>>> Did you obtain an SSL certificate for your TS Gateway server?
>>>>
>>>> Windows Server 2008 TS Gateway Server Step-by-Step Guide
>>>> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
>>>> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>>>>
>>>> With TSweb, you need to open port 3389 to the TS (and port 80 to the
>>>> TSWeb server).
>>>> _________________________________________________________
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> TS troubleshooting: http://ts.veranoest.net
>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>
>>>> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
>>>> microsoft.public.windows.terminal_services:
>>>>> I understand TS Gateway transmits RDP traffic over port 443. So
>>>>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>>>>> work.
>>>>> As soon as I forwarded port 3389, RDP started working. . .
>>>>>
>>>>> ???
>>>>>
>>>>>
>>>>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>>>>> need opened to that server?
>>>>>
>>>>> tia,
>>>>> RandyH
>>>>
>>
 
When I have had this problem it has usually turned out to be the cert on the
TS Gateway not set properly. Only thing I have open to it is port 443 and it
works like a charm for TS GW or TS Apps

Roger Crawford
HTS

"Rob Leitman [MS]" <robleit@online.microsoft.com> wrote in message
news:eTX1f2nxIHA.5520@TK2MSFTNGP06.phx.gbl...
> It's hard to tell what's stopping the connection, from what you describe.
>
> It could be DNS, or a firewall, ...
>
> Rob
>
> "RandyH" <RHollaw@HOTmail.com> wrote in message
> news:eh$zZFXxIHA.1936@TK2MSFTNGP04.phx.gbl...
>> that's what I thought....thank you...
>>
>> The TS Gateway is working internally, but not from the outside....
>>
>> In allowed resources, I have allowed to all network resources.
>>
>> Is there some DNS stuff I have to do?
>>
>>
>>
>>
>>
>>
>> Rob Leitman [MS] wrote:
>>> If you're going through the TS Gateway, you don't need 3389 open.
>>>
>>> Rob
>>>
>>> "RandyH" <RHollaw@HOTmail.com> wrote in message
>>> news:OXu783OxIHA.548@TK2MSFTNGP06.phx.gbl...
>>>> I did, I did...
>>>>
>>>> So is that right? 3389 and 443 or 80 both need open to the server to
>>>> run tsweb?
>>>>
>>>> I only have 443 open, should I open 80 too????
>>>>
>>>> Thank you Vera!
>>>>
>>>>
>>>>
>>>>
>>>> Vera Noest [MVP] wrote:
>>>>> Did you obtain an SSL certificate for your TS Gateway server?
>>>>>
>>>>> Windows Server 2008 TS Gateway Server Step-by-Step Guide
>>>>> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
>>>>> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>>>>>
>>>>> With TSweb, you need to open port 3389 to the TS (and port 80 to the
>>>>> TSWeb server).
>>>>> _________________________________________________________
>>>>> Vera Noest
>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>
>>>>> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
>>>>> microsoft.public.windows.terminal_services:
>>>>>> I understand TS Gateway transmits RDP traffic over port 443. So
>>>>>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>>>>>> work.
>>>>>> As soon as I forwarded port 3389, RDP started working. . .
>>>>>>
>>>>>> ???
>>>>>>
>>>>>>
>>>>>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>>>>>> need opened to that server?
>>>>>>
>>>>>> tia,
>>>>>> RandyH
>>>>>
>>>
>
 
It was working, now it's not working.....grrrr.

I broke it!

thanks to all for the help...

Rob Leitman [MS] wrote:
> It's hard to tell what's stopping the connection, from what you describe.
>
> It could be DNS, or a firewall, ...
>
> Rob
>
> "RandyH" <RHollaw@HOTmail.com> wrote in message
> news:eh$zZFXxIHA.1936@TK2MSFTNGP04.phx.gbl...
>> that's what I thought....thank you...
>>
>> The TS Gateway is working internally, but not from the outside....
>>
>> In allowed resources, I have allowed to all network resources.
>>
>> Is there some DNS stuff I have to do?
>>
>>
>>
>>
>>
>>
>> Rob Leitman [MS] wrote:
>>> If you're going through the TS Gateway, you don't need 3389 open.
>>>
>>> Rob
>>>
>>> "RandyH" <RHollaw@HOTmail.com> wrote in message
>>> news:OXu783OxIHA.548@TK2MSFTNGP06.phx.gbl...
>>>> I did, I did...
>>>>
>>>> So is that right? 3389 and 443 or 80 both need open to the server
>>>> to run tsweb?
>>>>
>>>> I only have 443 open, should I open 80 too????
>>>>
>>>> Thank you Vera!
>>>>
>>>>
>>>>
>>>>
>>>> Vera Noest [MVP] wrote:
>>>>> Did you obtain an SSL certificate for your TS Gateway server?
>>>>>
>>>>> Windows Server 2008 TS Gateway Server Step-by-Step Guide
>>>>> http://technet2.microsoft.com/WindowsServer2008/en/library/722f3aa8
>>>>> -2f22-462f-bcc6-72ad31713ddd1033.mspx
>>>>>
>>>>> With TSweb, you need to open port 3389 to the TS (and port 80 to
>>>>> the TSWeb server).
>>>>> _________________________________________________________
>>>>> Vera Noest
>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>
>>>>> RandyH <RHollaw@HOTmail.com> wrote on 02 jun 2008 in
>>>>> microsoft.public.windows.terminal_services:
>>>>>> I understand TS Gateway transmits RDP traffic over port 443. So
>>>>>> I forwarded port 443 to my TSGateway Server and RDP doesn't
>>>>>> work.
>>>>>> As soon as I forwarded port 3389, RDP started working. . .
>>>>>>
>>>>>> ???
>>>>>>
>>>>>>
>>>>>> Also, to just use TSWeb, (ts/en-US/Desktops.aspx) does port 3389
>>>>>> need opened to that server?
>>>>>>
>>>>>> tia,
>>>>>> RandyH
>>>>>
>>>
>
 
Back
Top