🚀 go-pugleaf

In article <3vfcsl$bt4@ixnews2.ix.netcom.com>,
rgregory@ix.netcom.com (Rich Gregory ) wrote:
 > > We're setting up a new server at work and are trying to get
 > > the new server to print through to the old servers
 > > printers.  So far I've created the queues & created a print
 > > server on the new server.

 > I solved a sililar problem a while ago... here's how I
 > finally solved it.  

 > 1)  Install AppleTalk on BOTH servers.
 > 2)  On the old server, edit the ATPS.CFG so you broadcast the printer
 >     you want to "share" as an Appletlk printer
 > 3)  On the new server, edit the ATPS.CFG file so it intercepts the     
 >     newly created AppleTalk printer, and advertises it as a regular
 >     NetWare printer

 > and, voila!  Users on both servers can print to all "shared"
 > printers. I tried to include examples of what to put in the
 > ATPS.CFG files, but I can't remember exactly I put...  If
 > you need more specific help, email me and I'll send you a
 > copy of what I've got.

Seems like a roundabout way of doing things, doesn't it?  We plan to
get rid of the old server as soon as we are sure the new server is
"okay".

-- 
Take care      |   This clown speaks for himself, his job doesn't
Wayne D.       |   pay for this, etc. (directly anyway)

>We're setting up a new server at work and are trying to get the new
>server to print through to the old servers printers.  So far I've
>created the queues & created a print server on the new server.

I solved a sililar problem a while ago... here's how I finally solved
it.  

1)  Install AppleTalk on BOTH servers.
2)  On the old server, edit the ATPS.CFG so you broadcast the printer
    you want to "share" as an Appletlk printer
3)  On the new server, edit the ATPS.CFG file so it intercepts the     
    newly created AppleTalk printer, and advertises it as a regular
    NetWare printer

and, voila!  Users on both servers can print to all "shared" printers. 
I tried to include examples of what to put in the ATPS.CFG files, but I
can't remember exactly I put...  If you need more specific help, email
me and I'll send you a copy of what I've got.

Rich Gregory

Wayne Dernoncourt (wayned@cpcug.org) wrote:
: I'm also cross posting this to the novell listserve (I hope) &
: comp.os.netware.misc

: We're setting up a new server at work and are trying to get the new
: server to print through to the old servers printers.  So far I've
: created the queues & created a print server on the new server.  I
: told the print server configuration/printer configuration that the
: printers were defined elsewhere (on the old server), I went to
: attached servers and attached to the old one, but when I bring up the
: list of queues to service, the ones on the new server only show up if
: I'm on the new server.  The question is how do I make the ones on the
: new server visible to the old server.  I deleted the new file
: server's print server configuration on the theory that since it
: "owned" the queues I was trying to print out on the old server, it
: would hide those from the other server -- that didn't work.

: Any clues for the slightly clueless.

The queues created on the NEW server, are only going to be visible on the 
NEW server.  The important things to focus on are 1) Match "exactly" the 
print server names.  2) Make sure that printer 0 on the old server is 
printer 0 on the new server (printer configuration).  The system couldn't 
care less if the queue names match across the servers.

One other important note.  Once all is running, if the new server ever 
goes down and you bring it back up, you'll have to unload and load 
pserver.nlm on the old server before jobs will be services by the printers.
Which also means that in order for this to even begin to work, once the 
new server is configured properly, you have to restart pserver on the old 
fileserver. 
--
 ----------------------------------------------------------------------
|- Dan Taylor - <danny@qnet.com>                                       |
|     "Think you can, or think you can't.  Either way, you're right".  |
 ----------------------------------------------------------------------