remote desktop printing error

[Reed Wiedower]

A user at my workplace is connecting via RDC to a workstation in another
site. The local machine has a local printer, which works fine. When the user
prints remotely back to the local printer, the job is queued but the printer
coughs up an error. Restarting the print queue on the remote machine resends
the document and from that point on everything is fine, unless the user logs
out of the session. If they do so, the printer again stops processing jobs.
The error logged each time is this:

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6161
Date: 8/23/2006
Time: 3:27:10 PM
User: VIENNA\jmcsween
Computer: ZVA-JMCSWEEN
Description:
The document outbind://3-0000000049EBEEFE0F575848B8B1F2FF3008FFA00700D29A5CF
owned by jmcsween failed to print on printer Tangerine (from MCSWEENJ-XP).
Data type: NT EMF 1.008. Size of the spool file in bytes: 81404. Number of
bytes printed: 0. Total number of pages in the document: 1. Number of pages
printed: 0. Client machine: \\ZVA-JMCSWEEN. Win32 error code returned by the
print processor: 3 (0x3).

Any thoughts? Restarting the queue each day is getting old.

end of line,

Reed Wiedower

 

[Ada Pan [MSFT]]

Hello Reed,

From the Event ID: 6161, we got the following error code: Win32 error code
returned by the print processor: 5. This means that when we try to print
documents, we are denied due to lack of permissions.

1. Set the printer can be used by Anonymous Logon users. Before Windows XP,
this account is included in Everyone group. In Windows XP or Windows 2003,
it is a separate group. Thus, in Windows XP/2003, we need to enable "Let
everyone permissions apply to anonymous users".

2. Add a NullSessionShare item for that printer.

Below are the detailed instructions to apply the workaround:

Step 1: On the printer which is shared out on the Windows XP client, please
check the user right for that printer queue. It is best to grant everyone
print right.


Step 2: Add user right for Anonymous user.

1. Run gpedit.msc on the Windows XP client with has printer attached.
2. Find this item:

Computer Configuration > Windows Settings > Security Settings > Local
Policies > Security Options

3. Enable "network access: Let everyone permissions apply to anonymous
users"
4. Find "network access: Shares that can be accessed anonymously"
5. Add that printer share name in that list.
6. Reboot the computer.

You may edit the Windows Registry to apply the workaround as well. To do
so, refer to the following MS KB article:

289655 HOW TO: Enable Null Session Shares on a Windows 2000-Based Computer
http://support.microsoft.com/?id=289655

RELATED KNOWLEDGE BASE ARTICLES
=================================
121853 Downlevel Print Jobs Not Redirected Correctly
http://support.microsoft.com/?id=121853

278259 Everyone Group Does Not Include Anonymous Security Identifier
http://support.microsoft.com/?id=278259

Hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Reed Wiedower]

I'll try the fix below, but for the reccord, the Win32 error code returned
by the print processor is 3, not 5. Does that make a difference?

end of line,

Reed Wiedower

 

[Ada Pan [MSFT]]

Hello Reed,

I am sorry for the typo. Please first try the suggestion in my previous
response and let me know the result.

If the suggestions don't help, please help us collect the following
information for further research:

1. What is the exact model of this printer?
2. Does this problem happen for all printers or just the specific printer?

If possible, please install the printer on other clients to see whether
this problem continues; meanwhile, please install another model of printer
on the problematic computer to see whether it works. In this way, we can
isolate whether this issue is related to the Windows client or the printer.

Based on my further research, this problem may occur when some third party
printer monitors conflict with terminal service. I ever dealt a similar
problem before with HP Laserjet 1000 printer which was caused by
hpZJLanguageMonitor. To trouble shoot this problem efficiently, let us
perform the following steps to remove all third party printer monitors,
processors on both the client and the terminal server to test this issue
again:

1. Stop the Printer Spooler service.
2. Start Registry Editor, and locate the Local Port value under the
following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Local
Port

3. Double-click the Driver subkey, and then edit the value. Change the
string value to "Localspl.dll" (without the quotation marks), and then
click OK. If it has been so, please simply skip this step.
4. Check the following registry key for third-party monitors. Remove any
non-default monitors:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors

The default port monitors are:

AppleTalk Printing Devices (When Services for Macintosh is installed)
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
Windows NT Fax Monitor
** LPR Port

5. Check the following registry key for third-party print providers. Remove
any non-default print providers:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers

The default print providers are:

Internet Print Provider
LanMan Print Services

6. Check the following registry key for third-party print processors.
Remove any non-default print providers:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windo
ws NT x86\Print Processors

The default print processor is: ModiPrint and winprint.

7. Change the third-party print processor to WinPrint.
8. Click Start, point to Settings, and then click Control Panel.
9. Double-click Printers and Faxes, right-click the printer, and then click
Properties.
10. On the Advanced tab, click Print Processor.
11. In the Print Processor box, click WinPrint.
12. Click OK two times.
13. Quit Registry Editor.

After you edit the registry, restart the print spooler to test this problem
again.

260142 How to Troubleshoot Windows 2000 Printing Problems
http://support.microsoft.com/?id=260142

Hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.