Setting up IP-Based Printer w/Thin-clients

  • Thread starter Thread starter porbarfarms@gmail.com
  • Start date Start date
P

porbarfarms@gmail.com

Guest
We are using Windows 2003 Server SP1 as a Terminal Server (TS) with
Windows-based (WinCE5.0) Thin-clients connecting to it using RDP from
a remote office through a router-to-router IPSec VPN.

The remote office is going to have printers that are connected
directly to the network via Ethernet. There are no fat-clients or
servers at the remote office.

The Thin-clients need to print to these IP-based printers from the
application that they are using on the TS.

At the TS, we understand that we have to install the printer drivers--
note that these drivers cannot be installed Thin-clients--nor should
this be necessary-right?
We also understand that we should only install drivers on the TS that
came with the Windows 2003 OS. So, if we do not see the printers
listed in Windows 2003 OS, how do we install the driver? For example
we want the thin-clients to print to a HP 2015dn printer, and here are
the steps we are using at the TS:

1. Add Printer
2. Choose Local Printer...
3. Choose "Create new port" -choose HP Standard TCP/IP
4. Supply Printer's IP Address
5. Now, we get the list of available printers and the HP2015 is not
listed. And there is the "Have disk" choice, etc
6. Now what? Where should the driver come from and should it be a PCL
5e or PCL6 driver.

Once this is completed, do the Thin-clients see the HP 2015dn listed
as available printers?

Thanks
 
RE: Setting up IP-Based Printer w/Thin-clients

First download the correct driver from the HP Website. Install the printer on
the TS as you described, click have disk, browse to the downloaded driver.
Complete the wizard. Now the printer is installed on the terminal server. If
your client makes a connection the TS, the printer is available.

"porbarfarms@gmail.com" wrote:

> We are using Windows 2003 Server SP1 as a Terminal Server (TS) with
> Windows-based (WinCE5.0) Thin-clients connecting to it using RDP from
> a remote office through a router-to-router IPSec VPN.
>
> The remote office is going to have printers that are connected
> directly to the network via Ethernet. There are no fat-clients or
> servers at the remote office.
>
> The Thin-clients need to print to these IP-based printers from the
> application that they are using on the TS.
>
> At the TS, we understand that we have to install the printer drivers--
> note that these drivers cannot be installed Thin-clients--nor should
> this be necessary-right?
> We also understand that we should only install drivers on the TS that
> came with the Windows 2003 OS. So, if we do not see the printers
> listed in Windows 2003 OS, how do we install the driver? For example
> we want the thin-clients to print to a HP 2015dn printer, and here are
> the steps we are using at the TS:
>
> 1. Add Printer
> 2. Choose Local Printer...
> 3. Choose "Create new port" -choose HP Standard TCP/IP
> 4. Supply Printer's IP Address
> 5. Now, we get the list of available printers and the HP2015 is not
> listed. And there is the "Have disk" choice, etc
> 6. Now what? Where should the driver come from and should it be a PCL
> 5e or PCL6 driver.
>
> Once this is completed, do the Thin-clients see the HP 2015dn listed
> as available printers?
>
> Thanks
>
>
>
 
Re: Setting up IP-Based Printer w/Thin-clients

