Return to EaziTrack support page
Issue: Unable to print from an EaziTrack application, but able to print from other programs.
Applies to: Windows 98, Windows 2000 and XP.
This can happen if you are connecting to an EaziTrack server using terminal services, and is usually because the printer you are trying to print to is either a network printer or is connected via a USB cable.
To understand the problem we need to look at how printing from EaziTrack is
acheived.
When you log onto the EaziTrack server you are creating a 'Microsoft Terminal
Services' session between the server and the 'Terminal Services Client'
software on your PC. As part of this connection, the client (your PC) provides
the server with information about the printers available on the client, so that
the server can redirect any documents to your printers.
However, by default, the Terminal Services Client software only allows printing
to printers that are connected via an LPT or COM port. The printer may be a
shared printer connected to another PC on your network, but the Key is how it
is physically attached.
If the printer is a true network printer, i.e. it has its own built in network
port, or is connected via a network print-server, it will probably be using its
own IP Address and be shown on your PC as connected via a TCP/IP printer
port. If the printer is connected to a PC using a USB Cable, then it will
probably be shown as connected via a USB port.
In either of these cases, the client will not inform the server that the
printer exists and so the server will be unable to use it.
The first step is therefore to identify the method the printer uses to connect
to your PC.
To do this:
Step 1.
For Windows 98 or 2000
Click 'Start' then 'Settings' then 'Printers'.
For For Windows XP.
Click 'Start' then 'Printers and Faxes'.
Step 2.
Right-Click on the printer and choose 'Properties'.
Click on the 'Ports' tab and you will see a list of ports such as LPT1, LPT2,
COM1, COM2, etc
Identify your printer and look at the ports description.
If the port is identified as a 'TCP/IP' or 'USB' port, then the above situation applies and you will need to apply the work-around shown below.
Work-Around.
This workaround allows Terminal Services Client to redirect to all port types
instead of just the default LPT and COM. This results in the server being
notified of the existence of the printer, allowing printing to take place (see
Note 1).
IMPORTANT! This work-around involves making changes to the Windows Registry and should only be attempted by proficient individuals. We take no responsibility for any damage, loss of data, security issue or system failure of any type caused by applying any of the changes decribed below.
1. Click Start, Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR
3. On the Edit menu, point to New, and then click DWORD value.
4. Type FilterQueueType, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the value box type FFFFFFFF, and then click OK.
Note 1.
For the server to send documents to the printer, the correct printer-driver
must be installed on the server. If, having applied the work-around described
above, you are still unable to print, please contact our technical support team
and provide the Make and Model of printer so that we can install the correct
driver for you.
Copyright EaziTrack 2000 all rights reserved.