From: underh20 on 29 Jan 2010 17:30 Hello all, Per John's suggestion below, I did issue the command to configure our global zone "atlantis" as the print server and configure our local zone "zoneA" as the print client. Also i issued the command below to send the postscript file for printing at printer1 : zoneA# lpadmin -p printer1 -s atlantis zoneA# lp -d printer1 /usr/sfw/share/ghostscript/8.15/examples/ alphabet.ps However, the print job is still not coming out "printer1-718" and the print queue remains. Below are the latest output at the print client "zoneA" : # lpstat -t scheduler is running no system default destination system for printer1: atlantis (as lpd://atlantis/printers/printer1#Solaris) printer1 accepting requests since January 29, 2010 5:14:48 PM EST printer printer1 disabled since January 29, 2010 5:14:48 PM EST. available. printer1: processing printer1-718 root 184 Jan 29 17:14 Anyone can shed some light as why "printer1-718" still sitting in the queue and not going away ? Thanks, Bill On Jan 29, 1:10 pm, groen...(a)cse.psu.edu (John D Groenveld) wrote: > [followup's set to comp.unix.solaris] > > In article <42502782-fc6e-49ec-a1b2-9d88228dc...(a)f17g2000prh.googlegroups..com>, > > underh20 <underh20.scubadiv...(a)gmail.com> wrote: > >Our server "atlantis" has one local zone "zoneA" setup. HP jetadmin > >is installed and has been running at the global zone and local zone, > >namely "atlantis" and "zoneA". > > Use your global zone as the print server and configure your > local zones to be your print clients: > > zoneA# lpadmin -p printer1 -s atlantis > zoneA# lp -d printer1 /usr/sfw/share/ghostscript/8.15/examples/alphabet.ps > > John > groenv...(a)acm.org
From: John D Groenveld on 29 Jan 2010 21:37 In article <f9597837-cafe-4680-90f5-8c6505565726(a)a5g2000prg.googlegroups.com>, underh20 <underh20.scubadiving(a)gmail.com> wrote: >zoneA# lpadmin -p printer1 -s atlantis >zoneA# lp -d printer1 /usr/sfw/share/ghostscript/8.15/examples/ >alphabet.ps > >However, the print job is still not coming out "printer1-718" and the >print queue remains. Below are the latest output at the print client >"zoneA" : Can you reach atlantis 515/tcp from zoneA or another host on your network? John groenveld(a)acm.org
From: underh20 on 1 Feb 2010 20:13 Hi John, Yes, I can reach atlantis via port # 515. Any idea how we can trouble- shoot further on this. Below is the output. Thanks, Bill zoneA# telnet atlantis 515 trying 172.50.224.63 Connected to Escape character is '^]'. On Jan 29, 6:37 pm, groen...(a)cse.psu.edu (John D Groenveld) wrote: > In article <f9597837-cafe-4680-90f5-8c6505565...(a)a5g2000prg.googlegroups.com>, > > underh20 <underh20.scubadiv...(a)gmail.com> wrote: > >zoneA# lpadmin -p printer1 -s atlantis > >zoneA# lp -d printer1 /usr/sfw/share/ghostscript/8.15/examples/ > >alphabet.ps > > >However, the print job is still not coming out "printer1-718" and the > >print queue remains. Below are the latest output at the print client > >"zoneA" : > > Can you reach atlantis 515/tcp from zoneA or another host on > your network? > > John > groenv...(a)acm.org
From: John D Groenveld on 1 Feb 2010 20:32 In article <522fd10d-3951-473b-b355-a723043c0672(a)l12g2000prg.googlegroups.com>, underh20 <underh20.scubadiving(a)gmail.com> wrote: >Yes, I can reach atlantis via port # 515. Any idea how we can trouble- >shoot further on What's the make and model of your printer? John groenveld(a)acm.org
From: underh20 on 2 Feb 2010 14:31 John, It's a HP LaserJet 8150DN printer. Thanks, Bill On Feb 1, 5:32 pm, groen...(a)cse.psu.edu (John D Groenveld) wrote: > In article <522fd10d-3951-473b-b355-a723043c0...(a)l12g2000prg.googlegroups..com>, > > underh20 <underh20.scubadiv...(a)gmail.com> wrote: > >Yes, I can reach atlantis via port # 515. Any idea how we can trouble- > >shoot further on > > What's the make and model of your printer? > > John > groenv...(a)acm.org
|
Next
|
Last
Pages: 1 2 Prev: Lost the key to a Sun 420R Next: Help! Old passwords still work in Solaris 10 |