windows 2003 server tsweb

Hi,

I have a question of the availability of the Remote
Desktop Web connection via the web. On my intranet I can
go to http://servername/tsweb/ and access the page and be
able to remotely connect to any computer on my network
but when I try to access this via the internet offsite I
can load http://www.something.com/tsweb/ but I cannot
connect to any of my clients. It says something about
cannot be located.

Here is my setup. I run Windows 2003 server with routing
and remote access configured and a dhcp server within
2003 also. Since it assigns non-routable ip addresses is
this why my remote desktop web connection will not
connect to clients or do I have something configured
wrong. For this to work do I have to use REAL ip
addresses on my local LAN or is it a forwarding problem
of some sort. I have 3389 forwarded to my server and
connection via the client works fine but no dice on the
web connection.

Thanks
Gary

The external address is unable to resolve the internal
name. In order for you to get to your clients WS. You
first have to logon to the server and then start another
TS session to the clients.






>-----Original Message-----
>Hi,
>
>I have a question of the availability of the Remote
>Desktop Web connection via the web. On my intranet I
can
>go to http://servername/tsweb/ and access the page and
be
>able to remotely connect to any computer on my network
>but when I try to access this via the internet offsite I
>can load http://www.something.com/tsweb/ but I cannot
>connect to any of my clients. It says something about
>cannot be located.
>
>Here is my setup. I run Windows 2003 server with
routing
>and remote access configured and a dhcp server within
>2003 also. Since it assigns non-routable ip addresses
is
>this why my remote desktop web connection will not
>connect to clients or do I have something configured
>wrong. For this to work do I have to use REAL ip
>addresses on my local LAN or is it a forwarding problem
>of some sort. I have 3389 forwarded to my server and
>connection via the client works fine but no dice on the
>web connection.
>
>Thanks
>Gary
>.
>

There is no way to utilize the web interface though? For
this to work it would have to be real world ip's i take
it? Seems like they should have built a way into it so
clients could connect through the web interface because I
do not want to allow regular users to log on locally to
server and then connect again through the client to their
desktop. Seems they would have a way that would route
them to the correct desktop in the server.

>-----Original Message-----
>The external address is unable to resolve the internal
>name. In order for you to get to your clients WS. You
>first have to logon to the server and then start another
>TS session to the clients.
>
>
>
>
>
>
>>-----Original Message-----
>>Hi,
>>
>>I have a question of the availability of the Remote
>>Desktop Web connection via the web. On my intranet I
>can
>>go to http://servername/tsweb/ and access the page and
>be
>>able to remotely connect to any computer on my network
>>but when I try to access this via the internet offsite
I
>>can load http://www.something.com/tsweb/ but I cannot
>>connect to any of my clients. It says something about
>>cannot be located.
>>
>>Here is my setup. I run Windows 2003 server with
>routing
>>and remote access configured and a dhcp server within
>>2003 also. Since it assigns non-routable ip addresses
>is
>>this why my remote desktop web connection will not
>>connect to clients or do I have something configured
>>wrong. For this to work do I have to use REAL ip
>>addresses on my local LAN or is it a forwarding problem
>>of some sort. I have 3389 forwarded to my server and
>>connection via the client works fine but no dice on the
>>web connection.
>>
>>Thanks
>>Gary
>>.
>>
>.
>