Terminal Services over port 80 over HTTPS only

[Guest sameer]

Hi,

 

Environment : windows Server 2000 with Terminal server

 

 

My desktop application is installed on Windows 2000 Terminal server and is

being used by the clients over the internet using Remote Desktop client on

their machines. For new clients i would request their IT department to open

up the terminal services port in their firewall and boom the client uses the

application over remote desktop. but with this new client the only port they

can have open is port 80 (which is not a problem since i can change remote

desktop server to listen on port 80 instead of the default remote desktop

port since my server does not have IIS) but the main problem is that their

firewall does not allow Remote desktop protocol ( i.e the protocol that

Remote Desktop uses), they want me to configure my application so that it is

accessible over httpS protocol, so the question is

 

1. is there any way i can configure Remote desktop server ( i can even

upgrade to windows server 2003 or 2008 as well) with even a thrid party

software ( if any) to work on only HTTPS protocol only.

 

2. I heard that windows 2008 does have something like that, can anyone

confirm this.

 

3. Is there any other product in the market ( citrix ?) which allows mutiple

session like Remote desktop over Port 80 using HTTPS only.

 

 

i am in a pretty frustrating situation , any help is appreicated.

 

 

thanks

 

Sameer

[Guest Patrick Rouse]

RE: Terminal Services over port 80 over HTTPS only

 

All of the solutions I'm aware of, inclusing our Virtual Access Suite, Citrix

Secure Gateway and 2008 TS can connect over SSL on port 443, which is almost

always open. Although I'm sure someone does it, I've never see a company

that restricts access to all HTTPS websites.

 

If you want more information on this, feel free to contact me at

MyFirstName.MyLastName@quest.com

 

 

--

Patrick C. Rouse

Microsoft MVP - Terminal Server

SE, West Coast USA & Canada

Quest Software, Provision Networks Division

Virtual Client Solutions

http://www.provisionnetworks.com

 

 

"sameer" wrote:

>

>

> Hi,

>

> Environment : windows Server 2000 with Terminal server

>

>

> My desktop application is installed on Windows 2000 Terminal server and is

> being used by the clients over the internet using Remote Desktop client on

> their machines. For new clients i would request their IT department to open

> up the terminal services port in their firewall and boom the client uses the

> application over remote desktop. but with this new client the only port they

> can have open is port 80 (which is not a problem since i can change remote

> desktop server to listen on port 80 instead of the default remote desktop

> port since my server does not have IIS) but the main problem is that their

> firewall does not allow Remote desktop protocol ( i.e the protocol that

> Remote Desktop uses), they want me to configure my application so that it is

> accessible over httpS protocol, so the question is

>

> 1. is there any way i can configure Remote desktop server ( i can even

> upgrade to windows server 2003 or 2008 as well) with even a thrid party

> software ( if any) to work on only HTTPS protocol only.

>

> 2. I heard that windows 2008 does have something like that, can anyone

> confirm this.

>

> 3. Is there any other product in the market ( citrix ?) which allows mutiple

> session like Remote desktop over Port 80 using HTTPS only.

>

>

> i am in a pretty frustrating situation , any help is appreicated.

>

>

> thanks

>

> Sameer

[Guest sameer]

RE: Terminal Services over port 80 over HTTPS only

 

Patrick, do you mean that they go only over 443 using HTTPS protocol and not

RDP protocol, again reason why i am being so specific is because client';s

firewall does not allow RDP protocol calls due to which Terminal services

does not work.

 

thanks

 

"Patrick Rouse" wrote:

> All of the solutions I'm aware of, inclusing our Virtual Access Suite, Citrix

> Secure Gateway and 2008 TS can connect over SSL on port 443, which is almost

> always open. Although I'm sure someone does it, I've never see a company

> that restricts access to all HTTPS websites.

>

> If you want more information on this, feel free to contact me at

> MyFirstName.MyLastName@quest.com

>

>

> --

> Patrick C. Rouse

> Microsoft MVP - Terminal Server

> SE, West Coast USA & Canada

> Quest Software, Provision Networks Division

> Virtual Client Solutions

> http://www.provisionnetworks.com

>

>

> "sameer" wrote:

>

> >

> >

> > Hi,

> >

> > Environment : windows Server 2000 with Terminal server

> >

> >

> > My desktop application is installed on Windows 2000 Terminal server and is

