|
|
|
date: Tue, 13 Sep 2005 17:22:01 -0700,
group: microsoft.public.windowsnt.terminalserver.client
back
Re: Thin Client cannot connect
So it isn't a licensing problem after all?
What exactly is the error message on the client, then?
_________________________________________________________
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?VGVkIENvZ2dlcg==?="
wrote on 15 sep 2005 in
microsoft.public.windowsnt.terminalserver.client:
> Thank you Vera for your responce
>
> The W2k TS has in use 40 workstations (XP Pro) 10 CAL Licences
> are taken by old workstations/Other Thin Clients and we have 5
> CALs available and not used
>
> When my client bought the other company we redid the network
> setup and replaced their VPN routers with Snap Gear VPN Routers
> and changed all DNS, DHCP etc
> all other workstations are working fine we are getting now a few
> workstations having the same problem but it is easy to delete
> the MSlicensing and the workstation will call the W2K TS server
>
> We tried the Factory reset on the thin Client to no avail,
> The Event viewer is the problem as it is not desplaying any
> problems with the connections so I cannot tell whats happening
> other than the message on the Thin Client
>
> Thanks
>
> "Vera Noest [MVP]" wrote:
>
>> Check the EventLog on the W2K TS to see the reason why the thin
>> client cannot connect.
>> If it indeed is a licensing problem:
>> * do you still have an activated TS Licensing Server (or was
>> the only LS running on the 2003 server which is offline?)
>> * if you have an LS, is it activated and does it have available
>> TS CALs?
>> * can the W2K TS locate the LS (maybe it is still looking for
>> the old LS?)
>>
>> Note that TS CALs are *not* per concurrent connection, they are
>> *not* returned to the LS on disconnecting. They are issued to a
>> specific client and expire after 52-89 days. Then they must be
>> renewed.
>> And even more important: a thin client needs a purchased TS
>> CAL, the free TS CALs are only issued to W2K Pro and XP Pro
>> clients (when connecting to a W2K TS).
>>
>> _________________________________________________________
>> 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?VGVkIENvZ2dlcg==?=" <Ted
>> Cogger@discussions.microsoft.com> wrote on 14 sep 2005 in
>> microsoft.public.windowsnt.terminalserver.client:
>>
>> > My Client bought another company which had TS 2K3 server with
>> > VPN to remote location and a thin client on the network the
>> > Server was decommisioned and is currently being rebuilt the
>> > VPN connection was redirected to my clients 2K terminal
>> > server Last week the Thin client could not connect to the 2k
>> > server it has a cal problem
>> >
>> > I was under the impression that thin clients picked there
>> > Cals off the server at login and when they log out the Cal is
>> > returned to the Free Pool
>> >
>> > Why would the server reject the client and how do I fix this
>> > problem The 2k Server has Service pack 4 on it and none of
>> > the other thin Clients have a problem
>> >
>> > Any sugestions
date: Thu, 15 Sep 2005 07:07:06 -0700
author: Vera Noest [MVP]
|
|
