Re: Terminal Server Session ID mismatch with Client Printers
- From: "Alex Balcanquall - MS" <alexbal@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 29 Jul 2006 00:42:38 -0700
I have never heard of this issue. I will do some more research, in the meantime I would suggest that you log a call with Microsoft Product Support Services (PSS). Please ensure you have the latest service pack installed.
You might want to check out common KB articles on printing and also check your event log for errors:
http://support.microsoft.com/search/default.aspx?query=terminal+services+printer+2003&catalog=LCID%3D1033&spid=&qryWt=&mode=r&cus=False
--
Alex Balcanquall
Product Manager
Terminal Services Team
Microsoft
-This e-mail is provided "AS IS" with no warranties, and confers no rights-
"Andy Lo" <AndyLo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2C8EE01A-8A6E-46EB-8CAA-E66D66C3C19F@xxxxxxxxxxxxxxxx
Hello,
We are currently using Windows 2003 Terminal Server and have been
experiencing a random problem recently and would appreciate if anyone can
shed some light for us please?
The issue that we are having is that occassionaly, some users will report to
us that they cannot print to their network printers and the best reason that
we can gather so far was that the their network printers were being assigned
with a different terminal session id to what I can see under Terminal Server
Manager. And so, nothing actually prints out when no matter how many times
they try to print and even the network speed wasn't any issue as well.
The only workaround that we have at the moment is to either restart the
server OR ask the user to logoff/logon again.
Has anybody experienced this problem before? And if so, how did you resolve
it please?
Thanks
Andy
.
- Prev by Date: Re: HP K550 Printer
- Next by Date: Re: Controlling logoff behavior
- Previous by thread: Re: HP K550 Printer
- Next by thread: Re: Controlling logoff behavior
- Index(es):
Relevant Pages
|
