Hi, im a windows engineer - having an issue with printing from AIX to a windows printer queue - basically what happens is that i restart the enable my print queue on my AIX box and then it starts to send the jobs to my windows printer queue - but after a few short prints it stops and when i do an lpq -P - i see the job is stuck on connect - then it goes to down after it times out. Does anyone have any pointers as where i should start to look - the windows end of things looks fine to me - once the queue times out and i re-enable it - it works for a little time then dies again. Im not an AIX engineer, so im kinda lost
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Printing
- Thread starter TidyTrax
- Start date
R u using IP printing? (direct printing?)
if so can you ping the printer ip address? i beleive it will be reachable if you say that it works for a while!!!
what kind of path does your printer is passing thru? is it a local or network printer?
if so can you ping the printer ip address? i beleive it will be reachable if you say that it works for a while!!!
what kind of path does your printer is passing thru? is it a local or network printer?
- Thread starter
- #4
Yeah using IP printing.
I managed to get it working, every now and again (no pattern) a job just sat on the status connect - so i deleted the job and the next X ran thru before the same thing again. Is it possible to have a mal formed print in Unix????? Or is it just RAW data being piped into the appropriate Windows print queue???
Thanks for the advise
Matt
I managed to get it working, every now and again (no pattern) a job just sat on the status connect - so i deleted the job and the next X ran thru before the same thing again. Is it possible to have a mal formed print in Unix????? Or is it just RAW data being piped into the appropriate Windows print queue???
Thanks for the advise
Matt
hi,
following instr of FAQ, you choose
"standard processing" : this mean that printer characteristic are not managed locally but remotely
(windows side in your case)
choosing "local filtering" you have to define a AIX
printer type, usually I don't use this way, becouse
AIX drivers often do not exists or have to work
a lot to find right parameters using a dummy printer
or similar one to your.
Reading better your 1st post, a doubt came to me:
is Win able to resolve the name of his remote machine(AIX)in IPO address ? use DNS or set in hosts file of Windows (windir\system32\drivers\etc\hosts) the couple
IP.ADD.ERE.SS hostname
bye
following instr of FAQ, you choose
"standard processing" : this mean that printer characteristic are not managed locally but remotely
(windows side in your case)
choosing "local filtering" you have to define a AIX
printer type, usually I don't use this way, becouse
AIX drivers often do not exists or have to work
a lot to find right parameters using a dummy printer
or similar one to your.
Reading better your 1st post, a doubt came to me:
is Win able to resolve the name of his remote machine(AIX)in IPO address ? use DNS or set in hosts file of Windows (windir\system32\drivers\etc\hosts) the couple
IP.ADD.ERE.SS hostname
bye
- Status