P
Pat Lorch
I've been reading about problems with printing in SP3, and I got a situation
that I haven't seen yet.
I have a Windows 2000 SP3 server running Terminal Services in application
mode. My users are logging in via dumb thin clients. I have an HP 4si and an
HP 6P, both connected via JetDirect TCP/IP.
Anyone with administrative access can print anything. However, normal users
cannot print documents that reside on a network share (to either printer).
The problem seems intermittent, and doesn't always affect all users. I have
not been able to find any rhyme or reason as to what is different about
different users. It also seems to mostly affect Microsoft Word documents and
Adobe PDF files. Microsoft Excel files seem to usually print fine.
What is interesting is that it appears in the queue, and even says
"Printing". I then get a file in the directory that the document exists,
called "hp6p" or "hp4si" (name depending on what printer was attempted). I
have got these files all over my shares.
My workaround thus far has been to have users copy files they wish to print
to a local drive (on the terminal server) and print it from there. That has
worked, but obviously its inefficient for the user.
It's interesting to look at these two system log entries:
This print failed. Attempted to print XYZ.doc located on
\\SERVER\SHARE\Folder.
----
Document 114, Microsoft Word - XYZ.doc owned by jdoe was printed on HP
LaserJet 4Si via port \\SERVER\SHARE\Folder\hp4si. Size in bytes: 0; pages
printed 1
This print was successful. This is the same document, copied to the users
desktop (located locally)
----
Document 115, Microsoft Word - XYZ.doc owned by jdoe was printed on HP
LaserJet 4Si via port hp4si. Size in bytes: 1152388; pages printed: 2
Note that the first one appears to be printing to a file located in the
folder. It is also interesting to note that it shows a byt size of 0.
Any ideas? Thanks.
Patrick Lorch
(e-mail address removed)-inc.com.spam
(Remove no spam for my correct email address)
that I haven't seen yet.
I have a Windows 2000 SP3 server running Terminal Services in application
mode. My users are logging in via dumb thin clients. I have an HP 4si and an
HP 6P, both connected via JetDirect TCP/IP.
Anyone with administrative access can print anything. However, normal users
cannot print documents that reside on a network share (to either printer).
The problem seems intermittent, and doesn't always affect all users. I have
not been able to find any rhyme or reason as to what is different about
different users. It also seems to mostly affect Microsoft Word documents and
Adobe PDF files. Microsoft Excel files seem to usually print fine.
What is interesting is that it appears in the queue, and even says
"Printing". I then get a file in the directory that the document exists,
called "hp6p" or "hp4si" (name depending on what printer was attempted). I
have got these files all over my shares.
My workaround thus far has been to have users copy files they wish to print
to a local drive (on the terminal server) and print it from there. That has
worked, but obviously its inefficient for the user.
It's interesting to look at these two system log entries:
This print failed. Attempted to print XYZ.doc located on
\\SERVER\SHARE\Folder.
----
Document 114, Microsoft Word - XYZ.doc owned by jdoe was printed on HP
LaserJet 4Si via port \\SERVER\SHARE\Folder\hp4si. Size in bytes: 0; pages
printed 1
This print was successful. This is the same document, copied to the users
desktop (located locally)
----
Document 115, Microsoft Word - XYZ.doc owned by jdoe was printed on HP
LaserJet 4Si via port hp4si. Size in bytes: 1152388; pages printed: 2
Note that the first one appears to be printing to a file located in the
folder. It is also interesting to note that it shows a byt size of 0.
Any ideas? Thanks.
Patrick Lorch
(e-mail address removed)-inc.com.spam
(Remove no spam for my correct email address)