I have a w2k3 sp1 with Terminal Server service installed. The same machine
also are the only DC that domain (yes I know it's not the very best
solution but it's a small process site) and it's also Terminal service
license server. We remotely connect to that server from another domain. Now
som of the users get
"The client could not establish a connection to the remote computer"
The most likely cause of this error are
1. Remote connection are not enabled ... but they are
2. The maximum number of connections are exceeded at the remote computer ...
there are at least 3 more available license, if it's that it mean ?
3. A network error ... it works for others from the same computer
Could it be a problem if they are connecting from another TS server (w2k3
sp2) from another domain because that will only take one license and thats
why som can and some not. The license server are set at "per device" and
then it won't accept more than one at a time from that device ? Will this be
solved if I change to "per user" license model ?
No, licensing is not the problem. A single client access license
allows for unlimited connections from that client.
Have you checked the settings in tscc.msc - rdp-tcp connection -
properties - network? Maybe there's a hardcoded limit on the number
of connections?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"jonte@bson.se" <jonasberthelsson@hotmail.com> wrote on 22 apr
2008 in microsoft.public.windows.terminal_services:
> I have a w2k3 sp1 with Terminal Server service installed. The
> same machine also are the only DC that domain (yes I know it's
> not the very best solution but it's a small process site) and
> it's also Terminal service license server. We remotely connect
> to that server from another domain. Now som of the users get
>
> "The client could not establish a connection to the remote
> computer" The most likely cause of this error are
> 1. Remote connection are not enabled ... but they are
> 2. The maximum number of connections are exceeded at the remote
> computer ... there are at least 3 more available license, if
> it's that it mean ? 3. A network error ... it works for others
> from the same computer
>
> Could it be a problem if they are connecting from another TS
> server (w2k3 sp2) from another domain because that will only
> take one license and thats why som can and some not. The license
> server are set at "per device" and then it won't accept more
> than one at a time from that device ? Will this be solved if I
> change to "per user" license model ?
>
> Please help me out ?
>
> Sincerely
>
> \\Jonas B
Yes, that was the problem ! It was set on 10, but the default are unlimited
or ? I havn't set that myself but perhaps any consultant has than that
Thank's a lot
\\Jonas B
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> skrev i
meddelandet news:Xns9A89E0B10451Bveranoesthemutforsse@207.46.248.16...
> No, licensing is not the problem. A single client access license
> allows for unlimited connections from that client.
>
> Have you checked the settings in tscc.msc - rdp-tcp connection -
> properties - network? Maybe there's a hardcoded limit on the number
> of connections?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "jonte@bson.se" <jonasberthelsson@hotmail.com> wrote on 22 apr
> 2008 in microsoft.public.windows.terminal_services:
>
>> I have a w2k3 sp1 with Terminal Server service installed. The
>> same machine also are the only DC that domain (yes I know it's
>> not the very best solution but it's a small process site) and
>> it's also Terminal service license server. We remotely connect
>> to that server from another domain. Now som of the users get
>>
>> "The client could not establish a connection to the remote
>> computer" The most likely cause of this error are
>> 1. Remote connection are not enabled ... but they are
>> 2. The maximum number of connections are exceeded at the remote
>> computer ... there are at least 3 more available license, if
>> it's that it mean ? 3. A network error ... it works for others
>> from the same computer
>>
>> Could it be a problem if they are connecting from another TS
>> server (w2k3 sp2) from another domain because that will only
>> take one license and thats why som can and some not. The license
>> server are set at "per device" and then it won't accept more
>> than one at a time from that device ? Will this be solved if I
>> change to "per user" license model ?
>>
>> Please help me out ?
>>
>> Sincerely
>>
>> \\Jonas B
Yes, the default is unlimited, so that you are only limited by the
number of licenses you have.
I'm glad that your problem is solved, and thanks for the feedback!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"jonte@bson.se" <jonasberthelsson@hotmail.com> wrote on 24 apr
2008 in microsoft.public.windows.terminal_services:
> Yes, that was the problem ! It was set on 10, but the default
> are unlimited or ? I havn't set that myself but perhaps any
> consultant has than that
>
> Thank's a lot
>
> \\Jonas B
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> skrev
> i meddelandet
> news:Xns9A89E0B10451Bveranoesthemutforsse@207.46.248.16...
>> No, licensing is not the problem. A single client access
>> license allows for unlimited connections from that client.
>>
>> Have you checked the settings in tscc.msc - rdp-tcp connection
>> - properties - network? Maybe there's a hardcoded limit on the
>> number of connections?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "jonte@bson.se" <jonasberthelsson@hotmail.com> wrote on 22 apr
>> 2008 in microsoft.public.windows.terminal_services:
>>
>>> I have a w2k3 sp1 with Terminal Server service installed. The
>>> same machine also are the only DC that domain (yes I know
>>> it's not the very best solution but it's a small process site)
>>> and it's also Terminal service license server. We remotely
>>> connect to that server from another domain. Now som of the
>>> users get
>>>
>>> "The client could not establish a connection to the remote
>>> computer" The most likely cause of this error are
>>> 1. Remote connection are not enabled ... but they are
>>> 2. The maximum number of connections are exceeded at the
>>> remote computer ... there are at least 3 more available
>>> license, if it's that it mean ? 3. A network error ... it
>>> works for others from the same computer
>>>
>>> Could it be a problem if they are connecting from another TS
>>> server (w2k3 sp2) from another domain because that will only
>>> take one license and thats why som can and some not. The
>>> license server are set at "per device" and then it won't
>>> accept more than one at a time from that device ? Will this be
>>> solved if I change to "per user" license model ?
>>>
>>> Please help me out ?
>>>
>>> Sincerely
>>>
>>> \\Jonas B
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
