Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Terminal server won't print Fox
Message
De
07/10/2002 11:21:32
 
 
À
06/10/2002 16:09:19
Information générale
Forum:
Windows
Catégorie:
Serveur terminal
Divers
Thread ID:
00708218
Message ID:
00708378
Vues:
8
>Hi. I am running VFP7 runtime (sp1) on Win98 workstations hosted by a Win2000 Terminal Server. NONE of my Fox apps will print. Everything else will. Fox has the appearance of sending the data to the default printer, but the printer is silent.
>
>Any help would be appreciated.
>
>Randy
>
>Question also submitted on Windows forum.

Randy,

First there are more than a few printer-related problems with WTS printing to local printers remapped via the TSAC/RDP client; I've found it absolutely necessary to add the drivers for each remote printer to WTS (Open the Printers applet, right click in the empty space, select Server Properties, and add the print drivers via the Print Drivers tab - Add button.) I've then attached the printer to TS via the appropriate TSxxxx port through an Admin session at each local station. And, I've also needed to tell Terminal Server to remap local printers into the WTS session.

Once that is done, you need to, at a minimum, alter each FRX as follows:

(1) Completely delete the content of the Tag and Tag2 fields of the first record of the FRX.

(2) Remove at least the following lines from the Expr field of the first record:

DEVICE=
OUTPUT=

If not all printers have similar characteristics (in my case, I have remoted barcode printers whose print quality and paper width vary) you may also need to delete or modify the following to their least common denominator (aka LCD) - ie if some printers can print at 600 DPI but others only at 200DPI, change the PRINTQUALITY and YRESOLUTION to 200.

PAPERSIZE *
DEFAULTSOURCE
PRINTQUALITY *
YRESOLUTION *
TTOPTION *
COLOR
DUPLEX
COLLATE
DRIVER **

* = Subject to either change to LCD or removal, if removed, these items should be defined in the Windows Printer setup for the local printer and the Print Server iterations; under the RDP, the Print Server will inherit the local printer settings at the time that the RDP session is started.)

** Unless completely bypassing spooler functionality, do not change this from DRIVER=winspool - if by chance you're using an alternative driver on the local station, remove this line from the Expr field. It's generally safe to remove this.

I've also had problems with SET PRINTER TO in RDP settings; I've found that I get much more reliable results using the WSH's Wscript.Network object's SetDefaultPrinter() method to assign printers to alternative locations; as a reminder, do not set it to LPT1: if the WTS box has a printer located on its LPT1:, instead, assign the equivalent TSxxxx port associated with the local print device. You should be able to set the printer to a UNC resolvable in the context of the Terminal Server; if you need to redirect to a LAN printer on a remote site, install it on the client and make it the default printer.

All custom paper sizes need to be defined on both the local station running RDP/TSAC and the WTS box.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform