Re: ISA and Terminal Server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Bill (anonymous_at_discussions.microsoft.com)
Date: 07/22/04 

Date: Thu, 22 Jul 2004 11:24:04 -0700

I get an error message that says, "the remote computer
could not be found. Make sure you typed the right
computer name or Ip address,"
>-----Original Message-----
>OK, so what happens when you try by name?
>
>Bill wrote:
>> I can connect to all of them from the LAN using their
>> internal Ip address.
>>
>>
>>> -----Original Message-----
>>> Bill wrote:
>>>> I have two SBS 2003 Servers with ISA in two different
>>>> companies. I was able to use remote administration
on
>>>> the SBS at one company without a problem, until I
>> added a
>>>> Widows 2000 Terminal Server running in application
server
>>>> mode. Now I can access the Terminal Server in
>>>> application mode, but can longer access my SBS 2003
in
>>>> remote administration mode.
>>>
>>> What happens when you try? Is this true from the LAN
as well as from
>>> the Internet?
>>>>
>>>> I have a similar setup at another company, except
that my
>>>> Terminal Server is on a 2003 Terminal Server in
>>>> appliation server mode. I can still access the SBS
2003
>>>> in remote administration mode and can browse to the
>>>> shared folders on the application server, but cannot
>>>> access the 2003 Server from a remote location
running in
>>>> application server mode. I have follwed all the
steps
>>>> outlined in KB 294720. All the above servers listen
on
>>>> port 3389 and I have seperate Internet IPs mapped to
each.
>>>>
>>>> Any ideas would be sincerely appreciated.
>>>
>>>
>>> .
>
>
>.
>

Relevant Pages

  • Re: Terminal Services Remote Desktop Login Problem
    ... Are these users on the same LAN as the server? ... > The error message is: ... > The connection to the remote computer was broken. ...
    (microsoft.public.windows.terminal_services)
  • Cant RDP "error in licensing protocol" user in Argentina
    ... They receive the following error message when attempting to connect via RDP: ... "The remote computer disconnected the session because of an error in the licensing protocol. ... Myself and several other people have been able to connect to each server with no issues, ... Researching the error points me to Terminal Services licensing issues, but Terminal Services was never set up for licensing so I don't see how this would apply. ...
    (microsoft.public.windows.server.general)
  • stop installation
    ... other compters, when I choose to install, the pop-up window, asking ... then an error message says " Error A. A connection to the ... remote computer could not be established.....". ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: Problem with Terminal Services Client
    ... > Business Server. ... > Remote connections might not be enabled or the computer ... Is this from a computer on the same LAN as your server? ... connect to the TS from a remote computer outside your LAN? ...
    (microsoft.public.windows.server.sbs)
  • Re: CreateScript: how to tell if it was successful
    ... >> If I attempt to create a script on a remote computer, ... the script terminates with the error message ... >> Is there a simple way to check if a CreateScript was successful, ... I found that the error message is tripping on the CreateScript, ...
    (microsoft.public.scripting.wsh)