Re: RDP Printer Issues from outside vendor
Printing is done within the rdp session, when you use a redirected
local printer.
So the problem is not your firewall, but that his printer is not
redirected.
Basically, there are 2 areas where printer redirection can fail.
1. redirection is not attempted at all
Solution: check the configuration of printer redirection in the RDP
client and on the Terminal Server, update the RDP client to the
version that comes with Windows Server 2003 (located in C:\WINDOWS
\system32\clients\tsclient\win32\msrdpcli.msi) or apply KB article
302361 to get support for redirection of non-standard local port
names, including tcp/ip ports.
2. redirection is attempted, but fails because the server doesn't
have a driver for the printer
Solution: whatever you do, do not install a 3rd party printer
driver on the Terminal Server, unless it is a Windows Hardware
Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
TS-compatible, and some are known to crash your printer spooler or
the whole server. In stead, map the printer to a native driver by
creating a custom ntprintsubs.inf file, as described in KB article
239088.
Check the EventLog on your server at the time the vendor connected.
If you don't see any printer-related records, redirection wasn't
even attempted. Most likely, you will see warnings and errors
related to printer redirection, in which case you have a missing
driver problem.
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106 (applies to 2003 as well)
http://support.microsoft.com/?kbid=239088
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?aXR0ZWNoaWUxMDA=?=
<ittechie100@discussions.microsoft.com> wrote on 02 nov 2007 in
microsoft.public.windows.terminal_services:
> I have a vendor that needs to connect into my Terminal server
> and run some reports that in turn need to be printed back to
> their printers. Is there a easy way to set this up ?
>
> I have a netgear firewall, configured it to allow 3389 to my
> terminal server. He can connect without issue using RDP, just
> can't see his local printers? My private range is 192.168.1.0
> and his private range is 192.168.2.0.
>
> I was assuming that after he connected he would be able to
> communicate with his printer...he tried pinging his printer
> 192.168.2.24 after connecting rdp session and gets reply timed
> out....Any help would be appreciated...sincerely