Re: [2003] Why can't app print?
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 28 Oct 2006 05:09:38 -0700
Vincent Delporte <justask@xxxxxxxx> wrote on 28 okt 2006 in
microsoft.public.windows.terminal_services:
On Thu, 26 Oct 2006 15:16:23 -0700, "Vera Noest [MVP]"
<vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Vincent Delporte <justask@xxxxxxxx> wrote on 26 okt 2006 in
microsoft.public.windows.terminal_services:
On Thu, 26 Oct 2006 13:11:00 -0700, "Vera Noest [MVP]"
<vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
So these printers are locally installed on the TS?
No. They are network printers (ie. with a NIC), and are
physically located on the user's LAN. I added them to Active
Directory.
But you *installed* the printer on the server, correct?
Let's put it this way: when you log on to the *physical* console
of the server, do you see the printer? And can you print to it?
Or did you just install the driver?
I installed the printer on the server, and I can print from the
server. The client can print to it... from Wordpad, not from our
applicaiton.
There are not redirected session printers?
I don't know what those are. If you mean whether those
printers are physically connect to client hosts through an
LPT1 port, the answer is no.
No, I mean this: I assume that the users have a connection to
this printer on their workstations. That means that - given the
correct version and settings on the rdp client on the
workstation - the printer could be automatically created for
them in the session, without installing the printer at all on
the server. That's called a redirected session printer.
OK, so it's not a redirected session printer. We created it on
the server.
Why did you do that?
Because I'm no expert, and the admin only has average
knowledge of TS.
If users have enabled redirection of loacl printers, they will
get the same printer *twice*, the one which you installed on
the server, and the redirected client session printer, which
is physically the same printer.
OK, it's not the case. They are not local printers, so they
don't show up twice.
But also network printers which are defined on the client can be
automatically redirected in the session.
If it was installed on the server (created IP port, added
driver, and it shows in Active Directory), I guess it's not
automatically created in the session.
If you want to keep your printers installed on the server,
make sure that you disable local printer redirection.
I'll check it out, although it doesn't seem to be a problem.
And check if a user can print to the printer from the console.
Where can I find the console once a user is connected through
Remote Desktop? They can print just fine with Wordpad.
I meant the *physical* console of the server. I'm struggling to
understand how your printer is setup.
OK, by "console", I was thinking of some kind of text-based
application. I can print successfully from the server (test page
sent by right-clicking on the printer > Properties > Print test
page).
And the EventLog should also give you some more info, can you
post the EventIDs? make sure that you have enabled all printer
logging on the server (errors, warnings and informational
events).
I'll check it out, since I don't have admin rights on the
server. I've built a basic EXE with no dependencies other than
the VB5 run-time. I'll ask the user to log on to the W2003
Server through her TS session, download that EXE from our site
(ie. it will be installed with her account as owner), and run
it: If things work ok, it should be able to print to the IP
printer located at her location.
No, please don't! Do not let a user install anything in the
session on the TS. Hopefully, they don't have the right to do
this anyway, and if they van, you have more problems, and it
doesn't tell you anything about your printing problem.
Why is that? We did tell the admin that our app should have
complete control over our directories, so we should be able to
download a file and run it. It if prints ok, it means that it's
not VB in the absolute, but rather some access right somewhere
that isn't right. Am I wrong?
You can't really give an *application* Full Control over a part of
the file system. ACLs on folders and files can contain User
accounts or Groups, not applications.
And normal users should not have the right to install applications
on a Terminal Server, that's the fastest road to an unstable TS.
I suspect that the files that make up our application don't
have the correct user rights, and/or some group policy forbids
it from printing. I'll keep you posted.
There are no policies which forbid applications to use a
printer. Have you checked the permissions on the printer?
OK. If we can't print this morning, I'll get back to the admin,
and ask him to check access rights on that printer, although if
they can print from Wordpad, why couldn't print from our
application?
Could be a lot of things. Maybe your application creates a
temporary file somewhere during printing, and the user doesn't have
the right to create that file?
Check to see if the print job shows up in the spooler on the TS.
You can also download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator on the
console of the server (when no user is connected), start a TS
session as a normal user and try to print from the application.
FileMon and RegMon will show you all "access denied" errors that
occur, so that you can give your users the necessary permissions on
a file-to file or Registry subkey basis.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
.
- Follow-Ups:
- Re: [2003] Why can't app print?
- From: Vincent Delporte
- Re: [2003] Why can't app print?
- References:
- [2003] Why can't app print?
- From: Vincent Delporte
- Re: [2003] Why can't app print?
- From: Vera Noest [MVP]
- Re: [2003] Why can't app print?
- From: Vincent Delporte
- Re: [2003] Why can't app print?
- From: Vera Noest [MVP]
- Re: [2003] Why can't app print?
- From: Vincent Delporte
- Re: [2003] Why can't app print?
- From: Vera Noest [MVP]
- Re: [2003] Why can't app print?
- From: Vincent Delporte
- [2003] Why can't app print?
- Prev by Date: Re: LPT1 printers problems with firewall
- Next by Date: Access Denied registry errors-not consistent for users in same group
- Previous by thread: Re: [2003] Why can't app print?
- Next by thread: Re: [2003] Why can't app print?
- Index(es):
Relevant Pages
|
