Solved

Unix originating lp print jobs, are shown in Windows print queue with owner username + source ip

Posted on 2015-01-05
1
90 Views
Last Modified: 2016-06-12
Some printing jobs get send from our Unix (solaris) print server (through LP) to our Windows 2012 Print server.

When these jobs end up in the Windows print queue, the "owner" is shown with the source ip adress.
Example screenshot

I noticed the change back in September 2014. Suddenly, the ip address was included with the owner field.



Is this a property of Windows LPDSVC or does it come from our Unix configuration? In our Unix print log files, i can't see that Unix sends the ip adress with the jobs. So it seems to me more of a Windows side effect.

My second question is: can the ip adress be stripped off the owner field? This extra notation of ip adress gives problems with our Followme printing environment. Because the username doesn't "match" the LDAP username fields.
0
Comment
Question by:Geert Bettens
1 Comment
 
LVL 61

Accepted Solution

by:
gheist earned 500 total points
ID: 40531396
You can correct your DNS to have proper host names displayed. At least unix lp did so long ago. CUPS shows both hostname and ip
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

My GPO's made for 2008 R2 servers were not allowing me to RDP into a new 2012 server by default.  That’s why I tried to allow RDP via Powershell, because I could log into a remote shell without further configuration. Below I will describe how I wen…
Resolve DNS query failed errors for Exchange
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

911 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now