jobowner and hostip

[Stanley]

what can be the differnce betwen ms and cups, because this happens only when the jobs came from cups. From ms to ms, i don't see added ip's to the jobs!

thanks for your help.


> OK, Windows must be adding the hostip - the LPD backend DOES NOT change =
> the username passed in the job.
>
> On Feb 10, 2010, at 10:41 PM, Stanley wrote:
>
> > lpstat -v give me
> >=20
> > For Printerdevice S199
> > --
> > device s199: lpd://pirnt-server-ms/s199
> > --
> >=20
> >> What are the device URIs for the queues?
> >>=20
> >> ("lpstat -v" will tell you)
> >>=20
> >> On Feb 10, 2010, at 12:54 AM, Stanley wrote:
> >>=20
> >>> hi michael,
> >>> =3D20
> >>> the printers are all PCL and configured as RAW printers. everthing =3D=
>
> >> works fine, when i print directly to the printer or thru the ms =3D
> >> printserver. the jobs are are queued with the originating ip, this =
> seems =3D
> >> to be, that these come from cups, the are no banners or something =
> like =3D
> >> that enabled.
> >>> =3D20
> >>> that is the problem for the accounting tool. which can't map correct =
> =3D
> >> the users, caused by the origination ip -> username(hostip).
> >>> =3D20
> >>> thank you for your support.
> >>> =3D20
> >>> --
> >>> =3D20
> >>>> What protocol are you using to send jobs from the CUPS system to =
> =3D3D
> >>>> Windows?
> >>>> =3D20
> >>>> On Feb 8, 2010, at 10:48 PM, Stanley wrote:
> >>>> =3D20
> >>>>> Hi,
> >>>>> =3D3D20
> >>>>> i've tested again and again, this occurs only, when i print thru =3D=
>
> >> cups =3D3D
> >>>> to the printsever(which is a windows) - when i print from windows =
> to =3D
> >> =3D3D
> >>>> windows, the qeue shows only jobowner! do you have any idea?
> >>>>> =3D3D20
> >>>>> thanks for your help
> >>>>> =3D3D20
> >>>>> =3D3D20
> >>>>>> OK, CUPS doesn't do this - you must be using other software that =
> is =3D
> >> =3D3D3D=3D3D
> >>>> =3D20
> >>>>>> adding the IP, or MS is adding it when they receive the job.
> >>>>>> =3D3D20
> >>>>>> On Feb 8, 2010, at 2:54 AM, Stanley wrote:
> >>>>>> =3D3D20
> >>>>>>> Hi Michael,
> >>>>>>> =3D3D3D20
> >>>>>>> thank you for your fast response and help. i'm sorry, i've =
> thougt, =3D
> >> =3D3D3D=3D3D
> >>>> =3D20
> >>>>>> that i've explained my problem correct, but now i see, i've got =
> to =3D
> >> =3D3D3D
> >>>>>> explain it better :-)
> >>>>>>> =3D3D3D20
> >>>>>>> we got a ms printserver, that is responsible for printing & =
> =3D3D3D
> >>>>>> accounting, but the dammed server can't map the user correctly to =
> =3D
> >> the =3D3D
> >>>> =3D3D3D
> >>>>>> accounts.
> >>>>>>> =3D3D3D20
> >>>>>>> the problem is, that the printjobs got a userid AND a hostip =
> from =3D
> >> =3D3D
> >>>> the =3D3D3D
> >>>>>> cups and cups forwarded this in the the ms server -> like =3D3D
> >>>> "jobowner(ip)"
> >>>>>>> =3D3D3D20
> >>>>>>> for a correct mapping, i need only the jobowner! without any ip, =
> =3D3D=3D
> >>=20
> >>>> that =3D3D3D
> >>>>>> is my problem.
> >>>>>>> =3D3D3D20
> >>>>>>> i hope, i've now explained it better ;-)
> >>>>>>> =3D3D3D20
> >>>>>>> best regards
> >>>>>>> =3D3D3D20
> >>>>>>> stanley
> >>>>>>> =3D3D3D20
> >>>>>>>> The current web interface shows the job-originating-user-name =
> for =3D
> >> =3D3D3D=3D3D
> >>>> =3D20
> >>>>>> each =3D3D3D3D
> >>>>>>>> job.  If you want to *add* the originating ip/hostname, edit =
> the =3D
> >> =3D3D
> >>>> =3D3D3D3D
> >>>>>>>> jobs.tmpl file in /usr/share/cups/templates/de and add =3D3D3D3D
> >>>>>>>> "({job_originating_host_name})" after the =3D3D3D
> >>>>>> "{job_originating_user_name}".
> >>>>>>>> =3D3D3D20
> >>>>>>>> On Feb 5, 2010, at 6:08 AM, Stanley wrote:
> >>>>>>>> =3D3D3D20
> >>>>>>>>> Hi,
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> is it possible, to only show the owner of the job in cups, =3D
> >> without =3D3D
> >>>> =3D3D3D
> >>>>>> the =3D3D3D3D
> >>>>>>>> originating ip/hostname. When i start a printjob, so i can see =
> in =3D
> >> =3D3D
> >>>> the =3D3D3D
> >>>>>> =3D3D3D3D
> >>>>>>>> printer qeue the owner of job and the originating hostip -> =
> =3D3D3D3D=3D
> >>=20
> >>>>>>>> owner(hostip).
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> thanks.
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> stanley
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> =3D3D3D3D20
> >>>>>>>>> _______________________________________________
> >>>>>>>>> cups mailing list
> >>>>>>>>> cups at easysw.com
> >>>>>>>>> http://lists.easysw.com/mailman/listinfo/cups
> >>>>>>>> =3D3D3D20
> >>>>>>>> ___________________________________________________
> >>>>>>>> Michael Sweet, Senior Printing System Engineer
> >>>>>>>> =3D3D3D20
> >>>>>>>> =3D3D3D20
> >>>>>>>> =3D3D3D20
> >>>>>>> =3D3D3D20
> >>>>>>> _______________________________________________
> >>>>>>> cups mailing list
> >>>>>>> cups at easysw.com
> >>>>>>> http://lists.easysw.com/mailman/listinfo/cups
> >>>>>> =3D3D20
> >>>>>> ___________________________________________________
> >>>>>> Michael Sweet, Senior Printing System Engineer
> >>>>>> =3D3D20
> >>>>>> =3D3D20
> >>>>>> =3D3D20
> >>>>> =3D3D20
> >>>>> _______________________________________________
> >>>>> cups mailing list
> >>>>> cups at easysw.com
> >>>>> http://lists.easysw.com/mailman/listinfo/cups
> >>>> =3D20
> >>>> ___________________________________________________
> >>>> Michael Sweet, Senior Printing System Engineer
> >>>> =3D20
> >>>> =3D20
> >>>> =3D20
> >>> =3D20
> >>> _______________________________________________
> >>> cups mailing list
> >>> cups at easysw.com
> >>> http://lists.easysw.com/mailman/listinfo/cups
> >>=20
> >> ___________________________________________________
> >> Michael Sweet, Senior Printing System Engineer
> >>=20
> >>=20
> >>=20
> >=20
> > _______________________________________________
> > cups mailing list
> > cups at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups
>
> ___________________________________________________
> Michael Sweet, Senior Printing System Engineer
>
>
>