RE: RDP VS RWW to Terminal Server
- From: v-gzwang@xxxxxxxxxxxxxxxxxxxx (Guozhen Wang[MSFT])
- Date: Tue, 20 May 2008 07:16:54 GMT
Hello Laura,
Thank you for your post and thanks for Steve's great inputs.
My name is Gary Wang, and it is my pleasure to work with you on this issue!
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
You would like to know the differences between RDC and RWW.
If I have misunderstood your concerns please feel free to let me know.
Suggestion :
==============
I totally agree with Steve. Based on my understanding, connecting to
terminal server via RDC and RWW have very little difference. In my
opinion, RWW provides a more easier way for external user to get to remote
desktop. In SBS environment, we recommend that using RWW to connecting
terminal service instead of by RDC .
In previous versions of SBS, exposing internal network resources to remote
sites often required configuring the server for VPN or dial-up connections.
For example, if a remote user wanted to view an intranet site or make a
remote desktop connection to a workstation, the only option was to
establish a VPN or dial-up connection to the SBS server first. SBS 2003
includes the RWW is streamline and simplify use and administration of all
remote features. It provides a single access point that users can access
anytime, anywhere and from any device. All they have to do is remember a
single URL.
And the only difference I can think is that RWW and RDC using different
work methods. By RWW, the RDP proxy is used to connect to Terminal Servers
and Clients. TS Proxy is used to forward TS requests through a firewall on
TCP port 4125, in essence keeping the connection alive. Once the connection
is established on port 4125, the traffic is then redirected to another
dynamically allocated port. All subsequence traffic will flow through the
new port at the server to the client at port 3389. In another word, you
even do not need to configure port redirection for 3389. And RWW using SSL
session to the website. You don't even need port 80. By this way, RWW
building up function from the narrowest of openings to the client. So your
threat analysis is reduced. However, RDC requires the server keeps listen
on port 3389, you may need to configure the firewall for port redirection
on server.
For how to deploy Terminal Server on in SBS 2003 network, please refer to
the following document:
Deploying Windows Server 2003 Terminal Server to Host User Desktops in a
Windows Small Business Server 2003 Environment
http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/adstrmsr.mspx
I look forward to your reply. Also, if you have any questions or concerns,
please do not hesitate to let me know. I am happy to help. :-)
Thank you for your time and cooperation!
Best regards,
Gary Wang(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: RDP VS RWW to Terminal Server
| thread-index: Aci5gSsrgB51gzBzSmieSfHDzgkT5g==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?bGF1cmE=?= <laura@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: RDP VS RWW to Terminal Server
| Date: Mon, 19 May 2008 00:23:00 -0700
| Lines: 11
| Message-ID: <B6D64161-3828-41ED-8CB1-F582DE573169@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:108282
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Which way is safer to login to Terminal server option 1 or 2 below, or
they
| are the same thing in regards to Security
| 1) RWW then connect to my application server and selecting Terminal
Server VS.
| 2) RDC to Terminal server directly (where SBS which has 2 nic, router
| redirects port 3389 to external NIC of SBS and then sbs redirects port
3389
| to Terminal Server, so When users RDC to mail.xxx.com it takes them to TS
| directly"
| What is the difference, pros, cons, security risk, speed and any other
know
| issues.
|
| Thank you.
|
.
- References:
- RDP VS RWW to Terminal Server
- From: laura
- RDP VS RWW to Terminal Server
- Prev by Date: Re: Deactivate/uninstall Exchange domain on SBS 2003
- Next by Date: VPN timeouts
- Previous by thread: Re: RDP VS RWW to Terminal Server
- Next by thread: SBS 2000 OEM to SBS 2003 upgrade part numbers
- Index(es):
Relevant Pages
|
