dear aix gurus,
a few of my customer have access via adsl/vpn to my aix 5.2 based apps. for
printing they have ms-lpd services activated on their clients. now each time
they access our aix boxes via adsl/vpn they get a different ip adresse out
from a pool. how can i send print output to them as they always do have
different ip adresses ? i use remote printing on my aix box and i have to
define the host, i want the printjob to be sent.

thanx for a hint
tim

"Tim Moor" <tim.moor@nospam.com> wrote in message
news:d6g4u3$lg$1@atlas.ip-plus.net...
> dear aix gurus,
> a few of my customer have access via adsl/vpn to my aix 5.2 based apps.
> for printing they have ms-lpd services activated on their clients. now
> each time they access our aix boxes via adsl/vpn they get a different ip
> adresse out from a pool. how can i send print output to them as they
> always do have different ip adresses ? i use remote printing on my aix box
> and i have to define the host, i want the printjob to be sent.

Examine your /etc/qonfig file and see if you are using rembak or piorflb for
these queues. For the example below, I've assumed rembak is being used.

Create a script somewhere and give it execute permissions for everyone.

#!/bin/ksh
/usr/lib/lpd/rembak -S $PRINTHOST -P $PRINTQUEUE "$@"
exit $?

Create a new queue that prints to /dev/null:
smit mkpq
print to a file
/dev/null

You now have a new queue that just discards (sends to /dev/null) anything
you queue to it.

Change this queue so that it invokes the above script as a backend. Either
vi /etc/qconfig or:
chquedev -q queuename -d null -a "backend = /path/to/your/script"

Now, in these users' .profile (or elsewhere) you could set the PRINTHOST and
PRINTQUEUE variables:
export PRINTHOST=`who am i |cut -d'(' -f2|sed 's/)//g'`
export PRINTQUEUE=`the queue name on this users PC`

Whenever the user logs in, the PRINTHOST variable is set to their
workstation's current hostname and PRINTQUEUE is set to the name of the
queue on their workstation. This single queue could then be used as a
remote queue to ALL users workstations. When any user submits a print job,
the value of PRINTHOST set in their .profile will be used in the backend
script. Effectively, you've created a single remote queue to any queue on
any host. Each time the user signs in and gets a new dynamic IP, the
PRINTHOST variable will be set correctly.

Best regards,
Paul
http://www.laixsoft.com

paul,
thank you very much for your help. it works great.
tim

<laixsoft@laixsoft.com> schrieb im Newsbeitrag
news:PwPie.3088$cd.1772@trnddc01...
> "Tim Moor" <tim.moor@nospam.com> wrote in message
> news:d6g4u3$lg$1@atlas.ip-plus.net...
> > dear aix gurus,
> > a few of my customer have access via adsl/vpn to my aix 5.2 based apps.
> > for printing they have ms-lpd services activated on their clients. now
> > each time they access our aix boxes via adsl/vpn they get a different ip
> > adresse out from a pool. how can i send print output to them as they
> > always do have different ip adresses ? i use remote printing on my aix
box
> > and i have to define the host, i want the printjob to be sent.
>
> Examine your /etc/qonfig file and see if you are using rembak or piorflb
for
> these queues. For the example below, I've assumed rembak is being used.
>
> Create a script somewhere and give it execute permissions for everyone.
>
> #!/bin/ksh
> /usr/lib/lpd/rembak -S $PRINTHOST -P $PRINTQUEUE "$@"
> exit $?
>
> Create a new queue that prints to /dev/null:
> smit mkpq
> print to a file
> /dev/null
>
> You now have a new queue that just discards (sends to /dev/null) anything
> you queue to it.
>
> Change this queue so that it invokes the above script as a backend.
Either
> vi /etc/qconfig or:
> chquedev -q queuename -d null -a "backend = /path/to/your/script"
>
> Now, in these users' .profile (or elsewhere) you could set the PRINTHOST
and
> PRINTQUEUE variables:
> export PRINTHOST=`who am i |cut -d'(' -f2|sed 's/)//g'`
> export PRINTQUEUE=`the queue name on this users PC`
>
> Whenever the user logs in, the PRINTHOST variable is set to their
> workstation's current hostname and PRINTQUEUE is set to the name of the
> queue on their workstation. This single queue could then be used as a
> remote queue to ALL users workstations. When any user submits a print
job,
> the value of PRINTHOST set in their .profile will be used in the backend
> script. Effectively, you've created a single remote queue to any queue
on
> any host. Each time the user signs in and gets a new dynamic IP, the
> PRINTHOST variable will be set correctly.
>
> Best regards,
> Paul
> http://www.laixsoft.com
>
>
>
>