Welcome to ISAserver.org

Terminal Server Publishing

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Server Publishing >> Terminal Server Publishing

Page: [1]

Message

<< Older Topic Newer Topic >>

Terminal Server Publishing - 15.Oct.2003 5:50:00 PM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

I am currently trying to Publish a terminal Server via ISA on a Windows 2003 server.

I have published the TSAC web site with success but when I try to contact the terminal server via the same external IP address I receive the VBScript error: Remote desktop disconnected.

Terminal services is bound to the internal network card so i don't think its a port contention

I can see traffic from the client trying to connect to the terminal servers Internal IP rather than the ISA to the Internal IP address...?

Any ideas, the help would be greatly appreciated.

Post #: 1

Featured Links*

RE: Terminal Server Publishing - 15.Oct.2003 8:05:00 PM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

you sure if you create custom protocols like rdp?

(in reply to Paul H)

Post #: 2

RE: Terminal Server Publishing - 16.Oct.2003 9:56:00 AM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Yes, Ive followed the Configuration instructions in the book (ISA Server and Beyond)

(in reply to Paul H)

Post #: 3

RE: Terminal Server Publishing - 16.Oct.2003 6:37:00 PM

raguilera

Posts: 2
Joined: 16.Oct.2003
Status: offline

I am getting the same error. When I enter FQDN in the login screen I get "computer could not be found" type error, when I put the IP Address, I get a similiar error, but says "server might be busy or not accepting connections". The TSAC works if internal from the network and externally I can use the full remote desktop client fine and hit the TSAC web page fine. Any thoughts?

(in reply to Paul H)

Post #: 4

RE: Terminal Server Publishing - 17.Oct.2003 10:47:00 AM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Are you using Windows 2003 or 2000 ?

(in reply to Paul H)

Post #: 5

RE: Terminal Server Publishing - 17.Oct.2003 11:08:00 AM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

from external connections make a port scan to the port that you make rdp publish and make sure that port is open. if isn't is because publish rule in isa is not correctly configurated!

(in reply to Paul H)

Post #: 6

RE: Terminal Server Publishing - 17.Oct.2003 11:58:00 AM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Cheers for the tip, but if the connection is not open how does the client know what the Internal IP address of the Terminal server is, ISA seems to pass this information on ???

(in reply to Paul H)

Post #: 7

RE: Terminal Server Publishing - 17.Oct.2003 12:19:00 PM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

from external you must type your external ip of isaserver, not your internal server. the server publishing rules is to emulate that your internal servers are running in isa server. in this case is the same that you are running terminal services on isa.

(in reply to Paul H)

Post #: 8

RE: Terminal Server Publishing - 17.Oct.2003 1:31:00 PM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Sorry seems to be some confusion here,

The TSAC website publishes with no problems connecting using a FQDN which resolves to the external IP of the ISA server.

When I try to connect to the terminal server via the TSAC Website or using the remote desktop client I cant get a connection.

When Client X attempts to connect to the Terminal Server via the ISA's external IP address, On the internal LAN I can see traffic from the Client X trying to attempt a connection to the Terminal servers Internal IP Address.

(in reply to Paul H)

Post #: 9

RE: Terminal Server Publishing - 17.Oct.2003 2:00:00 PM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

so you say that the connections pass sucessfull throw isa and in terminal server the logs indicates a call by external clients. so the problem might be in the terminal configurations. i never use terminal services on windows 2003. have you tried a connection by a internal machine?

try to add a ip packet filter that allow all ip traffic to the machine that you are trying to connect

tnks

(in reply to Paul H)

Post #: 10

RE: Terminal Server Publishing - 17.Oct.2003 4:16:00 PM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Thank for the help stants.

Ive tried the ip packet filter with no success.
Also I have tried the TSAC website internally and a remote desktop connection to the terminal server and they both work fine.

(in reply to Paul H)

Post #: 11

RE: Terminal Server Publishing - 17.Oct.2003 8:22:00 PM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

it's very strange...

i don't know how works terminal on windows 2003. but... grrr... [Big Grin]

if you have another machine in internal network like windows xp, try to publish that machine and view the result.

tnks

(in reply to Paul H)

Post #: 12

RE: Terminal Server Publishing - 21.Oct.2003 9:51:00 AM

cconnick

Posts: 1
Joined: 22.Apr.2003
From: Los Angeles
Status: offline

Paul and Raguilera, my experience is EXACTLY as you have described. The TSAC connection to the terminal server works great from inside the LAN, and I can connect to the TSAC website from the Web. But when I try to logon to the terminal server from the logon screen using the server's FQDN, I get "The specified remote computer could not be found." That message comes quickly. When I use the server's IP address, the messge is "The client could not connect to the remote server, etc. etc." This message can take as long as 30 seconds to appear. I'm thinking two things: 1) the terminal server can't receive client credentials or for some reason can't authenticate the client. 2) I'm wondering if ANYONE has ever made the terminal service web access work.

(in reply to Paul H)

Post #: 13

RE: Terminal Server Publishing - 21.Oct.2003 4:22:00 PM

tshinder

Posts: 47439
Joined: 10.Jan.2001
From: Texas
Status: offline

Hey guys,

I use TSAC all the time from external clients. The key is to pay close attention to what I said in the article. The server name you enter into the Web page must be resolvable to the address you used in the RDP Server Publishing Rule.

The problem is that people enter the internal server name, which clearly isn't resolvable by Internet based hosts.

HTH,
Tom

(in reply to Paul H)

Post #: 14

RE: Terminal Server Publishing - 22.Oct.2003 1:18:00 PM

Guest

Can someone urgently pls paste the link for the download to install the TSweb interface please?

I am running Server 2003. Anyone pls. This is urgent.

Regards

(in reply to Paul H)

Post #: 15

RE: Terminal Server Publishing - 22.Oct.2003 2:03:00 PM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

Can you let me know if your successfull with publishing a terminal server on Windows 2003, im currently re-building to W2K as I had problems as you could see.

Here's the required link
http://www.microsoft.com/windows2000/downloads/recommended/TSAC/default.asp

(in reply to Paul H)

Post #: 16

RE: Terminal Server Publishing - 22.Oct.2003 2:53:00 PM

stants

Posts: 40
Joined: 16.Feb.2003
From: Corroios, Lisboa, Portugal
Status: offline

hi!

as i was say in top

quote:
from external you must type your external ip of isaserver, not your internal server. the server publishing rules is to emulate that your internal servers are running in isa server.

i think that wasn't understood [Wink]

(in reply to Paul H)

Post #: 17

RE: Terminal Server Publishing - 23.Oct.2003 9:23:00 PM

tshinder

Posts: 47439
Joined: 10.Jan.2001
From: Texas
Status: offline

Hey guys,

Publishing the TS Web requires:

1. A web publishing rule to publish the Web site

2. An RDP Server Publishing rule

There's an article on this site on how to do it.

HTH,
Tom

(in reply to Paul H)

Post #: 18

RE: Terminal Server Publishing - 27.Oct.2003 3:25:00 PM

Paul H

Posts: 12
Joined: 15.Oct.2003
From: UK, England
Status: offline

What I was looking for was this article

http://support.microsoft.com/?id=311777

I needed the source address of the externalclients translating to the internal ip of the ISA server.

Thanks for everyones help and suggestions.

(in reply to Paul H)

Post #: 19