Koozali.org: home of the SME Server

MS Terminal Server

Offline geoff

  • ***
  • 61
  • +0/-0
MS Terminal Server
« on: July 29, 2004, 02:10:09 AM »
I have a situation where I need to have a Windows 2000 Terminal Server behind an SME Server available to another location using ADSL. The SME server has a fixed IP address using an ADSL modem in bridged mode and I can access it using SSL.

Has anyone done this? Any help would be muchly appreciated.

Jon_Reynolds

MS Terminal Server
« Reply #1 on: July 29, 2004, 02:39:55 AM »
I belive you would want to forward the port from your SME server to the TS. The port for the MS RDP protocol is 3389, I think.

Hope that helps,

Jon

Offline dmac

  • ****
  • 143
  • +0/-0
    • http://www.rylar.ca
MS Terminal Server
« Reply #2 on: July 29, 2004, 06:37:19 AM »
Jon_Reynolds is correct, the port you need is 3389.  Also, you will need to make sure that you can find the TS Server, either using the hostname or IP address of the server.

Have you considered a VPN connection to validate on the Internal network and then setup the TS link?

Darin
"In a world without Fences, why do we need Gates and Windows"

Offline rexgaylord

  • ***
  • 59
  • +0/-0
    • http://www.backuplasvegas.com
MS Terminal Server
« Reply #3 on: July 29, 2004, 08:10:16 AM »
SME port forwarded to to a terminal server works great, Ive installed it as a working commbo a few times now.  What I have found to work really well is to use the web client right from the 2003 server and copy it right to an Ibay and force SSL so they get an SSL login.  (there is one glitch in that because they have wrote the file default.htm, but the coding inside of it refers to Default.htm on exit so the web page errors out on close, but if you copy default.htm to Default.htm so it has a copy of both file names, it works perfect).  The other combo that I have tried is port forwarding 443 to the terminal server and configure IIS and install an SSL certificate on the terminal server, that also forces them to use the web client in in SSL.  I'm getting ready to do a test install of 2003 Small Business Server and have the SME deliver the external email to the Exchange server after it has been throughly cleaned.  I'd be interested in any problems that anybody has had putting SBServer in that enviroment.  An example of using the 2003 server web client in an ibay can be seen at www.tandemxo.com/tsweb.  The great part about it is that if there is something behind it, you don't have to enter the server name, it just goes there on enter (Or maybe the not so good thing)...
......................................................

Offline rexgaylord

  • ***
  • 59
  • +0/-0
    • http://www.backuplasvegas.com
MS Terminal Server
« Reply #4 on: July 29, 2004, 08:17:38 AM »
P.S.

That example is actually going to an XP Pro PC, but same concept, same ports, same 2003 Server web client, so nothing work hacking...
......................................................

Offline geoff

  • ***
  • 61
  • +0/-0
MS Terminal Server
« Reply #5 on: July 29, 2004, 02:23:38 PM »
Thanks to everyone for your replies - I'll be setting this up next week so I'll report.

Offline jmvelez

  • ****
  • 85
  • +0/-0
    • http://velezcomputer.com
MS Terminal Server
« Reply #6 on: July 30, 2004, 04:18:55 AM »
The performance difference in W2K and W2K3 is great.  The only bad about W2k3 is extra Lic to pay since all clients needs a Lic.  The port forwarding works great with Win TS or Citrix