?
Solved

Problems with Terminal Services easy print (Error 372)

Posted on 2011-03-23
9
Medium Priority
?
3,076 Views
Last Modified: 2012-05-11
Hi Everyone

One of our customers has a remote office with a user connecting to the main office with a simply RDP connection.

The users machine is windows xp Sp3, running the latest RDP 7 client. The local printer of his is a HP 4250 connection to the local lan and installed on the local machine with a standard TCPIP port.
The driver is the HP UPD 5.2 PCL6 (tried the actual 4250 PCL driver as well).

The server is a up to date Server 08 R2 terminal server. Other users in the office can print to printers using local IP ports, but no easy printing seems to be working.

When printing from the server i simply choose the redirected printer, and it spools up on the server and says the job is complete, but it never actually sends anything down the line to the client machine. The event logs show nothing on the pc. The event log on the server (specifically the PrintService log) is throwing an error with event ID 372. I can find nearly nothing online about this error, but please see the attached image for an idea.

Any suggestions to resolve this?

Thanks! Screenshot of erro logged
0
Comment
Question by:SpyderG
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 18

Expert Comment

by:Netflo
ID: 35203421
Hi, has your XP client got .Net 3.5 installed, which is required for print Easy Print to work.

May I suggest you take a look at the following MS article for some useful pointers which will help resolve your issue.

TS: Terminal Server Printing / Easy Print  

Best of luck!
0
 
LVL 11

Expert Comment

by:yelbaglf
ID: 35203443
Have you verified the security permissions on the printers folder?  Make sure the everyone group has permissions to this.

http://support.microsoft.com/kb/962930
0
 

Author Comment

by:SpyderG
ID: 35217436
Hi guys and Thanks

I have checked and the everyone group has write and change permissions to the folder. When applying changes i ensured the print spooler service was stopped. I did get access denied errors to a couple of DLL files. Should i be taking ownership of the folder and trying again?

Also i have checked and the client does have RDP v7 on their machine as well as 3.5 which is required to install it.

The printer is being redirected ok, and it does print just fine locally, i also connected to another customers terminal server from this client and the redirected printer worked just fine. Still stuck on this...

Cheers!
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 18

Expert Comment

by:Netflo
ID: 35219085
Can you please take ownership first then apply the everyone permission to that folder.

I have verified the permissions as described on the MS KB article and on a live Server 2008 R2 server which are correct. Please see the attached screenshot.

I believe we have narrowed the problem down to corrupt files as this folders contents should be empty. After setting the permissions can you MOVE the contents of this folder to a temporary location and test from the client.

Best of luck!
Capture.PNG
0
 

Expert Comment

by:RCoTeam
ID: 35384293
was there a final solution to this, I'm having the same issue?
0
 
LVL 18

Expert Comment

by:Netflo
ID: 35384572
I believe my final comment should have resolved the issue, SpyderG can you confirm?
0
 

Accepted Solution

by:
SpyderG earned 0 total points
ID: 35385469
We found that the PC in question had a Windows.0 directory rather than a Windows directory. Noticed the image file isnt getting tranferred to the printer directory on the client. The customer has opted to move to a new Windows 7 PC rather than reinstall XP. WIll update if this resolves the issue.
0
 

Author Comment

by:SpyderG
ID: 35939773
Sorry for the late reply, installing the new PC resolved the issue, likely was the odd windows path that was causing it.

Thanks everyone!
0
 

Author Closing Comment

by:SpyderG
ID: 35964478
Problem was odd and not related to any other answers provided.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question