Inactive TS port

  • Thread starter Thread starter BFH
  • Start date Start date
B

BFH

Guest
Installing Wyse Thin Clients, using their OS, not Win CE or such. Connecting
USB local printer to the thin clients and accessing Win2003 server via RDP.
Once logged in, I can create a printer which prints to the WinTerm's USB
local printer, however, once I log off and log back on, the printer doesn't
work. The printer icon is still there, but if I check the port settings, the
port I created in the last session is listed as an "Inactive TS port," and
there's a new port available for the USB local printer.

If I change the printer to print to that new port, it works, but then on log
off and log back on, that port is listed as Inactive, etc. etc. etc. (and
even if that worked, I wouldn't want users to have to do it).

So, I need to know what to set up on the server to recognize the thin
client's port on logon 2 as being the same port set up on logon 1. Any
takers?

So, I need to know how I can
 
Re: Inactive TS port

Please tale a look at a similar issue online and see if the resolution helps
fix your issue:
http://www.pcreview.co.uk/forums/thread-1614545.php

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"BFH" <BFH@discussions.microsoft.com> wrote in message
news:C9A61894-1082-4AB2-A82B-9C7AE835D62B@microsoft.com...
> Installing Wyse Thin Clients, using their OS, not Win CE or such.
> Connecting
> USB local printer to the thin clients and accessing Win2003 server via
> RDP.
> Once logged in, I can create a printer which prints to the WinTerm's USB
> local printer, however, once I log off and log back on, the printer
> doesn't
> work. The printer icon is still there, but if I check the port settings,
> the
> port I created in the last session is listed as an "Inactive TS port," and
> there's a new port available for the USB local printer.
>
> If I change the printer to print to that new port, it works, but then on
> log
> off and log back on, that port is listed as Inactive, etc. etc. etc. (and
> even if that worked, I wouldn't want users to have to do it).
>
> So, I need to know what to set up on the server to recognize the thin
> client's port on logon 2 as being the same port set up on logon 1. Any
> takers?
>
> So, I need to know how I can
>
>
 
Re: Inactive TS port

Thanks - in case anyone else runs into this, here's a link (that was linked
in the link Ayesha sent me) which describes how I solved the problem:

http://support.microsoft.com/?kbid=239088

The problem was that the terminal server didn't have the right drivers for
the printers that the client had attached, and didn't have the exact same
name. So, the client had a printer called "HP LaserJet 1200" and the TS had
a driver for "HP LaserJet 1200 Series PCL" - I had to create a file in the
c:\winnt\inf directory to tell the TS what driver to use when autoconnecting
to the client printer.

This may get cumbersome as I roll these out, unless I tell people not to use
their local printers (good luck, I've been trying to do that for years).

"Ayesha Mascarenhas [MSFT]" wrote:

> Please tale a look at a similar issue online and see if the resolution helps
> fix your issue:
> http://www.pcreview.co.uk/forums/thread-1614545.php
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "BFH" <BFH@discussions.microsoft.com> wrote in message
> news:C9A61894-1082-4AB2-A82B-9C7AE835D62B@microsoft.com...
> > Installing Wyse Thin Clients, using their OS, not Win CE or such.
> > Connecting
> > USB local printer to the thin clients and accessing Win2003 server via
> > RDP.
> > Once logged in, I can create a printer which prints to the WinTerm's USB
> > local printer, however, once I log off and log back on, the printer
> > doesn't
> > work. The printer icon is still there, but if I check the port settings,
> > the
> > port I created in the last session is listed as an "Inactive TS port," and
> > there's a new port available for the USB local printer.
> >
> > If I change the printer to print to that new port, it works, but then on
> > log
> > off and log back on, that port is listed as Inactive, etc. etc. etc. (and
> > even if that worked, I wouldn't want users to have to do it).
> >
> > So, I need to know what to set up on the server to recognize the thin
> > client's port on logon 2 as being the same port set up on logon 1. Any
> > takers?
> >
> > So, I need to know how I can
> >
> >
>
>
 
Back
Top