Prev: Start up program
Next: Terminal services licensing reinstallation Windows Server 2003
From: Kelly on 30 Mar 2010 21:05
I have about 20 HP thin clients that 10 of them print to a local printer
connected via USB or parallel. They will all print fine for a week or two and
then they notify me to tell me they can't print. I then have to log them off
of the RDP session and clear print jobs that are spooling within Windows CE.
These jobs are stuck in the HP Thin Connect application that allows me to
setup a printer for RDP.

Sometimes a few go weeks or months without a problem, and then other's have
this happen every week or two. Does anyone know why this happens or have a
solution. Again, these are only the thin clients that have a local printer
connected, the network printers are all OK. I know I could make them a
network printer, but I'm limited to IP addresses.

Thank you,
From: Kelly on 1 Apr 2010 05:46
Note; These Thin Clients are hard wired with Cat5/Cat6
Terminal Services is running on Windows Server2003 SR2
All patches and Windows Security updats are aplied

"Kelly" wrote:

> I have about 20 HP thin clients that 10 of them print to a local printer
> connected via USB or parallel. They will all print fine for a week or two and
> then they notify me to tell me they can't print. I then have to log them off
> of the RDP session and clear print jobs that are spooling within Windows CE.
> These jobs are stuck in the HP Thin Connect application that allows me to
> setup a printer for RDP.
>
> Sometimes a few go weeks or months without a problem, and then other's have
> this happen every week or two. Does anyone know why this happens or have a
> solution. Again, these are only the thin clients that have a local printer
> connected, the network printers are all OK. I know I could make them a
> network printer, but I'm limited to IP addresses.
>
> Thank you,
From: jolteroli on 5 Apr 2010 13:26
try to get rid of WindowsCE and have a look to:

(o) http://www.thinstation.org/
(o) http://www.ltsp.org/

with this os running, every TC can be turned into a HP-JetDirectAlike print
server (usb/lpt). the setup a network printer on your windows server and
just choose the IP address/FQDN of this TC, port 910[0-3] and install the
driver. now every workstation/ts-session can print on this printer.

or just lower network mask of every IP adapter by 1 bit and your network
will double the addresses space smoothly and without connection loss. e.g.:
255.255.255.0 to 255.255.254.0. after that, you can assign the upper
addresses, because the upper ones can only be reached with the new subnet
mask.

-jolt

"Kelly" <Kelly(a)discussions.microsoft.com> schrieb im Newsbeitrag
news:10072F55-3360-4EEC-9B90-F68F2ABB317E(a)microsoft.com...
> Note; These Thin Clients are hard wired with Cat5/Cat6
> Terminal Services is running on Windows Server2003 SR2
> All patches and Windows Security updats are aplied
>
> "Kelly" wrote:
>
>> I have about 20 HP thin clients that 10 of them print to a local printer
>> connected via USB or parallel. They will all print fine for a week or two
>> and
>> then they notify me to tell me they can't print. I then have to log them
>> off
>> of the RDP session and clear print jobs that are spooling within Windows
>> CE.
>> These jobs are stuck in the HP Thin Connect application that allows me to
>> setup a printer for RDP.
>>
>> Sometimes a few go weeks or months without a problem, and then other's
>> have
>> this happen every week or two. Does anyone know why this happens or have
>> a
>> solution. Again, these are only the thin clients that have a local
>> printer
>> connected, the network printers are all OK. I know I could make them a
>> network printer, but I'm limited to IP addresses.
>>
>> Thank you,


 | 
Pages: 1
Prev: Start up program
Next: Terminal services licensing reinstallation Windows Server 2003