remote desktop/remote web connection

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

jack c.
hey mate:what is the difference is there a difference between remote desktop
connection and remote desktop web connection?please explain.
thanks,jack
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Remote desktop Connection:

Install executable on remote system (need to have permission to do this, of
course), executable contacts the host system, and off you go.

Remote Desktop Web Connection:

1) install (and harden! and patch) IIS on the host system, including the
RDWC piece.
2) open ports in the firewall for both IIS and Remote Desktop (80 and 3389,
TCP, by default)
3) From a remote system, use Internet Explorer to connect to the host's IIS.
This will upload a signed ActiveX control (remote system must be configured
to allow such an operation, and the user must assent to the installation)
ActiveX control then contacts the host over port 3389 and off you go.

The Web Connection method has significantly more complexity than the simple
Remote Desktop connection. It doesn't involve any advance preparation at
the remote end of things, but if the remote end is locked down (in a
corporate or educational setting)--neither method should work.


"jack c." <jackc@discussions.microsoft.com> wrote in message
news:1EC6FAD2-16AA-4990-B617-8F4B48A8C537@microsoft.com...
> jack c.
> hey mate:what is the difference is there a difference between remote
> desktop
> connection and remote desktop web connection?please explain.
> thanks,jack
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

FYI to 'jack'... The web based method can not be used with a PocketPC, AFAIK...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

"Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
news:O9MoWN91EHA.2600@TK2MSFTNGP09.phx.gbl...
> Remote desktop Connection:
>
> Install executable on remote system (need to have permission to do this, of course), executable
> contacts the host system, and off you go.
>
> Remote Desktop Web Connection:
>
> 1) install (and harden! and patch) IIS on the host system, including the RDWC piece.
> 2) open ports in the firewall for both IIS and Remote Desktop (80 and 3389, TCP, by default)
> 3) From a remote system, use Internet Explorer to connect to the host's IIS. This will upload a
> signed ActiveX control (remote system must be configured to allow such an operation, and the user
> must assent to the installation) ActiveX control then contacts the host over port 3389 and off you
> go.
>
> The Web Connection method has significantly more complexity than the simple Remote Desktop
> connection. It doesn't involve any advance preparation at the remote end of things, but if the
> remote end is locked down (in a corporate or educational setting)--neither method should work.
>
>
> "jack c." <jackc@discussions.microsoft.com> wrote in message
> news:1EC6FAD2-16AA-4990-B617-8F4B48A8C537@microsoft.com...
>> jack c.
>> hey mate:what is the difference is there a difference between remote desktop
>> connection and remote desktop web connection?please explain.
>> thanks,jack
>
>