Terminal Server Name ResolutionThe 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')