C
Chris Mackie
A problem!!
At the moment I use Terminal Services with Windows 2K and the newer Remote
Desktop Client. When PCs want to print from an application they can use any
locally attached printer or any printer that prints to a network queue ...
whether the printer has a queue associated with a Microsoft shared printer
or it is a NetWare queue. However if the printer is printing directly to an
IP address of a JetDirect box or similar network device this printer will
not appear in the list of available printers when the client goes to print
from terminal services.
It is very popular to set up PCs to print directly to a device with IP
printing, so it would be useful to have the printers available when a person
is using print queue redirection with the Terminal Services Client.
Does anbody know of a way to get this to work .... even if it is a very
devious method .... any idea would be useful!!??
.... or vice-versa .... am I missing something here???
Regards,
Chris Mackie.
At the moment I use Terminal Services with Windows 2K and the newer Remote
Desktop Client. When PCs want to print from an application they can use any
locally attached printer or any printer that prints to a network queue ...
whether the printer has a queue associated with a Microsoft shared printer
or it is a NetWare queue. However if the printer is printing directly to an
IP address of a JetDirect box or similar network device this printer will
not appear in the list of available printers when the client goes to print
from terminal services.
It is very popular to set up PCs to print directly to a device with IP
printing, so it would be useful to have the printers available when a person
is using print queue redirection with the Terminal Services Client.
Does anbody know of a way to get this to work .... even if it is a very
devious method .... any idea would be useful!!??
.... or vice-versa .... am I missing something here???
Regards,
Chris Mackie.