Re: Printer autocreation failing

Hi Rob,

In an earlier post on Dec 07 12:18am, you said:

"...all printers are set up with a standard tcp/ip port."

When using printers attached to a standard tcp/ip port, you need to use the 5.2.3790.1830 client I recommended, *or* make the registry change in each user's registry, like Vera recommended:

302361 - Printers That Use Ports That Do Not Begin With COM, LPT,
or USB Are Not Redirected in a Remote Desktop or Terminal Services
Session
http://support.microsoft.com/?kbid=302361

If you do *not* do one or the other, the client will not make an attempt to redirect the printer, regardless of what drivers you have installed on the server, or what driver mappings you have created in the ntprintsubs.inf file.

Why not go ahead and update the client on each machine? There are no strange effects with the 5.2.3790.1830 client, it only takes less than 30 seconds to install, and it is the matching client for connection to 2003 SP1.

To summarize how to get printing to work:

1.) Make sure the client and server are set to enable printer redirection. This is enabled by default.

2.) Install the 5.2.3790.1830 client on all machines that will be connecting to the server via TS. The install file for this version is located on your 2003 server here:

C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi

3.) Follow the instructions in article 239088 to create print driver mappings

Windows 2000 Terminal Services server logs events 1111, 1105, and 1106

http://support.microsoft.com/kb/239088

As long as the printer you are using is TS compatible, then the three steps above are all that is needed to make it work.

-TP

Rob Oldfield wrote:
This just gets weirder and weirder. I've removed that T640 driver
from the TS box (well, in actual fact, two TS boxes - we're in the
middle of lining up the second one to be able to load balance - but
I'm getting the same thing when connecting to either) and connected
up again. No printer, but no error message about not being able to
find the driver. Another local printer that I have installed is
showing up correctly.

I tried editing the printsubs.inf file anyway, but still no signs of
life being able to autocreate the T640.

The baseball bat solution is looking better and better.

.

Relevant Pages

  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... The SBS server is running SP2. ... However I don't know if the client computers do. ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)