This isn't of any help, the printers are attached to a remote server, the
impersonated account can't access remote resources unless kerberos
delegation is configured correctly and all clients are authenticated using
kerberos.
As I said in my other reply, printing is not supported and in general
doesn't work from services (windows and web).
Willy.
"Michael Nemtsev" <Mi************@discussions.microsoft.com> wrote in
message news:F2**********************************@microsof t.com...
| Add impersonate=true to web.config
|
| "Paul Aspinall" wrote:
|
| > Hi
| > I am trying to print, server side, from my web application.
| >
| > I'm getting problems, as my ASPNET account is a local account, and is
not
| > trusted on the domain to print to printers (ie. does not belong to
'Users'
| > group)
| >
| > What is the best way round this??
| >
| > I've asked the security guys to specifically add the account with
| > permissions to the printer (ie. specifically add \\webhost\ASPNET ) but
they
| > say that it won't work, because \\webhost is not trusted in the domain).
| >
| > Can anyone help??
| >
| > What is the best way to let ASPNET run under another account? (ie other
than
| > the local ASPNET)
| >
| > Surely the network guys can add the local machine account
\\webhost\ASPNET
| > to have permissions to print on the printer?
|
| --
| WBR,
| Michael Nemtsev :: blog:
http://spaces.msn.com/laflour
|
| "At times one remains faithful to a cause only because its opponents do
not
| cease to be insipid." (c) Friedrich Nietzsche
|