On Jan 8, 4:19 pm, Bart Van Vugt
<BartVanV...@discussions.microsoft.com> wrote:
> First download the correct driver from the HP Website. Install the printer on
> the TS as you described, click have disk, browse to the downloaded driver.
> Complete the wizard. Now the printer is installed on the terminal server. If
> your client makes a connection the TS, the printer is available.
>
>
>
> "porbarfa...@gmail.com" wrote:
> > We are using Windows 2003 Server SP1 as a Terminal Server (TS) with
> > Windows-based (WinCE5.0) Thin-clients connecting to it using RDP from
> > a remote office through a router-to-router IPSec VPN.
>
> > The remote office is going to have printers that are connected
> > directly to the network via Ethernet. There are no fat-clients or
> > servers at the remote office.
>
> > The Thin-clients need to print to these IP-based printers from the
> > application that they are using on the TS.
>
> > At the TS, we understand that we have to install the printer drivers--
> > note that these drivers cannot be installed Thin-clients--nor should
> > this be necessary-right?
> > We also understand that we should only install drivers on the TS that
> > came with the Windows 2003 OS. So, if we do not see the printers
> > listed in Windows 2003 OS, how do we install the driver? For example
> > we want the thin-clients to print to a HP 2015dn printer, and here are
> > the steps we are using at the TS:
>
> > 1. Add Printer
> > 2. Choose Local Printer...
> > 3. Choose "Create new port" -choose HP Standard TCP/IP
> > 4. Supply Printer's IP Address
> > 5. Now, we get the list of available printers and the HP2015 is not
> > listed. And there is the "Have disk" choice, etc
> > 6. Now what? Where should the driver come from and should it be a PCL
> > 5e or PCL6 driver.
>
> > Once this is completed, do the Thin-clients see the HP 2015dn listed
> > as available printers?
>
> > Thanks- Hide quoted text -
>
> - Show quoted text -

Ok -that's what we thought. But when we read that we should only
install printer drivers from what is available on the Native OS, and
not 3rd party drivers, it is confusing. The native OS would never have
all the printer drivers since new printers are made everyday! So, we
assumed that HP would be a 3rd-party driver supplier and we assumed
wrong.

Thanks -that's what we will do.
 
Re: Setting up IP-Based Printer w/Thin-clients

compsosinc@gmail.com wrote on 08 jan 2008 in
microsoft.public.windows.terminal_services:

> On Jan 8, 4:19 pm, Bart Van Vugt
> <BartVanV...@discussions.microsoft.com> wrote:
>> First download the correct driver from the HP Website. Install
>> the printer
> on
>> the TS as you described, click have disk, browse to the
>> downloaded driver.
>
>> Complete the wizard. Now the printer is installed on the
>> terminal server.
> If
>> your client makes a connection the TS, the printer is
>> available.
>>
>>
>>
>> "porbarfa...@gmail.com" wrote:
>> > We are using Windows 2003 Server SP1 as a Terminal Server
>> > (TS) with Windows-based (WinCE5.0) Thin-clients connecting to
>> > it using RDP from a remote office through a router-to-router
>> > IPSec VPN.
>>
>> > The remote office is going to have printers that are
>> > connected directly to the network via Ethernet. There are no
>> > fat-clients or servers at the remote office.
>>
>> > The Thin-clients need to print to these IP-based printers
>> > from the application that they are using on the TS.
>>
>> > At the TS, we understand that we have to install the printer
>> > drivers-- note that these drivers cannot be installed
>> > Thin-clients--nor should this be necessary-right?
>> > We also understand that we should only install drivers on the
>> > TS that came with the Windows 2003 OS. So, if we do not see
>> > the printers listed in Windows 2003 OS, how do we install the
>> > driver? For example we want the thin-clients to print to a HP
>> > 2015dn printer, and here are the steps we are using at the
>> > TS:
>>
>> > 1. Add Printer
>> > 2. Choose Local Printer...
>> > 3. Choose "Create new port" -choose HP Standard TCP/IP
>> > 4. Supply Printer's IP Address
>> > 5. Now, we get the list of available printers and the HP2015
>> > is not listed. And there is the "Have disk" choice, etc
>> > 6. Now what? Where should the driver come from and should it
>> > be a PCL 5e or PCL6 driver.
>>
>> > Once this is completed, do the Thin-clients see the HP 2015dn
>> > listed as available printers?
>>
>> > Thanks- Hide quoted text -
>>
>> - Show quoted text -
>
> Ok -that's what we thought. But when we read that we should only
> install printer drivers from what is available on the Native OS,
> and not 3rd party drivers, it is confusing. The native OS would
> never have all the printer drivers since new printers are made
> everyday! So, we assumed that HP would be a 3rd-party driver
> supplier and we assumed wrong.
>
> Thanks -that's what we will do.

But HP is of course a 3rd party supplier! Anything that is not
native is 3rd party, and native is what came with the Windows
installation CD.

But see your other thread in this newsgroup on the same issue for
more information.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
Back
Top