Printer disappearing act.

[fuqqer69]

I have a user with Windows ME and a Deskjet 672C. We've installed a Deskjet 660C driver for them instead. Immediately after the printer is installed, the printer autocreates in her Citrix session. After an evening or two, her printer disappears. The problem went away for a couple of weeks, then it came back this last week. Any hints or directions?

Another thing, when she goes to print and scrolls through her printers, she sees all of the other printers installed on that server. But not her own.

Thanks for any help,

Jake

 

[zaneryrie]

Hi Jake,

You may need to redirect your printer drivers using the following information. I hope this helps.


=================================================
WTSUPRN.INF file specified redirection for certain types of printers.
HP 2100 Series
HP 900 Series
HP 600 Series

Please make a copy of the file wtsuprn.inf and name it wtsuprn.old prior to making any modifications!

=================================================
How to Set a Default Autocreated Printer withTSE and MetaFrame?

Synopsis:
This document was obtained from the Microsoft support site. Please follow this link for the original document, Article ID: Q221509.
Details:
Symptoms
Some workstation local print drivers pose problems for Windows NT Server, Terminal Server Edition. If the drivers have not been properly tested on Terminal Server, they can cause lockup problems on the server or even blue screen error messages.
Cause
The user usually has the ability to install local printers on his or her workstation. When the user connects to a Terminal Server session, the local printer is autocreated in the Terminal Server session. In very large companies, it is hard to control what printers and print drivers the user is loading on his or her local workstation.
As an example, the HP4000 print driver has caused problems on some Terminal Server installations. The print queue can stop responding (hang) and the jobs not print. The HP LaserJet 4 print driver has been shown to be very stable in this environment, and can be used as a substitute for the HP4000 print driver. To ensure that the HP LaserJet 4 driver is used ,if your user tries to load the HP4000 print driver or any other incompatible driver on his or her local workstation, there is a workaround to set the default printer driver used on the Terminal Server.
Resolution
There is a file on Terminal Server that can be modified to make the disparate printer driver names appear to be equal. This will set a default print driver that works properly on Terminal Server.
To make this modification, follow these steps:
NOTE: You need to know ahead of time the exact name of the print driver that can potentially be loaded on the client workstation. You can find this out by loading the print driver on a test workstation in local mode, not a Terminal Server session.
1. Click Start, Settings, and then Printers.
2. Right click the printer that is causing the problem.
3. Select Properties and then click the Details tab.
Write down the name of the printer driver. On computers running Windows 95 and Windows 98, the driver is listed in the Print using the following driver dialog box. On computers running Windows NT, the Driver box is on the General tab. The print driver name can vary on the workstation, depending on the operating system. Make sure you have the right driver name for the client workstation that is being used.
For example, if you see "HP LaserJet 4000 Series PCL 5e", write this name down, paying attention to all punctuation and case sensitivity.
4. On the Terminal Server computer, click Start, Settings, and then Printers.
5. Double-click the Add Printer icon, select My Computer, and then click Next.
6. In the Available Ports list box, select LPT1 and then click Next.
7. In the left pane, select the manufacturer of the printer you have installed on your workstation. In the right pane, scroll to the model of the printer you want the Terminal Server to load as the default driver; for example, "HP LaserJet 4". This is the server printer driver name that you want to use as the default printer. Write this name down.
8. Open the Wtsuprn.txt file. This file is located in the %SystemRoot%\System32 folder. The file is as follows:
=================================================
; WTSUPRN.TXT
;
; this is a template for wtsuprn.inf -- rename this file to wtsuprn.inf
;
; this file provides a mapping for client printers that have a name
; different from the server printer. this file is necessary because many
; printers for Win95 are different from their WinNT equivalent.
;
; Note: the driver for the server printer must be installed. See the
; WinFrame Concepts and Planning Guide.
;
[Identification]
OptionType = PRINTER
[ClientPrinters]
;
;Client Name Server Name
; | |
; | |
; \|/ \|/
;"HP LaserJet 4/4M" = "HP LaserJet 4"
;"HP LaserJet 4P/4MP" = "HP LaserJet 4P"
;"HP LaserJet 4 Plus/4M Plus" = "HP LaserJet 4 Plus"
;"HP LaserJet 4Si/4Si MX" = "HP LaserJet 4Si"
;"HP LaserJet 4V/4MV" = "HP LaserJet 4V"
;"HP LaserJet 5/5M - Enhanced" = "HP LaserJet 5"
;"HP LaserJet 5/5M - Standard" = "HP LaserJet 5"
;"HP LaserJet 5/5M PostScript" = "HP LaserJet 5"
;"HP LaserJet 5L (PCL)" = "HP LaserJet 5L"
;"HP LaserJet 5P/5MP (HP)" = "HP LaserJet 5P"
=================================================
Use this exact format to enter the previous information that you gathered from the workstation and the server. Leave out the semicolon (, this is to remark the line out.
Make sure you type the right driver under the proper column. Client name would be the workstation; server name is the Terminal Server; for example:
"HP LaserJet 4000 Series PCL 5e" = "HP LaserJet 4"
Save this file with a .inf extension and then close the Wtsuprn.txt file. From now on, if you have to add any other printers, add them to the Wtsuprn.inf file.
9. Log off the Terminal Server computer and log back on. Log on to your client workstation to a Terminal Server session; your printer is autocreated in the Terminal Server session printer's folder and you can print to your local printer.
Installing a New, Non-Native Print Driver
When you need to install a new print driver to your workstation, you will also have to install a print driver to the Terminal Server computer. Install the printer on the server as a local printer. Upon completion of the printer installation, delete the printer icon from the printer folder. The printer driver will be installed on the server and when you connect the workstation to the Terminal Server, the new printer is autocreated. If the printer driver names are different for the workstation (client) and the server, follow the same procedure as above to make them equal.
More Information
This will work for your printing needs. The only drawback is that some of the functionallity of the replaced printer driver on the server may not work on the newer printer. If you have concerns about this, contact the printer manufactuer.
Category: Printing ; Configuration
Product: MetaFrame
Version: Ver. 1.8 Build 663
Language : ENGUS
Date: 06/16/99 09:50:07 AM
Date Updated: 02/08/2000

 

[fuqqer69]

I use the wtsprnt.inf file rather than the wtsuprn.inf file. Is there any difference really? As I read the documentation, it seems like the wtsprnt.inf is the last resort end-all be all of the print aliasing files. Either way, the printer doesn't alias all that well. Could there be some other problem that I'm not aware of?

Thanks