Windows NT Thin client set up

  • Thread starter Thread starter Gretchen Hembree
  • Start date Start date
G

Gretchen Hembree

I am new to thin clients and am actually borrowing one from a friend to see
if we want to make a purchase. I plugged the machine in and DHCP worked
because it has a correct IP address for our network. I could also ping the
server I want to connect to, but when I attempted to connect it would not for
either our 2003 server or our 2000 server. I am confused why it didn't even
issue it a temporary license. Is there something I need to physically do on
the server to issue a license to a thin client?

Thanks. ~Gretchen
 
Why do you believe that the problem is caused by licensing?
Do you get any error message on the client when you try to connect?
Are there any errors or warnings in the EventLog on the Terminal
Server?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?R3JldGNoZW4gSGVtYnJlZQ==?=
<GretchenHembree@discussions.microsoft.com> wrote on 19 aug 2007:

> I am new to thin clients and am actually borrowing one from a
> friend to see if we want to make a purchase. I plugged the
> machine in and DHCP worked because it has a correct IP address
> for our network. I could also ping the server I want to connect
> to, but when I attempted to connect it would not for either our
> 2003 server or our 2000 server. I am confused why it didn't
> even issue it a temporary license. Is there something I need to
> physically do on the server to issue a license to a thin client?
>
> Thanks. ~Gretchen
 
Yes I get a licensing error. I can't remember word for word off hand, but it
said it can not connect due to licensing issues.

The event viewer showed an error 1028: The terminal server client
WBT008064420155 has been disconnected because its license could not be
renewed. The license server AHTS2 was contacted to get Windows Server 2003 -
Terminal Server Per Device CAL Token. license for this client.

I will confess that we are still using temporary licenses for our machines.
I ordered CALs last week but have not gotten them yet. However, I thought a
temporary license would be issues just for testing purposes. Is that
different for a thin client?
Thanks.

"Vera Noest [MVP]" wrote:

> Why do you believe that the problem is caused by licensing?
> Do you get any error message on the client when you try to connect?
> Are there any errors or warnings in the EventLog on the Terminal
> Server?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?R3JldGNoZW4gSGVtYnJlZQ==?=
> <GretchenHembree@discussions.microsoft.com> wrote on 19 aug 2007:
>
> > I am new to thin clients and am actually borrowing one from a
> > friend to see if we want to make a purchase. I plugged the
> > machine in and DHCP worked because it has a correct IP address
> > for our network. I could also ping the server I want to connect
> > to, but when I attempted to connect it would not for either our
> > 2003 server or our 2000 server. I am confused why it didn't
> > even issue it a temporary license. Is there something I need to
> > physically do on the server to issue a license to a thin client?
> >
> > Thanks. ~Gretchen
>
 
OK, that explains the problem.
The key word in the EventLog is "renewed".
It means that this client has already received a temporary license
(probably when your friend used it) and that temporary license has
expired.
A client (any client, thin or fat doesn't matter) gets a temporary
license only *once*. If that license expires, the client must get a
permanent licenses.
So you'll have to wait until your license pack arrives.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?R3JldGNoZW4gSGVtYnJlZQ==?=
<GretchenHembree@discussions.microsoft.com> wrote on 20 aug 2007:

> Yes I get a licensing error. I can't remember word for word off
> hand, but it said it can not connect due to licensing issues.
>
> The event viewer showed an error 1028: The terminal server
> client WBT008064420155 has been disconnected because its license
> could not be renewed. The license server AHTS2 was contacted to
> get Windows Server 2003 - Terminal Server Per Device CAL Token.
> license for this client.
>
> I will confess that we are still using temporary licenses for
> our machines. I ordered CALs last week but have not gotten them
> yet. However, I thought a temporary license would be issues
> just for testing purposes. Is that different for a thin client?
> Thanks.
>
> "Vera Noest [MVP]" wrote:
>
>> Why do you believe that the problem is caused by licensing?
>> Do you get any error message on the client when you try to
>> connect? Are there any errors or warnings in the EventLog on
>> the Terminal Server?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?R3JldGNoZW4gSGVtYnJlZQ==?=
>> <GretchenHembree@discussions.microsoft.com> wrote on 19 aug
>> 2007:
>>
>> > I am new to thin clients and am actually borrowing one from a
>> > friend to see if we want to make a purchase. I plugged the
>> > machine in and DHCP worked because it has a correct IP
>> > address for our network. I could also ping the server I want
>> > to connect to, but when I attempted to connect it would not
>> > for either our 2003 server or our 2000 server. I am confused
>> > why it didn't even issue it a temporary license. Is there
>> > something I need to physically do on the server to issue a
>> > license to a thin client?
>> >
>> > Thanks. ~Gretchen
 
Back
Top