Re: Network printing?

From: Judge Dredd (123_at_123.com)
Date: 09/17/04


Date: Thu, 16 Sep 2004 23:24:25 -0400

It's a Konica 7060 with the IP302 print controller. The driver for it
is native in Server 2003. It's just that the client workstation is
using it as a network printer, and it seemed like everything I found
about network printing on the Microsoft KB led me to believe that was
not supported on the TS 2003. I will definitely download that updated
RDP client and give it a go.
Thanks again for sharing your knowledge, it's very much appreciated...
On Wed, 15 Sep 2004 22:25:03 -0700, "Patrick Rouse [MVP]"
<PatrickRouseMVP@discussions.microsoft.com> wrote:

>Actually that's backwards. What you need to worry about is if the printer
>installed on your local computer has a matching driver on the 2003 server.
>
>When a client logs onto an RDP Session, the server trys to auto create any
>client printers. If the server has a matching driver, the printer is auto
>created. If there is not a driver on the server that matches the client
>printer driver, an error will be wrinten to the server's event log indicating
>which printer driver it needs to auto create the printer.
>
>If you didn't need to load a 3rd party printer driver on the Windows XP
>machine, the printer driver is most likely built-into 2003.
>
>If you had to use the manufacturer's disk to install your printer on the XP
>machines, the printer may not be natively supported by 2003, so you'd have to
>map it to a built-in driver.
>
>What kind of printer (model)?
>
>"Judge Dredd" wrote:
>
>> Ok, let me give you a little more info (thanks for the reponse, by the
>> way)
>> The clients are XP Pro, the terminal server is 2003. Is the driver
>> built into 2003 the matching driver for xp?
>>
>> On Mon, 13 Sep 2004 20:47:09 -0700, "Patrick Rouse [MVP]"
>> <PatrickRouseMVP@discussions.microsoft.com> wrote:
>>
>> >Just use Remote Desktop Client 5.2.3790 and this is fully supported. If you
>> >add the printer to each client as a local TCP/IP Printer and a matching
>> >driver exists on the terminal server, it will be autocreated in each user's
>> >session.
>> >
>> >The other option, if the sites are connected via VPN is to add the printer
>> >as a local TCP/IP Printer on the Terminal Server.
>> >
>> >RDP Client 5.2.3790 here:
>> >http://www.workthin.com/tsdown.htm
>> >
>> >Printing INfo:
>> >http://www.workthin.com/tsp.htm
>> >
>> >Patrick Rouse
>> >Microsoft MVP - Terminal Server
>> >http://www.workthin.om
>> >
>> >"Judge Dredd" wrote:
>> >
>> >> Here's the scenario:
>> >> A remote office, no server. A network printer, prints to an IP port on
>> >> the printer. I want to be able to have users print to that network
>> >> printer via Terminal Server; without using a 3rd party option like
>> >> thinprint. I would also not like to share the printer on another
>> >> workstation and then capture the printer port from the terminal server
>> >> workstation. Any help greatly appreciated!
>> >>
>>
>>



Relevant Pages

  • Re: SBS 2003 - SBS 2008 migration issues
    ... DHCP cannot work properly with the hyper-v role, and probably DNS, neither will the configuration wizards. ... clients losing the ability to use it after removing trend client, reseting winsock / removing network components / reinstalling teh client don't bring it back. ... When I add the 32 bit driver to the printer it simply tells me it's not a suitable driver, and to try adding the driver from a 32 bit client. ... If I install hyperV on the SBS 2008 will it run a win2k3 server? ...
    (microsoft.public.windows.server.sbs)
  • Re: Printer autocreation failing
    ... behaviour of a TS incompatible printer driver. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Tried installing that printer tray hotfix, ... Also tried updating the RDP client to the latest ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... reinstall the driver onto the TS box). ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... redirection of the driver to the LJ4) and functional. ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: .webpnp Driver file
    ... I think the client user will need to be an admin user if the driver contains ... Server is able to create webpnp file. ...
    (microsoft.public.windows.server.clustering)