Tunneling via IIS

I have installed an application on a Windows server 2003 that has a web based
admin interface, but it's without security. I would like to access this admin
interface from outside the 2003 box.

Is it possible to tunnel web request via IIS in such a way that I will be
able to access the admin interface via IIS and to use HTTPS and normal IIS
authentication?

Example:
The admin interface is available locally at http://127.0.0.1:8888/index.htm
Externally I would use the address https://appname.myserver/index.htm
where appname.myserver is a IIS website, IIS would then forward all requests
to the 127.0.0.1:8888 website and tunnel back the html reply to my browser.

Re: Tunneling via IIS

On Jul 1, 1:20 am, Tim wrote:
> I have installed an application on a Windows server 2003 that has a web based
> admin interface, but it's without security. I would like to access this admin
> interface from outside the 2003 box.
>
> Is it possible to tunnel web request via IIS in such a way that I will be
> able to access the admin interface via IIS and to use HTTPS and normal IIS
> authentication?
>
> Example:
> The admin interface is available locally athttp://127.0.0.1:8888/index.htm
> Externally I would use the addresshttps://appname.myserver/index.htm
> where appname.myserver is a IIS website, IIS would then forward all requests
> to the 127.0.0.1:8888 website and tunnel back the html reply to my browser.


You can do that with IIS, but IIS does not come with any native
extensibility module to do that.

The Microsoft ISA Server product provides that functionality by
default.

I do not understand why you need to do all this tunneling at all. Just
add SSL Certificate to the admin website and expose that as the
https://appname.myserver IP address. Or are you trying to compensate
for a limitation within the web based admin interface -- which would
be odd since an application shouldn't care what port nor whether it is
running over HTTP/HTTPS unless the application is specifically trying
to limit its functionality and you are tring to compensate for it.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Tunneling via IIS

"David Wang" wrote:

> On Jul 1, 1:20 am, Tim wrote:
> > I have installed an application on a Windows server 2003 that has a web based
> > admin interface, but it's without security. I would like to access this admin
> > interface from outside the 2003 box.
> >
> > Is it possible to tunnel web request via IIS in such a way that I will be
> > able to access the admin interface via IIS and to use HTTPS and normal IIS
> > authentication?
> >
> > Example:
> > The admin interface is available locally athttp://127.0.0.1:8888/index.htm
> > Externally I would use the addresshttps://appname.myserver/index.htm
> > where appname.myserver is a IIS website, IIS would then forward all requests
> > to the 127.0.0.1:8888 website and tunnel back the html reply to my browser.
>
>
> You can do that with IIS, but IIS does not come with any native
> extensibility module to do that.
>
> The Microsoft ISA Server product provides that functionality by
> default.
>
> I do not understand why you need to do all this tunneling at all. Just
> add SSL Certificate to the admin website and expose that as the
> https://appname.myserver IP address. Or are you trying to compensate
> for a limitation within the web based admin interface -- which would
> be odd since an application shouldn't care what port nor whether it is
> running over HTTP/HTTPS unless the application is specifically trying
> to limit its functionality and you are tring to compensate for it.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>

Just to clearify about the admin website; it's not a IIS site, it's a
service that has implemented it's own web interface on a TCP port without any
use of IIS at all, so it's not possible to add security to the site as it
would had it been an IIS site.