Re: Setup Local Printing

From: Ron Boetger (rboetger_at_bblink.net)
Date: 08/05/04


Date: Wed, 04 Aug 2004 23:38:54 -0400

OK I finally had time to think and play around a little more. I have
a Windows 2003 Server in my office. It has the same TCP/IP connection
to the HP 4050 PS that my laptop has. I use Remote desktop client
from my server after configuring local resources to connect disk
drives and printers.

The next screen was a warning that only the disk drives would be
connected. After the session started I looked at the printers on TS
server I had remoted to and there were all my local printers, even
ones that I did not install the print drivers for on the TS Server.
I sent a test page through the remote client to the 4050 and it
printed at my office. So something is messed up on my laptop.

Also I saw a 1111 error for the Microsoft Fax.

This being said, any ideas how to fix the laptop.

Thanks

Ron

On Tue, 03 Aug 2004 12:39:55 -0700, "Vera Noest [MVP]"
<vera.noest@remove-this.hem.utfors.se> wrote:

>OK, let's try to go to the bottom with this.
>
>Yes, network printers can be redirected just like locally attached
>printers. This was already possible in W2K TS. The only
>requirement is that the rdp client is at least version 5.1.
>Better still, use the latest client, version 5.2.3790,
>downloadable from:
>
>http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
>4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
>
>The fact that you don't see these Events is a bit puzzling, I
>agree. But I would still check those driver names.
>
>About the printer driver name: from KB 239088:
>"If you do not know the printer driver name to add to the right
>side of the equal sign in the .inf file, you can install the
>printer on the server. After the printer is installed the printer
>driver name appears to the right of "Model:" under the "General"
>tab of the printer properties."
>
>Even if both the XP and the 2003 driver are native Microsoft
>drivers for the same printer model, it is not at all guaranteed
>that the driver *names* are exactly the same.
>On my XP, the printer driver name for your model is called:
>"HP LaserJet 4050 Series PS"
>According to the Client Printer Autocreation Matrix at
>PrintingSuppoprt.com at
>http://www.printingsupport.com/matrix.htm
>the mapping that you need to make this work is:
>
>"HP LaserJet 4050 Series PS" = "HP LaserJet 4050 Series PCL"
>
>If it still doesn't work with the latest rdp client and the driver
>names match or you have used the above mapping, could you try the
>same connection with a different XP client? Make the same
>connection on the client to the same printer, connect to the same
>network, and start a TS session?
>
> --
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
>Ron Boetger <rboetger@bblink.net> wrote in
>news:ktbvg0l7e0dl4jcph3d7nutkdr37cgu0le@4ax.com:
>
>> I have re-read all of the posts and the KB - Maybe I am looking
>> in all the wrong places but here goes!
>>
>> There are no errors 1111, 1105, or 1106 in the Event Viewer
>> under System or any of the other items in the Event Viewer.
>> Since I am not getting these errors I am hesitant to mess with
>> the registry as the KB suggests.
>>
>> In the "Printers & Faxes" on both the Server and the Workstation
>> the printer is named HP LaserJet 4050 PS. I have not been able
>> to find the name of the actual printer driver. They are the
>> drivers that Microsoft supplies for the HP 4050 with the OS's
>> (not supplied from HP) I would guess they are the same.
>>
>> According to the KB Article 239088 for Windows 2000 (I am using
>> Windows 2003) it is only the local ports that get redirected. I
>> want to redirect my network printer (which I thought Windows
>> 2003 could do).
>>
>> I don't know what to do next?
>>
>> Thanks
>>
>> Ron
>>
>>
>> On Mon, 02 Aug 2004 07:03:38 -0700, "Vera Noest [MVP]"
>> <Vera.Noest@remove-this.hem.utfors.se> wrote:
>>
>>>Ron, did you ever read that KB article?
>>>The answers to all of your questions are spelled out there.
>>>
>>> --
>>>Vera Noest
>>>MCSE,CCEA, Microsoft MVP - Terminal Server
>>>http://hem.fyristorg.com/vera/IT
>>>*----------- Please reply in newsgroup -------------*
>>>
>>>Ron Boetger <rboetger@bblink.net> wrote in
>>>news:72nqg09ehold088bis6hgp8c94b590q7ve@4ax.com:
>>>
>>>> Both the printer on my WinXP laptop and the new server are HP
>>>> LaserJet 4050 PS. I cant find any error in the event log with
>>>> the error numbers you stated or any other print error. In
>>>> what directory do I create the ntprintsubs.inf file
>>>>
>>>> Thanks
>>>>
>>>> Ron
>>>>
>>>> On Sun, 01 Aug 2004 13:33:22 -0700, "Vera Noest [MVP]"
>>>> <vera.noest@remove-this.hem.utfors.se> wrote:
>>>>
>>>>>Ron,
>>>>>
>>>>>Maybe I have not expressed myself clear enough, but I have
>>>>>already answered this in my first post:
>>>>>
>>>>>>If you still don't see your printer in your ts session, the
>>>>>>most likely cause is a missing printer driver on the server,
>>>>>>or a mismatch in the printer driver name.
>>>>>>
>>>>>>Check the EventLog on the TS, which should report what
>>>>>>printer driver is missing or not recognized, and then solve
>>>>>>the problem by
>>>>>>creating a custom ntprintsubs.inf file, and map the local
>>>>>>printer driver name to the name of a native printer driver on
>>>>>>the server.
>>>>>>
>>>>>>Here are the details:
>>>>>>
>>>>>>239088 - Windows 2000 Terminal Services Server Logs Events
>>>>>>1111, 1105, and 1106
>>>>>>http://support.microsoft.com/?kbid=239088
>>>>>
>>>>>As an example, if the name of the driver on your laptop is
>>>>>something like "HP LaserJet 4050" and the name of the driver
>>>>>on the server is something like "HP LaserJet 4050 Series",
>>>>>then the names don't match and you must create a custom
>>>>>ntprintsubs.inf, as explained in KB article 239088.
>>>>>
>>>>>Once the server recognizes your local printer, it will be
>>>>>autocreated within your session. There's no need to connect to
>>>>>it manually.
>>>>>
>>>>> --
>>>>>Vera Noest
>>>>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>http://hem.fyristorg.com/vera/IT
>>>>> --- please respond in newsgroup, NOT by private email ---
>>>>>
>>>>>Ron Boetger <rboetger@bblink.net> wrote in
>>>>>news:povpg05ailrv8r38qpudo4fsidj4jimlbl@4ax.com:
>>>>>
>>>>>> Let me start over again. I don't think I have given enough
>>>>>> information.
>>>>>>
>>>>>> I am running a Windows XP laptop in my office. I have a HP
>>>>>> 4050 printer with a Jet Direct card. I am printing to it
>>>>>> through my office network. I am attached to the internet
>>>>>> through a DSL with dynamic IP.
>>>>>>
>>>>>> At my customers site we have a new Windows 2003 Server. DSL
>>>>>> with a static IP. I have turned on Remote Desktop on the
>>>>>> server and I am able to use Remote Desktop Client fomr my
>>>>>> laptop and attach to the server from my office. I have
>>>>>> loaded the HP 4050 driver on to the Windows 2003 server and
>>>>>> have named it the same as mine on the laptop.
>>>>>>
>>>>>> With my Remote Desktop Client I am able to see my local
>>>>>> laptop drives during the remote session and I am able to
>>>>>> copy files from the Server to my laptop during the remote
>>>>>> session. I am however not able to print to my HP 4050 from
>>>>>> the server during a remote session.
>>>>>>
>>>>>> My Remote Desktop Client has Printer and Disk Drives checked
>>>>>> under "Options - Local Resources - Local Devices".
>>>>>>
>>>>>> My next step was to enable Terminal Services and follow your
>>>>>> directions in the above posts. I admit this is my lack of
>>>>>> knowledge. I don't know what I am looking for nor do not see
>>>>>> my local printer showing up on the Windows 2003 server under
>>>>>> printers and faxes. I have gone into the "PORTS" properties
>>>>>> of the printer on the server and do not see anywhere to
>>>>>> connect to my printer at the office.
>>>>>>
>>>>>> Many Thanks for all your help.



Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: xp pro sharing printer
    ... How to troubleshoot network printing problems in Windows XP ... SMB-connected print server ... Incompatible print driver ... and then redirect the port to the network server. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)