Re: Terminal Server Name Resolution
- From: "Jim Harrison" <jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Sat, 18 May 2002 08:30:02 -0700
MessageAnother kewler thing about the XP TS client is that you can specify the
port number in the "Computer" textbox.
Just enter it like: "ComputerName:Port"
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/authors/harrison/
Read the books!
----- Original Message -----
From: John Tolmachoff
To: [ISAserver.org Discussion List]
Sent: Friday, May 17, 2002 5:35 PM
Subject: [isalist] Re: Terminal Server Name Resolution
http://www.ISAserver.org
We have it set up so all servers have a different port number.
On the TS client, edit the cns file to the changed port number.
We do not resolve the computer name, as we use the IP address.
John Tolmachoff
IT Manager, Network Engineer
RelianceSoft, Inc.
Fullerton, CA 92835
www.reliancesoft.com
-----Original Message-----
From: Chris Lawless [mailto:ChrisL@xxxxxxxxxxxxxxxxxx]
Sent: Thursday, May 16, 2002 11:01 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Terminal Server Name Resolution
http://www.ISAserver.org
I've just been through some of this with a lot of help with articles on the
web site. I'll try to summise some of what I learned.
If you also want TS on the ISA you have to change its port such that web
publishing can listen on the standard port of 3389 and pass it on to another
server. Note that if you're changing the port remotely make sure you add packet
filters for the new port or you'll end up stranded and unable to connect...!
You can then publish your terminal server but as you say, one IP address is
needed per terminal server as publishing can onlu listen on one port per IP
address.
I suspect the best way to manage multiple server will be to login to one and
then TS from there to the others once you are "inside".
Chris.
-----Original Message-----
From: Guinn Unger [mailto:mlists@xxxxxxxxxxxxx]
Sent: Thursday, May 16, 2002 1:49 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Terminal Server Name Resolution
http://www.ISAserver.org
Is this saying that every TS server has to have a public name and IP
address? It would seem like this could be a real problem if you had a lot of
machines that you wanted to be able to manage via the web through TS.
It appears to me that a TS publishing rule simply maps an external IP
address on the ISA machine to an internal IP address. So would you need a
separate publishing rule for each TS server?
Thanks.
Guinn
-----Original Message-----
From: Jim Harrison [mailto:jim@xxxxxxxxxxxx]
Sent: Thursday, May 16, 2002 11:19 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Terminal Server Name Resolution
http://www.ISAserver.org
The external client has to be able to resolve whatever name you enter in
the "server" field to an ISA external IP so that it can be routed to the proper
TS server behind it.
You also have to have a TS publishing rule to the server you're trying to
connect to.
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/authors/harrison/
Read the books!
----- Original Message -----
From: Guinn Unger
To: [ISAserver.org Discussion List]
Sent: Thursday, May 16, 2002 6:32 AM
Subject: [isalist] Terminal Server Name Resolution
http://www.ISAserver.org
I have Terminal Server set up on two of our servers. From inside the
firewall everything works fine. Both the Windows and web clients can access
both machines. The Windows client also works fine over the VPN. However, if I
try to log on from outside the firewall with the web client the server cannot
be found. The actual error message is "Error connecting to terminal server:
ungerras". (ungerras is an internal name, not published on the web.) However,
if I leave the server name blank when logging on, it actually connects to
ungerras. It indicates that it is logged onto www.mydomain.com (where
"mydomain" is out published web site), but it is actually connecting to
ungerras (on a different machine). However, there doesn't seem to be any way
to connect to the other server (which is actually running on the IIS machine
that we are connecting through).
I'm curious about what is going on here, and it's clear that I don't
understand how the server name is being resolved. Any help would be
appreciated.
(I believe that we are set up following the instructions on the
isaserver.org web site.)
Guinn Unger
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
mlists@xxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
chrisl@xxxxxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
isalist@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
