"I cound't found the " Printer and Faxes Folder, start Server properties)"
To open Server Properties from "Printer and Faxes" right click on the white
space of this window => select "Server Properties" from the menu and left
click on the selection. Print Server Properties dialog page should start =>
left click on the Drivers tab=> and left click on the Add button => "Add
Printer Driver Wizard should start.
You may also try as the alternative:
Client side:
First try to install in-box driver for your printer - do not install OEM
driver (uninstall if already installed). If you haven't found the exact
driver in the list, try to find close in name type. Install the driver and
print Test Page (Right click on the installed printer queue, scroll down to
Properties and Left Click on properties. On the "<PrinterName> Properties"
dialog box find Print Test Page button). If your TP looks fine just use this
driver for your printer. If not delete it and try another one. This way we
will eliminate problem with compatibility for the OEM driver and you can
forget all the additional steps you will have to do to make Custom INF file
to work.
Now start the connection to the TS server and wait for the printer to be
redirected. It should have the same name as the client one but now the
client computer name and session should be included in the redirected
printer name. Open document and print selecting this redirected printer. It
should work without any additional step. If not - the configuration on your
server or the client is set to block the printing redirection. Remember -
printing redirection is enabled by default so if you haven't change the
setting on client or server it should work. If you use inbox driver (the one
supplied by the system not the OEM one installed from the OEM CD) you need
do nothing to enable printing redirection.
If this is still not working check the setting on the client app (open
mstsc.exe => expand the Option>> => click on the Local Resources Tab => make
sure Printers are checked in Local devices group)
Server side:
If this (client property) is checked and you have problem with printer
redirection you have to connect to the console of the server and check the
General Policy to verify someone did not explicitly made the restriction for
printing redirection.
If this is OK - no restrictions for printing redirection - open tscc.msc =>
double click on the right panel RDP-Tcp connection => click on "Client
Settings" tab => verify
"Use connection settings from user settings" is checked
You do not disable printer mapping or any port mapping
If this is not working????????
Go back to the client open registry key
"HKEY_CURRENT_USER\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR\Your_installed_printer_name"
and delete this key
Stert the client program and connect to TS with the same inbox installed
printer (deleting this key you will only delet the cached setting for this
printer - not the data or printer driver)
Please let us know this is working
Ch
--
Zenon Pilat (MS)
---
This posting is provided "AS IS" with no warranties, and confers no rights
---
lux said:
I tried to install my remote printer we got the following error " Printer drivers not install"
We are using windows 2000 server, could please tell me setup of installing the printer drives.
base on your reply to me, I cound't found the " Printer and Faxes
Folder, start Server properties)
Please help me out..
----- Zenon Pilat (MS) wrote: -----
I do not understand why you need the remote/network printer.
If your client side printer use some OEM drivers what you need to do is to
install the same driver on the server (from Printers and Faxes folder start
Server Properties => click on Drivers tab and click on Add button => use
Have a Disk to install out of box OEM driver) and create CUSTOM INF file.
All of this has to be done on the server.
I believe this will solve the problem no matter what kind of network you are
using.
This are instructions to install CUSTOM INF file (do not forget to install
the driver on the server)
Custom INF file may help to run OEM not supported drivers. It maps client
and server side driver and two registry key must be added on the server side
for file name and section name.
1. create INF file - example of CUSTOM.INF file
[OEM Printer Mapping]
"Canon BJC-8200" = "Canon BJC-8200 (BJRSTR)" ;installed OEM driver = OEM
driver on the server
2. two reg values for HKEY_LOCAL_MACHINE\...\rdpwd keys added
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\Wds\rdpwd\PrinterMappingINFName = "c:\windows\inf\CUSTOM.INF "
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\Wds\rdpwd\PrinterMappingINFSection = "OEM Printer Mapping"
--
Zenon Pilat (MS)
---
This posting is provided "AS IS" with no warranties, and confers no rights
---
Lux said:
We have 2 windows 2000 server and we setup terminal client in 12
location.
Their login to our server through VPN connection through DHCP (DHCP
configure in Pix firewall) it is not a Site to site VPN conectivity. As we
know that site to site vpn I can configure printer and map the network
drive but in DHCP how to configure the printer. We try to setup the remote
printer. we couldn't. Please help out, so that we can take print in our
remote location itself.
