RE: SBS 2003 and ISA 2004, publish TS Server
Edward Tian
Thank you for posting here.
For SBS 2k3 server, we have some special design for deploying Terminal
Server in the network, while we are not losing the ability to access the
SBS server remotely from the internet at the same time. The users on the
internet could use the web interface to access the Terminal Server inside
the SBS network. It is RWW (Remote Web Workplace: http://SBSFQDN/remote).
For the detailed steps of deploying, please refer to the following white
paper:
Note: If you have any hardware router or firewall, please open the port 80,
443 and 4125. The port 80 and 443 is used for RWW and 4125 for the RDP
session.
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
For your information:
To support a Remote Desktop connection to the client machine and/or
Terminal Servers through a firewall, SBS implements a server-side port
forwarder that uses the SBS server to dynamically forward Terminal Server
data through a firewall or a router, keeping the Terminal Server connection
alive.
First of all, the remote user is going to open up a Web browser and
navigate to the computer selection page of the Remote Web Workplace site,
connecting on TCP port 80. The remote user is going to be prompted to
install the Terminal Server ActiveX component, if necessary. After that's
installed, the SBS server is going to query the Active Directory for all
internal client computers running an OS that supports Remote Desktop and
Terminal Servers. Then it will present that list to the remote user for
selection.
After that, the user is going to select his or her internal client or the
Terminal Server and then click the Connect button. The Small Business
Server reads the port value from the registry, and that location is
HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\P
ort and creates a listening socket on that port. That's TCP port 4125 by
default. This port is opened on the firewall, if the user has run the SBS
CEICW. For those of you who have a single NIC configuration, again, you'll
have to open that port on your router. The SBS server creates a connection
to the internal computer's remote desktop sharing service on TCP port 3389.
The server then creates a thread to manage the Terminal Server connection
between the remote client and then the internal client Terminal Server
connection. The thread is started, and the port value for the server is
passed back to the client in the form of a URL. At that point, the Terminal
Service ActiveX control connects using the port specified in the returned
URL. Then, after that, the thread monitors port traffic and forwards any
Terminal Server requests to the appropriate client.
More information:
833983 TechNet Support WebCast: An overview of Microsoft Windows Small
Business Remote Web Workplace
http://support.microsoft.com/?id=833983
http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2F
en%2Ftranscripts%2Fwct010804.asp
I would appreciate your time to go through the above article and following
the process to deploy your Terminal Server. If you have any questions or
concerns related to this issue, please let me know.
In addition, we can also use the server publishing method to publish this
terminal server. However, the terminal service of the SBS Server itself
could no longer listen to the external NIC on port 3389, we should use an
alternate port for it. More information:
How to Server Publish a Terminal Server with ISA While also Running
Terminal Services on the ISA
http://support.microsoft.com/?id=294720
How to Change Terminal Server's Listening Port
http://support.microsoft.com/default.aspx?scid=KB;EN-US;187623
Hope the above information helps. I look forward to your update.
Have a nice day! :-)
Best Regards
Edward Tian(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: SBS 2003 and ISA 2004, publish TS Server
| thread-index: AcXe6y2ZlNSywkNHQtWQFsKWEij4Og==
| X-WBNR-Posting-Host: 220.234.174.46
| From: "=?Utf-8?B?R3V0aHJpZSBKYWZmZXJzb24=?="
<GuthrieJ...@discussions.microsoft.com>
| Subject: SBS 2003 and ISA 2004, publish TS Server
| Date: Tue, 1 Nov 2005 05:50:11 -0800
| Lines: 9
| Message-ID: <97A60A13-9D34-4B70...@microsoft.com>
| 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.0
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:166551
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I want to publish an internal TS Server to the internet. Do I have to
create
| rules in the ISA? Is there any other method I can use? Will I still be
able
| to connect to the SBS Server itself using RDP?
|
| The SBS Server has two NIC and everything is functioning well.
|
| Thanks for any help.
|
| Guthrie Jafferson
|