Xref: utzoo comp.unix.sysv386:8229 biz.sco.general:64
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!sco!paulz
From: paulz@sco.COM (W. Paul Zola)
Newsgroups: comp.unix.sysv386,biz.sco.general
Subject: Re: Remote Printing Over SCO TCP/IP?
Message-ID: <17043@scorn.sco.COM>
Date: Mon, 20 May 91 18:09:35 GMT
References: <1991May19.204503.1754@rfengr.com>
Sender: news@sco.COM
Organization: The Santa Cruz Operation, Inc.
Lines: 157


In article <1991May19.204503.1754@rfengr.com> rfarris@rfengr.com (Rick Farris) writes:
}I'm trying to figure out how to automatically print on a
}printer attached to another host.
}

[details deleted]

}
}--
}Rick Farris  RF Engineering POB M Del Mar, CA 92014  voice (619) 259-6793
}rfarris@rfengr.com     ...!ucsd!serene!rfarris      serenity bbs 259-7757


The following article from the SCO Information Tools database should help 
with your problem.   I'm posting because I think this may be of general
interest.

################## cut here ################ cut here ##################

How do I set up remote printing with SCO TCP/IP?

KEYWORDS: printer remote lpinit mkdev rcmd 

RELEASE:  SCO TCP/IP Generic

PROBLEM:  How do I set up remote printing with SCO TCP/IP.

SOLUTION: The following steps outline how to set up remote printing
	  with SCO TCP/IP.  
	  
	  (1) If you are running over SCO TCP/IP, the utility remote
	  command (rcmd) can provide access to all remote printers with 
	  an identical User Interface, "lpr."  There are a few steps you 
	  need to do to set this up:
	  
	  	(i) Get rcmd working. The machines need to be set up as 
		trusted hosts.  The easiest way to do this is to add the 
		remote machines to the "/etc/hosts.equiv" file.  Then you 
		can test the rcmd command in the following manner:
	  	 
	  	   cat /etc/motd | rcmd <remote_host> lp -d<dest_printer> 

	  	where anything enclosed in braces <> is replaced with the
	  	correct host or remote printer destination. This will print
		the local /etc/motd on the remote printer.
	  
	  	If you are testing rcmd as root, you must also have an entry
		in /.rhosts on the remote machine that looks like:
	  
	  	   <local_host> root
	  
	  	See rcmd(C) in the SCO TCP/IP documentation for more details.
	  
	  
  	(2) Follow the guidelines below depending on whether you have an
	    SCO XENIX System V Operating System or an SCO UNIX System V/386
	    Release 3.2 Operating System.

	    SCO XENIX 386 Operating System:

		(i) You will need to run "lpinit" on the local machine
		(the one that does not have the printer(s)). Choose Add
		(Option 1) from the lpinit main menu.  Then, from the Add
		menu, choose Remote Printer (Option 3).  Do not select SCO 
		XENIX-NET, as this is dependent upon xnlpc.  Rather, choose
		UUCP and answer the questions appropriately.  SCO recommends
		using the same printer name on this machine that is used on
		the remote machine so users do not have to send printouts to
		different destinations when they are on different machines.
	  
	  	(ii) Edit the /usr/spool/lp/remote file and change the entry 
		that lpinit added.  Initially it should look like:
	  
	  	   foo_printer:  uux - <remote_host>!lp -dfoo_printer
	  	   (where "foo_printer" would be the name of your printer)
	  
	  	After editing the file, it should look like:
	  
	  	   foo_printer:  rcmd remote_host lp -dfoo_printer
	  	   (where "foo_printer" would be the name of your printer)
	  
	  	(iii) Create "/usr/spool/lp/.rhosts on the destination machine
	  	(where the printer is) with an entry as follows:
	  
	  	   <local_host> root
	  
	  
	    SCO UNIX System V/386 Operating System:

		(i) You will need to run "sysadmsh", on the local machine
		(the one that does not have the printer(s)). Choose the
		following options:

		   Printers
		   Configure
		   Add

		You will then be presented with a menu as follows:

		   Printer name   <enter the printer name>

		SCO recommends using the same printer name on this machine 
		that is used on the remote machine so users do not have to 
		send printouts to different destinations when they are on 
		different machines.

		Comment       <enter a comment such as remote printer on max>

		Class Name    <press return if you do not have classes>

		Use printer interface <select Existing>

		Name of interface <enter "network," as this is the name of the
				   interface script>
		
		Connection   <select Direct>

		Device name  <enter "/dev/null">

		Dial-up information <press return>

		Device       <select Hardwired>

		Require banner  <select yes or no>

	  	(ii) Create the /usr/spool/lp/remote file and add the 
		following information:

	  	   foo_printer:  rcmd remote_host lp -dfoo_printer
	  	   (where "foo_printer" would be the name of your printer)
	  
		You will need to make an entry for each printer you add.
		After you have finished editing /usr/spool/lp/remote
		execute the following commands:

		   chown lp remote
		   chgrp lp remote
		   chmod 755 remote

	  	(iii) Create "/usr/spool/lp/.rhosts on the destination 
		machine (where the printer is) with an entry as follows:
	  
	  	   <local_host> root

		Then change the permissions and ownership to be the same
		as the remote file.

################## cut here ################ cut here ##################

I hope this helps you with your problem.

-
Paul Zola			Support Technical Lead, Operating System
				paulz@sco.COM 
Gotta tend the earth if you want a rose.  - Emily Saliers
    DISCLAIMER: I speak for myself, and not for SCO.