Can`t add client printer in RDP session, please hlp
Tags:
-
Printers
-
Servers
-
Windows
- Product
Last response: in Windows 2000/NT
Anonymous
November 2, 2004 2:41:33 PM
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)
hi all.
server win2003
client server 2000
RDP Client 5.2.3790.0
printer Canon LBP 810
Drivers set up in server and client, the driver name the same
RDP, server user have enabling client mapping properties
RDP session have enabling client mapping properties
The printer not autocreate in session
Then i try connect printer via Printers - Add Printer - Network printer -
Browse for a printer -
Client Network - Client... , Client folder not expand.
what i must check step by step to solve it?
Max Rodkin
hi all.
server win2003
client server 2000
RDP Client 5.2.3790.0
printer Canon LBP 810
Drivers set up in server and client, the driver name the same
RDP, server user have enabling client mapping properties
RDP session have enabling client mapping properties
The printer not autocreate in session
Then i try connect printer via Printers - Add Printer - Network printer -
Browse for a printer -
Client Network - Client... , Client folder not expand.
what i must check step by step to solve it?
Max Rodkin
More about : add client printer rdp session hlp
Anonymous
November 8, 2004 7:17:52 AM
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)
Hi,
I understand the driver for Canon was installed from the OEM disk supplied
by Canon and this is not MS certified driver, right?
First check Event Viewer for error messages in System tree. In case you see
any error with ID 1111, 1105 or 1106 all you need is custom INF file that
will map client and server side drivers. This is very well described in KB
article
Q239088 "Windows 2000 Terminal Services Server Logs Events 1111, 1105, and
1106"
Even when you installed same new driver on both sides the custom INF file
may still be needed. This custom INF file is the must if you want to map OEM
driver on the client to any compatible driver on the server side.
Make also sure:
1. on client when you start mstsc check if Printers check box is checked
(under Local Resources tab)
2. on server side run TSCC.msc and navigate to RDP-TCP Properties => click
Client Settings tab
verify you have "Use connection settings from user settings" checked
verify check boxes for Printer mapping, LPT port mapping and COM port
mapping under section "Disable the following:" are NOT checked
3. You may also check GP settings but for printing redirection the default
setting is to enable so if you haven’t change the settings it is not
relevant.
Please let me know what you found and if this is still not working for you.
If this is the case I will try to repro in our lab but I will need the exact
repro steps.
--
Zenon Pilat (MS)
---
This posting is provided "AS IS" with no warranties, and confers no rights
---
"Max Rodkin" <maxi4@mail.ru> wrote in message
news:ehyvx6JwEHA.1148@TK2MSFTNGP10.phx.gbl...
> hi all.
> server win2003
> client server 2000
> RDP Client 5.2.3790.0
> printer Canon LBP 810
> Drivers set up in server and client, the driver name the same
> RDP, server user have enabling client mapping properties
> RDP session have enabling client mapping properties
> The printer not autocreate in session
> Then i try connect printer via Printers - Add Printer - Network printer -
> Browse for a printer -
> Client Network - Client... , Client folder not expand.
> what i must check step by step to solve it?
> Max Rodkin
>
>
>
Hi,
I understand the driver for Canon was installed from the OEM disk supplied
by Canon and this is not MS certified driver, right?
First check Event Viewer for error messages in System tree. In case you see
any error with ID 1111, 1105 or 1106 all you need is custom INF file that
will map client and server side drivers. This is very well described in KB
article
Q239088 "Windows 2000 Terminal Services Server Logs Events 1111, 1105, and
1106"
Even when you installed same new driver on both sides the custom INF file
may still be needed. This custom INF file is the must if you want to map OEM
driver on the client to any compatible driver on the server side.
Make also sure:
1. on client when you start mstsc check if Printers check box is checked
(under Local Resources tab)
2. on server side run TSCC.msc and navigate to RDP-TCP Properties => click
Client Settings tab
verify you have "Use connection settings from user settings" checked
verify check boxes for Printer mapping, LPT port mapping and COM port
mapping under section "Disable the following:" are NOT checked
3. You may also check GP settings but for printing redirection the default
setting is to enable so if you haven’t change the settings it is not
relevant.
Please let me know what you found and if this is still not working for you.
If this is the case I will try to repro in our lab but I will need the exact
repro steps.
--
Zenon Pilat (MS)
---
This posting is provided "AS IS" with no warranties, and confers no rights
---
"Max Rodkin" <maxi4@mail.ru> wrote in message
news:ehyvx6JwEHA.1148@TK2MSFTNGP10.phx.gbl...
> hi all.
> server win2003
> client server 2000
> RDP Client 5.2.3790.0
> printer Canon LBP 810
> Drivers set up in server and client, the driver name the same
> RDP, server user have enabling client mapping properties
> RDP session have enabling client mapping properties
> The printer not autocreate in session
> Then i try connect printer via Printers - Add Printer - Network printer -
> Browse for a printer -
> Client Network - Client... , Client folder not expand.
> what i must check step by step to solve it?
> Max Rodkin
>
>
>
endy
March 31, 2009 6:40:59 AM
stevetaylor
March 3, 2012 10:33:48 PM
We also had same problem with Canon printer and then we found great solution at http://terminalworks.com/remote-desktop-printing. working great, low price an no problems anymore. hope it helps
!