• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Map windows client Printer

I need help with printing to a windows client printer.

I am a Window guy that needs help with UNIX.  Some of my problems I am sure are the fact that I am thinking like MS.  Please excuse my ignorance.

SCO 5.0.5 running propratiary app. I have found sysadmsh and can go to system and hardware and see printers.  I am trying to add a printer to be listed in the app.  All clients were static ip and I changed this a number of months ago but now I see that some of the mapping was done through the static IPs.  I do have the list of old IPs but changing back doesn't work.  I want to delete the old printers listed in the printer manager and create new but they were configured as local not remote.  I tried to configure one as remote and it could not see the printer, then I tried to set it up as local and I just don't know what the settings should be.  All of the printers are connected to /dev/null and I don't know if that is correct or becuase the IPs have changed.
2 Solutions
Not sure if I can understand EXACTLY what you want to do:

You can use "scoadmin" to delete the unwanted printer, or add local/remote printer, add
a local printer is very straight forward, all you need to do is sepecify the printer port and
type, and give a name to the printer.

To add a remote printer, you need to add the printer infor in /etc/hosts file (name and IP),
then use scoadmin to add the remote printer. (for a printer with NIC, that's all you need
to do).

For a printer attached to a Windows 2000/2003/XP PC, you need to make sure sure your
Windows printer server (w2k, Win 2003 or Win XP), has the optional package (Print
Services for UNIX, which comes with LPR for w2k, winXP) installed for handling the printer
jobs from Unix boxes.

also have a look at the answer in the following question:

If you want to print from Windows PC to the SCO box, you also need to install Print,
Services for UNIX, and make sure that the the printer name is EXACT match with
the name defined in the SCO box.

Those printers being connected to /dev/null have been configured as "network attached printers".

Originally in Unix there were two kind of printers: Local Printers, and printers attached to some other unixbox.

When you configured a local printer, it was attached to some port (such as /dev/bpp/0) and had several filters (the filters were the actual printer drivers, converting i.e.plain text ascii to pcl or postscript or whatever)

When you configured a remote printer, basically the file to be printed was sent to the other unixbox without any changes being made to it. This is also the big difference to the windows-printintg system. In the windows-printing system, even when accessing a shared printer on some other machine, the printerdriver is allways on the machine creating the printjob, and the only thing the other machine does is the spooling.

Now networkprinters have become more and more common and of course these networprinters did not have any printerdrivers inside, so we had to find a way of accessing those printers, but still applying the local filter (that is printerdriver). This was done by creating a local printer, printing to /dev/null and applying two filters, first the actual printerdriver and then second a filter called netstandart, that actually has sent the file to the printer.

now how can you configure your printers ? first delete the old ones using lpadmin -x and then create the new ones as descried here:


Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

Tackle projects and never again get stuck behind a technical roadblock.
Join Now