Re: Printer autocreation failing

Nope. Afraid not. All three of the log events are enabled.

And it actually got a bit stranger again - but this time in a good way. I
had a workaround in mind so that I could get my users working correctly,
which was basically - via login script - to do the equivalent of start, run,
\\printserver, and double clicking on the printer and, after my previous
post, I put that in place (with the obvious downside that that will
reinstall the driver onto the TS box).

Having done that, not only did the 640 start autocreating correctly, but it
did so with the additional trays enabled (in fact, with trays 1-5 enabled
which is, I'm thinking, showing that it's picking up the redirection of the
driver to the LJ4) and functional.

Obviously, if it's now going to work and remain stable, then I'll be happy,
but it would certainly be nice to know exactly what the problem has been.

(Note... just to repeat the earlier question on whether the matrix page on
printingsupport.com is updated...)


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9895D77B242B1veranoesthemutforsse@xxxxxxxxxxxxxxxx
Maybe you have disabled warnings and informational messages on the
server? Check in Printers and Faxes - File - Server properties -
Advanced.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Rob Oldfield" <blah@xxxxxxxx> wrote on 10 dec 2006 in
microsoft.public.windows.terminal_services:

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.


"Rob Oldfield" <blah@xxxxxxxx> wrote in message
news:%23nnV1wFHHHA.536@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the suggestion. Having run out of other things to
try, I'll give it a go.

I do find it very strange that, given that the 632 works at one
of my sites, that I can't get that to work on a second site.
Looking at the driver matrix at
http://www.printingsupport.com/mappings/lexmark.htm it does
appear that the LJ4 is going to be the best one to try first.
That list doesn't look to be all that up to date, do you know
if it's still being updated? It would be a shame if it wasn't
as it's a very useful resource - and I'd be happy to help out
by keeping it current.

The fallback option also looks interesting, particularly for
those pesky home based users with those nasty
printer/fax/photocopier/toaster things that they all seem to
have. Strange that MS haven't publicised it a bit more.


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns9894D247735F8veranoesthemutforsse@xxxxxxxxxxxxxxxx
I'm afraid that these are all rather typical examples of the
irratic behaviour of a TS incompatible printer driver.

I would uninstall these drivers completely and instead map the
printer to a native driver, like the HP LaserJet 4.
That should at least give you a consistent redirected session
printer. Detailed instructions here:

239088 - Windows 2000 Terminal Services Server Logs Events
1111, 1105, and 1106
http://support.microsoft.com/?kbid=239088

Instead of mapping the driver manually, you can also configure
a fallback printer driver (after uninstalling the Lexmark
driver):

http://www.printingsupport.com/mambo/index.php?
option=com_content&task=view&id=56&Itemid=49

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Rob Oldfield" <blah@xxxxxxxx> wrote on 09 dec 2006 in
microsoft.public.windows.terminal_services:

Oh dear. Things are getting worse. I originally installed
the PCL driver for the 640 but then noticed that the 632 that
works at our other site was using the PS version. So I tried
setting the 640 up as PS as well. Since then (not sure if
it's actually just random and I got lucky the first few
times) both the PCL and PS versions have been behaving
randomly. Sometimes they create and sometimes they don't.
Trying to access the printer properties, or page setup in
Word, causes the session to hang.

Tried installing that printer tray hotfix, and realised that
I couldn't as the print server is 2000 server (as is the one
that works). Also tried updating the RDP client to the
latest version (as per TP's suggestion) on one of my XP
clients, and that also makes no difference.

Still no errors in event logs anywhere.

Any ideas (other than the obvious one of taking a baseball
bat to the hardware)?


"Rob Oldfield" <blah@xxxxxxxx> wrote in message
news:e5zOelgGHHA.2632@xxxxxxxxxxxxxxxxxxxxxxx
Sadly, half of my TS clients are still using Win2K, so
version 6 of the client isn't an option. I have actually
got one step further forward though... by going to the TS
box and installing the print queue from the remote server
(i.e. start, run, \\remoteservername, and double clicking on
the printer) I now have the printers autocreating.

BUT, they're doing it without adding in additional trays.
I've checked the printer on the server, and that has the
trays set up, and the local version of the printer also has
them. They just fail to show up in the autocreated version.

I'm going to try installing the patch from
http://support.microsoft.com/?kbid=870981 tonight (thanks
to Vera's site for finding that one), and see how that goes.

For ref, this behavious is consistent on both the T640 and
the T632, and no difference is made if I upgrade the client
to 5.2.3790.1830

"TP" <tperson.knowspamn@xxxxxxxxxxxxxxx> wrote in message
news:u2PFkIeGHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
That is not the latest.

You can use version 5.2.3790.1830 to enable redirection of
printers attached to standard tcp/ip ports. The install
file for this version is located on your 2003 server here:

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

Alternatively, you can download the newest available
client, version 6.0.6000.16386 here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=26f
11f 0c-0d18-4306-abcf-d4f18c8f5df9

The primary benefit of using the version 6 client is to
allow you to use the new features available when connecting
to Vista and Windows Server code-named Longhorn. It works
fine when connecting to 2003 as well, however, the initial
connection takes longer and the credential-saving
capability is different than 5.x client versions.

-TP
Rob Oldfield wrote:
TS box is running 2003 server, SP1. RDP client is
5.1.2600.2180 which is, as far as I can see, the latest
version. Client is set to automatically connect local
printers, all printers are set up with a standard tcp/ip
port.


.

Relevant Pages

  • Re: IPSEC question
    ... The important issue is to get the server working properly first without ... I hit the SBS weblog and tried their stuff. ... Microsoft network client: Digitally sign communications: ... 898060 Installing security update MS05-019 or Windows Server 2003 Service ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 - SBS 2008 migration issues
    ... DHCP cannot work properly with the hyper-v role, and probably DNS, neither will the configuration wizards. ... clients losing the ability to use it after removing trend client, reseting winsock / removing network components / reinstalling teh client don't bring it back. ... When I add the 32 bit driver to the printer it simply tells me it's not a suitable driver, and to try adding the driver from a 32 bit client. ... If I install hyperV on the SBS 2008 will it run a win2k3 server? ...
    (microsoft.public.windows.server.sbs)
  • Re: Printer autocreation failing
    ... behaviour of a TS incompatible printer driver. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Tried installing that printer tray hotfix, ... Also tried updating the RDP client to the latest ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... redirection of the driver to the LJ4) and functional. ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: SQL Native Client vs SQL Server Driver
    ... On the blog for the SQL Native Client, you will find a lot of useful ... However, its biggest advantage is that unlike the MDAC, not only that you ... They won't be happy if you break something on their machine by installing ... a new application should always use the lasted driver if it can do ...
    (microsoft.public.sqlserver.odbc)
Loading