RE: Publishing Terminal Server on Windows Server 2003
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 26 Aug 2003 14:29:08 -0500
Hi Joe,
Make sure you enter a server name that is resolvable to the public
address you used for the RDP Server Publishing Rule.
HTH,
Thomas W Shinder
www.isaserver.org/shinder <http://www.isaserver.org/shinder>
ISA Server and Beyond: http://tinyurl.com/1jq1
Configuring ISA Server: http://tinyurl.com/1llp
<http://tinyurl.com/1llp>
-----Original Message-----
From: Joseph Ledwidge [mailto:josephl@xxxxxx]
Sent: Tuesday, August 26, 2003 2:00 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Terminal Server on Windows
Server 2003
http://www.ISAserver.org
I have a separate licensing server setup for 2003 and can
connect on my LAN to the 2003 terminal server. My problem is that I
can't connect to it externally even though I have followed the same
steps as I did for a windows 2000 Terminal server
I have created a Protocol Definition for Inbound 3389
Created a Server publishing rule mapping this to the internal
server
I do not have Terminal services installed on the ISA server.
I can connect to the IIS server and see the root under
construction page and the Remote Desktop Connection page at
www.mydomain.com/tsweb
When I enter a server name I get the following error. I have
seen this before while trying to configure TS access but can't remember
what I did to correct it.
"The client could not establish a connection to the remote
computer. The most likely causes for this error are 1. Remote
connections might not be enabled at the remote computer 2. The max no of
connections was exceeded at the remote computer 3. A network error
occurred while establishing the connection."
Tried going back to the start and doing all the ISA config again
but same result.
Thanks for any help
Joe
Other related posts:
