Re: Configuring networked printer

On Fri, 2007-04-06 at 19:44 +0100, andy wrote:
Greg Folkert wrote:
On Fri, 2007-04-06 at 19:12 +0100, andy wrote:
Greg Folkert wrote:
On Fri, 2007-04-06 at 16:25 +0100, andy wrote:

Hi all

OK - have fixed the old issue re: the OOo configuration
printing -
it
just required me to stop and restart the print server :)

Next issue - I'm wanting to be able to print from Box B to the
USB
printer which is located on Box A.
Box A is 192.168.1.40
I have changed the /etc/cups/cupsd.conf file to read:


Okay, in the CUPS web interface on the "remote" machine (the
machine
that has the printer connected), you only need to worry about
about
making sure the check box "Share published printers connected to
this
system" is checked. This turns on advertising and should
auto-magically
setup you local machine to use the printer on he remote machine.
It
also
removes any permission problems you might have.

You may have to do this from the machine with the printer
attached,
as
the default is to not check: "Allow remote administration"

I'd also suggest you check the "Allow users to cancel any job
(not
just
their own)" check box. It just makes things easier to deal with,
especially if you have Windows machines trying to print via
Samba.

The allow by IP stuff you are trying, get to be a BIG hassle and
begins
to fall apart quickly once you add other machines into the fray.


Thanks Greg

I have now set the "share" advertising checkbox as you suggested,
saved changes and the CUPSd restarted.

This is the latest response from the "client" (Box B) machine: An
error occurred while loading
http://valhalla.org:631/printers/EpsonDX6050?op=print-self-test-page:
Could not connect to host valhalla.org (port 631)

Valhalla = Box A (+ printer)

There shouldn't be any reason Box B is not allowed access to port
631
- under Slackware this was fine and I haven't adjusted the
firewall
(external OBSD) since installing Etch. What I was wondering is
whether
this the correct form and correct location of the necessary files:

ipp://192.168.1.40/printers/EpsonDX6050

This is how it is set up on Box B to access the remote printer on
Box
A. Is this the source of the problem?


Okay, you might be surprised at this, but you might have configured
you
"local" to not listen to advertising machine.

On your local machine, you need to have the check box named "Show
printers shared by other systems" checked. This then allows you
local
machine to auto-magically configure your printer on the remote
machine.

You should then see (within a few moments) the proper printer show
up.
You should not have to configure your local machine in any way,
other
than to select it. Though you should set CUPS to use the
"discovered"
printer by default.

Once that happens ( setting the checkbox on the local machine, the
discovery and setting of default) your machine should just work.

Greg

Thanks for this - I think this might be pretty useful, but I am
getting confused by what you mean by remote and local. Can I just go
over your suggestions using the following:
Box A (has printer attached 192.168.1.40 valhalla)
Box B (no printer 192.168.1.29 winlin)

Are you saying:
Box A must have the check box "Show printers shared by other systems"
checked?

I have done this on Box B and get the following when the server
restarts:
An error occurred while loading
http://ip6-localhost:631/admin/?OP=redirect:
Could not connect to host ip6-localhost (port 631)

Can you just clarify this one a bit for me please.

don't use the "ip6-localhost". Just use "localhost" ipv6 sucks at this
point in time.

And yes it is Box B winlin that needs this (Show printers shared by
other systems) set.

Box A does not need it, unless you have another machine sharing printers
that you want to use locally on Box A.

Box B winlin, is your workstation. It needs to listen.

Box A valhalla is a server, it needs to advertise.

Once you have properly setup A to be a server, and B to be a client and
the advertising works, the magic of CUPS will just be great.

This of course assumes Box A has the printer properly setup in the first
place. Which you've said it is.
--
greg, greg@xxxxxxxxxxxxxxx

Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: TCP Listener Problem
    ... If the local machine works and the remote doesn't, ... a "netstat -a" and see if the server is listening on the specified port. ...
    (microsoft.public.dotnet.framework.remoting)
  • __doPostBack Error -- Javascript
    ... and ran on the local machine. ... The program was then uploaded on a remote ... I think the problem occurs because the java runtime environment (or some ... needed java software) is missing on the server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to configuare caches box in sendmail
    ... i want to configuare one sendmail server. ... Mail Transport Agent (Sendmail) on a remote server. ... all mail for your local machine into one system mailbox on the remote ...
    (alt.os.linux)
  • Re: Run VB6 .exe on server from a remote machine on same network; db is SQL Server 2000
    ... program on a remote PC and control it locally? ... client on the local machine, as you do that you might as well install the ... program at the same time and avoid the network traffic of running a program ... database on the same server you will reduce traffic, ...
    (microsoft.public.vb.general.discussion)
  • E2K7 SP1 Rollup6 / W2K8 - IIS Error
    ... I just installed a new E2K7 Server in a remote site and I get the following ... Unable to create Internet Information Services (IIS) directory entry. ... local machine name:xxxxxxx ...
    (microsoft.public.exchange.setup)