Terminal Server Name Resolution
- From: "Guinn Unger" <mlists@xxxxxxxxxxxxx>
- To: "'ISA Mailing List'" <isalist@xxxxxxxxxxxxx>
- Date: Thu, 16 May 2002 08:32:40 -0500
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
Other related posts:
