Re: Could Not Establish A Connection To The Remote Computer...

Hi, Vera,

Thanks a lot for your reply.

I forgot to mention that Domain A is a Windows 2000 domain, and the both the
Terminal Service server and the Terminal Service Licensing server are on
Windows 2000 Servers (SP4).

I tried your suggestion to test for a black hole router. It appears there
is not a black hole router, since I was successfully able to ping from both
the TS client and the TS server using a 1472 MTU size.

I don't know if this matters, but I noticed a
"LicensingGracePeriodExpirationWarningDays" registry entry in the Terminal
Service server in Domain A. (This was not found in the TS Licensing server.)
It has a decimal value of 15. And I recall seeing a post (from you?) that
this indicates some other kind of problem.

Do you think it's better to start from scratch and uninstall Terminal
Services (and Licensing) and then reinstall? Thanks again for your help. I
really appreciate it.

Jeff

"Vera Noest [MVP]" wrote:

There might be a black hole router between your clients in domain B
and the TS in domain A, which blocks packets above a certain size.
This prevents the transfer of the permanent TS CAL to the client
(on first connection, the client gets a temporary license, on
second connection, it gets a permanent license).

If this is the problem, you have to change the MTU size. Check the
Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.asp

The multiple temporary licenses are caused by deleting the
MSLicensing key from the clients. This forces the LS to issue a new
temporary license of the next connection.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmVmZg==?= <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 23
aug 2006 in microsoft.public.win2000.termserv.apps:

Hello,

We have Terminal Services in application mode along with its
licensing service in Domain A, which we installed two days ago.
Users in Domain A can connect in with no problem. However,
users in a Domain B, which is in a completely different forest,
have trouble connecting in even though they have Windows XP
Professional.

A user in Domain B can connect in one time with no problem. But
when the user tries to connect in a second time, the following
error message appears on their screen:
"The client could not establish a connection to the remote
computer. The most likely casues for this error are: 1) Remote
connections might not be enabled at the remote computer. 2) The
maximum number of connections was exceeded at the remote
computer. 3) A network error occured while establishing the
connection"

At that time, the Terminal Service server logs event ID 1004 -
"The terminal server cannot issue a client license." If the
user in Domain B then deletes the MSLicensing key from their
registry, he/she can connect in again one time.

I also noticed Terminal Service Licensing is issuing new
temporary license (we have not yet activated our TS licenses)
each time the same user in Domain B connects, so there appear to
be "duplicates". Users in Domain A are not experiencing that
and are able to use their same already issued license (no
duplicates).

Any help/guidance you can provide to resolve this problem is
greatly appreciated. Users in Domain B are getting tired of
having to delete the MSLicensing key each time they want to
connect. Thanks in advance for your help.

Jeff

.

Relevant Pages

  • RE: Users randomly disconnected
    ... connection to the old NT4 server, ... the BDC and to a test server which is a W2k workstation". ... Stop the License Logging service. ...
    (microsoft.public.windows.server.migration)
  • Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
    ... servers do not automatically discover a license server that is ... on second connection you get a permanent ... > there is no TSLS, and that the grace period is going to expire. ...
    (microsoft.public.windows.terminal_services)
  • Application Server Mode
    ... i tried re-activating the license server and even re-installed terminal ... The client could not establish a connection to the remote computer. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Licensing Server not found on this domain??
    ... The TCP/IP Netbios Helper Service was disabled and apparently causes that ... > "the connection was ended because of a network error, ... > so I assumed maybe his license got expired and someone else scooped it. ... > workgroup, To connect to another license server, click ok, click connect ...
    (microsoft.public.windows.terminal_services)
  • Re: WindowsXP Remote Desktop Client
    ... > suddenly, as the client software made the connection to the server, I began to ... > license expiry continues. ... > server using a Remote Desktop Client on different Windows machines. ...
    (microsoft.public.win2000.macintosh)