> > being used by the clients over the internet using Remote Desktop client on

> > their machines. For new clients i would request their IT department to open

> > up the terminal services port in their firewall and boom the client uses the

> > application over remote desktop. but with this new client the only port they

> > can have open is port 80 (which is not a problem since i can change remote

> > desktop server to listen on port 80 instead of the default remote desktop

> > port since my server does not have IIS) but the main problem is that their

> > firewall does not allow Remote desktop protocol ( i.e the protocol that

> > Remote Desktop uses), they want me to configure my application so that it is

> > accessible over httpS protocol, so the question is

> >

> > 1. is there any way i can configure Remote desktop server ( i can even

> > upgrade to windows server 2003 or 2008 as well) with even a thrid party

> > software ( if any) to work on only HTTPS protocol only.

> >

> > 2. I heard that windows 2008 does have something like that, can anyone

> > confirm this.

> >

> > 3. Is there any other product in the market ( citrix ?) which allows mutiple

> > session like Remote desktop over Port 80 using HTTPS only.

> >

> >

> > i am in a pretty frustrating situation , any help is appreicated.

> >

> >

> > thanks

> >

> > Sameer

[Guest Jonathan Wood]

Re: Terminal Services over port 80 over HTTPS only

 

You could implement an SSL-VPN solution. First a VPN connection is setup

over HTTPS/SSL, next RDP connections are tunneled through the VPN tunnel.

Firewalls will only see the SSL packets passing through and not the RDP

packets embedded in them. A nice free and open-source solution is

SSL-Explorer:

 

http://sourceforge.net/projects/sslexplorer/

 

- Jonathan

 

 

"sameer" <sameer@discussions.microsoft.com> wrote in message

news:20C35F7B-04DC-44B7-8FF0-038E55C36A07@microsoft.com...

> Patrick, do you mean that they go only over 443 using HTTPS protocol and

> not

> RDP protocol, again reason why i am being so specific is because client';s

> firewall does not allow RDP protocol calls due to which Terminal services

> does not work.

>

> thanks

>

> "Patrick Rouse" wrote:

>

>> All of the solutions I'm aware of, inclusing our Virtual Access Suite,

>> Citrix

>> Secure Gateway and 2008 TS can connect over SSL on port 443, which is

>> almost

>> always open. Although I'm sure someone does it, I've never see a company

>> that restricts access to all HTTPS websites.

>>

>> If you want more information on this, feel free to contact me at

>> MyFirstName.MyLastName@quest.com

>>

>>

>> --

>> Patrick C. Rouse

>> Microsoft MVP - Terminal Server

>> SE, West Coast USA & Canada

>> Quest Software, Provision Networks Division

>> Virtual Client Solutions

>> http://www.provisionnetworks.com

>>

>>

>> "sameer" wrote:

>>

>> >

>> >

>> > Hi,

>> >

>> > Environment : windows Server 2000 with Terminal server

>> >

>> >

>> > My desktop application is installed on Windows 2000 Terminal server and

>> > is

>> > being used by the clients over the internet using Remote Desktop client

>> > on

>> > their machines. For new clients i would request their IT department to

>> > open

>> > up the terminal services port in their firewall and boom the client

>> > uses the

>> > application over remote desktop. but with this new client the only port

>> > they

>> > can have open is port 80 (which is not a problem since i can change

>> > remote

>> > desktop server to listen on port 80 instead of the default remote

>> > desktop

>> > port since my server does not have IIS) but the main problem is that

>> > their

>> > firewall does not allow Remote desktop protocol ( i.e the protocol that

>> > Remote Desktop uses), they want me to configure my application so that

>> > it is

>> > accessible over httpS protocol, so the question is

>> >

>> > 1. is there any way i can configure Remote desktop server ( i can even

>> > upgrade to windows server 2003 or 2008 as well) with even a thrid party

>> > software ( if any) to work on only HTTPS protocol only.

>> >

>> > 2. I heard that windows 2008 does have something like that, can anyone

>> > confirm this.

>> >

>> > 3. Is there any other product in the market ( citrix ?) which allows

>> > mutiple

>> > session like Remote desktop over Port 80 using HTTPS only.

>> >

>> >

>> > i am in a pretty frustrating situation , any help is appreicated.

>> >

>> >

>> > thanks

>> >

>> > Sameer