Connection ended on "thin clients"

[Guest]

I have a remote office that connects to our corp office via Remote Desktop.
The "regular computers" seem to login fine to the Terminal Server, however,
the 3 HP thin clients appear to have trouble connecting. The error I get
when the "thin clients" try to connect is "The connection was ended because
of a network error. Please try connecting to the remote computer again."
This only occurs on the thin clients, NOT the PC's. I didn't setup this
configuration and don't know much about the thin clients? Does anyone have
any ideas? Thanks a bunch!

 

[Vera Noest [MVP]]

Is there anything in the EventLog on the TS when this happens?
Is your TS running W2K or 2003?
Have you checked the licensing situation of these thin clients? There
are a couple of thin client-specific problems with license renewal.

 

[Guest]

I don't see anything bad in the event viewer other than some DCOM errors
which I don't suspect have anything to do with the problem. The following
info is the error from the log.

Access denied attempting to launch a DCOM Server using
DefaultLaunchPermssion. The server is:
{00020906-0000-0000-C000-000000000046}
The user is Unavailable/Unavailable, SID=Unavailable. Event ID:10003

There are two servers. Both are running Windows 2000 Server SP4. There is
a "front-end" terminal server, and an additional server where data is stored.
They are running the SBS edition, which I'm also not that familiar with.

I have no idea what to check as it relates to licensing on these HP/Compaq
thin clients. Never used thin clients before. Thing is I can connect using
the Remote Desktop fine from an ordinary pc. The model I believe is a
HP/Compaq T5000. The license logging service was off, and I turned it on,
although I don't think that has helped. Vera, I was on your site yesterday.
You've got lots of good info, but couldn't find a resolution.

Where would you suggest I start?

Please help! I would be very grateful!! Thanks in advance!

 

[Vera Noest [MVP]]

I meant the Terminal Services Licensing Manager on the server that
runs the TS Licensing Service, since there are known problems with
renewal of TS CALs by thin clients. But if that was the cause of
the problem, I would also expect Event 1004 ("cannot issue client
license") on the server that runs Terminal Services.

Since you don't see that Event, we'll have to look somewhere else.
How is the setup of the thin clients? Have you checked their
connection configuration, IP configuration, etc?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Guest]

Since I no nothing about these thin clients, is there a good easy
manuel/process for setting up these devices? It's an HP T5000. How can I
check the configuration? I will be going to the site tomorrow night. Is
there a special "admin" password needed? Should I reset the BIOS? If so,
what is the process for resetting the BIOS? Does resetting the BIOS restore
the configuration to "factory defaults?"

Do you happen to know if HP's support is good on these devices, and if they
are available after hours?

Thank you so much for your help!

 

[Vera Noest [MVP]]

I've never used a HP thin client, but if you go to HPs website
www.hp.com and search for hp t5000, one of the first documents
that's returneded is the

Troubleshooting Guide for HP Compaq T5000 thin clients.
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00215686/c
00215686.pdf

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---