[cups.general] Re: [Samba] client ip no longer listed in cups page

[Ryan Suarez]

Hi Helge,

It works great, thanks! I've set 'cups options = 
job-originating-host-name=%m' in smb.conf

cupsd on the printserver still logs the source IP as coming from the 
samba server: "oa-e203-e1 sulimanl 409733 [21/Feb/2005:10:54:13 -0500] 1 
1 - 192.168.76.64"

However, we use pykota for print accounting, which I believe parses the 
IPP headers directly to grab the job originating hostname. It sees the 
netbios name of the client and (unfortunately) the samba server IP: 
['192.168.76.64', 'oa-e203-14'] But this is something we can work with.

And there is no need to run a separate instance of cupsd on the samba 
server.

thanks for your help,
Ryan

Helge Blischke wrote:

Try to add the drective
	cups option = job-originating-host-name=%I
to the globals section in your smb.conf (or %M or %m, wether you want
the DNS name or the netbios name of the client machine instead of it's
IP address).

Helge

PS: let us know if that really works, please.


>Ryan Suarez wrote:
>  
>
>>Ryan Suarez wrote:
>>| Greetings Samba Admins,
>>|
>>| We use samba 3.0.7 with cups 1.1.20 to serve printing to XP clients.
>>|
>>| samba and cups originally sat on the same debian machine.  Due to load
>>| issues, we've moved cups to a separate debian machine and added the
>>| 'cups server =' directive to smb.conf.
>>|
>>| After this, the XP client IP is no longer listed in cups page_log, the
>>| samba server IP is listed instead.  We need this information for print
>>| accounting.
>>|
>>| Any ideas?
>>|
>>|| Not unless you spool through cupsd running on the Samba
>>|| box to the remote cups server.
>>|| cheers, jerry
>>
>>Greetings CUPS Admins,
>>
>>As Jerry from samba suggested, I'm now spooling samba printjobs from
>>cupsd on the samba machine to cupsd on the printserver.
>>
>>Now the XP client source IP is properly recorded in the samba server's
>>page_log.  However, on the actual printserver's page_log the source IP is
>>still being listed coming from samba server's IP.  So this looks like an
>>issue with CUPS.
>>
>>Please help.  I need this information for proper print accounting...
>>
>>Samba server's CUPS config
>>--------------------------
>>Browsing On
>>BrowseAddress 192.168.76.66
>>BrowseDeny All
>>BrowseAllow 192.168.76.66
>>BrowseInterval 30
>>BrowseOrder deny,allow
>>BrowsePoll 192.168.76.66:631
>>
>>Print server's CUPS config
>>--------------------------
>>Browsing On
>>BrowseAddress 192.168.76.67
>>BrowseDeny All
>>BrowseAllow 192.168.76.67
>>BrowseInterval 300
>>BrowseOrder deny,allow
>>
>>regards,
>>Ryan
>>    
>>
>
>  
>