SCO OpenServer 5.0.7 Remote Printing

[CarrahaG]

Hello

We recently installed SCO OpenServer 5.0.7. However, we have no access to remote network printers (printers connected to print servers).

When we run "mkev lp", go to the "System" tab and then select "Print Services", we see two choices:
"Local Print Service Enabled"
"(Remote UNIX Print Service Enabled)"
However, we can NOT enable the Remote UNIX print service. When we use the TAB key to navigate to that option, it simply skips over it. We also notice that the remote printing option is in parenthesis.


If we go under the "Printer" Tab, and select "Add Remote" and then try to select "UNIX", nothing happens.

When we run the command "mkdev rlp", we get the error:
"mkdev: /usr/lib/mkdev/rlp not found".

In seems as if remote printing is not installed. How can we install this?

Regards,
Georges

 

[motoslide]

Have a look here:

http://www.sco.com/ta/125723

It says at the end where you can find the 'rlp' that was taken away from /usr/lib/mkdev. But, it also appears that they recommend you remove CUPS first.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[CarrahaG]

Hello

Thanks alot. This helped. I got further now but still not succesful in installing the remote printer. I removed a previously defined remote printer but when I run the command "lpstat -t", I get the following error message:
"UX:lpstat: ERROR: Error reading printer information for "printer name" (No such file or directory).".

I believe that I manually removed all orphaned directories that had the same name as the printer under the "/usr/spool/lp" directory. What else could be causing that error message refering to the printer name?


Regards,
Georges

 

[PHV]

Edit the /var/spool/lp/system/pstatus file.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[CarrahaG]

Hello

It helped. I was able to set up the remote printer but now the job just remains in the queue and nothing physically print.

The printer is an Okidata ML320 connected to a DL-Link print server. The /etc/hosts files has the entry as follows:

192.168.10.163 speedy speedy.jolley.local

The host is "speedy" and the printer name is "speedyptr". We used "mkdev rlp" to install the printer and when we run the "lpstat -t" command, we get the output below:

speedyptr accepting requests since "...."
speedyptr:
queuing is enabled
Printer Status: On line

When a job is sent to the printer, we then run the "lpstat -t" command again. We get the following now:

speedyptr accepting requests since "...."
printer speedyptr waiting for auto-retry. available.
stopped with printer fault.

The job remains in the queue. When we try to cancel the job we get the message:

UX:cancel: WARNING: Request "speedyptr-1140" does not exist.

The strange thing is that the same printer was working on an older server with the same SCO OS 5.0.7. We only migrated the OS to a new server.

Any ideas?

 

[motoslide]

Please post the /etc/printcap entry which was created (or updated) when you created the printer.
Then, look on D-Link's website for valid printer QUEUE names used for lpd.
Once you find the correct name, replace this:
rp=speedyptr
with
rp={valid queue name}

If the D-Link supports port-9100 printing, I'd switch to HPNP or NETCAT in a heartbeat. That's just a personal preference, not necessarily a recommendation.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[PHV]

I'd switch to HPNP or NETCAT
I personnally use netcat for all port9100 printers, even genuine HP.

 

[CarrahaG]

Hello

The princap entry is as follows:
speedyptr:\
:lp=:rm=speedy:rp=speedyptr:sd=/usr/spool/lpd/speedy
ptr:mx#0:

I checked the documenation in the D-Link manual and it states that when running the mkdev rlp command, you need to supply the following:


1. For the printer name enter an alias for the printer on the local machine and press Enter. This name should be the same as the destination port name. This is "speedyptr".

2. For the remote host that printer is attached to, enter the address of the D-Link print server. You can use the name you added to /etc/hosts. We used the name "speedy" in the /etc/hosts files.

We still have the old server up in which the printing was working perfectly. The printcap entry is exactly the same as above.

Regards,
Georges

 

[motoslide]

The double-posting of this thread is a bit problematic.

I wasn't able to determine if the DLINK supports port9100 printing, but you can test this without changing anything.

Just run this command:
# telnet speedy 9100
This line that I'm typing should go to the printer
Cntl-]

If the device listens on port 9100, it should allow you to type and whatever you type will be printed. To end the connection, hit "Control" and "]" at the same time.

If that works, get "netcat" and leave the lpr/lpd stuff in the dust.
If that isn't an option, can you verify that the SCO system can communicate with ANY printer using lpr/lpd?
What did you have to do to get the "mkdev rlp" operational? There are 2 copies of the lp binaries on SCO5, it's possible your's are confused.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[CarrahaG]

Hello

Sorry about the double posting. We initially created this thread because we had a problem with getting the remote prinitng activated. After, we got it activated, we decided to open another thread since we were encountering a new problem. In the end, both threads were kept active.

About your question. I checked the manual and could not find anything about support for port 9100 printing. In anycase, I ran the command:

# telnet speedy 9100

After pressing enter. I got the result "Connected to speedy.". At the blank line following that result, I typed a small sentence. I then pressed "^]". I then got the "telnet>" prompt on a new line. I then entered "quit" and pressed the RETURN key and got "Connection closed." and the shell prompt again.

Nothing printed.

There are some printers that are connected to the server with serial ports and those printers print fine with the lp command. However, none of the printers connected with print server are working.

I have never used netcat before and I believe that we may have a problem using netcat because of the application we are using and how it is configured to print to printer queues. However, all tests I am doign now is outside of the application.

I got the mkdev operational after I implemented your advice above using the technical article

http://www.sco.com/ta/125723.

Basically I had installed SCO Maintenance pack 1 and Maintenance Pack 5. After I removed the CUPs from Maintenace Pack 5, I was able to use "mkdev rlp". I checked the Maintenance Pack 1 and saw no CUPs to remove.

How can I check about the lp binaries that you mentioned?

Regards,
Georges

 

[CarrahaG]

Hi

I found out the following and I am not sure if this helps. On the old server, there is a device called speedyptr. I also found a script called setspeedyptr that was created by someone that has the following in it:

rm -f /dev/speedyptr
mknod /dev/speedyptr p
chmod 666 /dev/speedyptr
while true
do
cat /dev/speedyptr | lpr -d speedyptr
done

In the /etc/rc.d/8/userdef file there is a line "setspeedyptr &".

I ran the script on the new server and it creates the device. However, still can not print. The job still gets stuck in the queue.

Regards,
Georges

 

[southbeach]

Have you checked permissions for /usr/spool/lp/admins/lp/interfaces/*.orig ?? (if I am not mistaken) The drivers here should have chmod 755 - When I encounter this kind of problem, this is usually the root cause.

That being said, I would 'netcat' as previously suggested. It works great and it integrates just fine with your printer stack/queue.

I have the binaries floating around some where, let me know if you need it.



--
SouthBeach

http://www.fpgroups.com

The good thing about not knowing is the opportunity to learn - Yours truly, 2008.