Re: Could Not Establish A Connection To The Remote Computer...
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 Aug 2006 12:12:30 -0700
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
- Follow-Ups:
- Prev by Date: Re: Application INI not moving to Users Home Directory
- Next by Date: Re: Could Not Establish A Connection To The Remote Computer...
- Previous by thread: Re: Application INI not moving to Users Home Directory
- Next by thread: Re: Could Not Establish A Connection To The Remote Computer...
- Index(es):
Relevant Pages
|