lan printers aren't detected

Hm, that works fine for me between two Breezy machines. Can you please do

  sudo /usr/share/cups/browsing_status; echo $?

on both machines and check that it is indeed '1'? Do you happen to have multiple
ethernet cards on the printer server? Can you please do the following on the server:

   sudo tcpdump port 631

and check that there is a message like

  18:10:27.929407 IP 10.28.130.200.ipp > 10.28.130.255.ipp: UDP, length 106

every 30 seconds?

(In reply to comment #1)
> Hm, that works fine for me between two Breezy machines. Can you please do
>
> sudo /usr/share/cups/browsing_status; echo $?
>
> on both machines and check that it is indeed '1'?
It echo's nothing at all... However i checked the file on both machines and it
does say "Browsing On" in both files.

> Do you happen to have multiple
> ethernet cards on the printer server?
Nope

> Can you please do the following on the server:
>
> sudo tcpdump port 631
>
> and check that there is a message like
>
> 18:10:27.929407 IP 10.28.130.200.ipp > 10.28.130.255.ipp: UDP, length 106
>
> every 30 seconds?

And this doesn't work on either of the machines, as can be expected.
I did fiddle around a bit with cups since the browsing didn't work. Maybe i
should just purge and reinstall it.

(In reply to comment #2)
> (In reply to comment #1)
> > Hm, that works fine for me between two Breezy machines. Can you please do
> >
> > sudo /usr/share/cups/browsing_status; echo $?
> >
> > on both machines and check that it is indeed '1'?
> It echo's nothing at all...

Erm, that's close to impossible, "echo $?" prints the exit status of the
previous command, it should print "0", "1", or "2".

> > Can you please do the following on the server:
> >
> > sudo tcpdump port 631
> >
> > and check that there is a message like
> >
> > 18:10:27.929407 IP 10.28.130.200.ipp > 10.28.130.255.ipp: UDP, length 106
> >
> > every 30 seconds?
>
> And this doesn't work on either of the machines, as can be expected.

Do you have any firewall in place, or similar?

> I did fiddle around a bit with cups since the browsing didn't work. Maybe i
> should just purge and reinstall it.

Could help - please report if it did.

Thanks

Oops, my bad. I thought the questionmark was part of the question.
On both machines it echoes 1.
A purge and reinstall didn't help
And for the firewall: my linux router block some incoming ports but that
shouldn't have anything to do with it and has always been there.

(In reply to comment #4)
> Oops, my bad. I thought the questionmark was part of the question.
> On both machines it echoes 1.

OK, that's fine. It means that browsing is enabled from the configuration's
point of view.

Could you please tar up your configuration directory and send it to me? Maybe I
can reproduce it then:

 sudo tar cz /etc/cupsys > cupsys-conf.tar.gz

If it contains any sensitive data (passwords and the like), then please clean it
up first and/or email it privately to me (<email address hidden>). If not, just
attach the tarball here, please.

Created an attachment (id=4764)
the "client" side cups config

Created an attachment (id=4765)
the "server" side cups config

Thanks for the files!

(In reply to comment #8)
I had the same problem between a mandrake client and a breezy server, upgraded
from hoary:
in fact, the following option:

Browsing On

is not enough to allow client to connect to a cupsys server: my problem was that
my breezy server had the following too restrictive option:

Listen 127.0.0.1:631

which disallow connection from outside 'localhost'
i had to change that in :

Listen @LOCAL:631

to allow client connection from the LAN (not WAN of course)

I've tried your suggestion.
However when i now start gnome-cups-manager on the client i have to wait about 5
minutes (waaay to long for a timeout imo) without seeing anything happen. After
those 5 minutes i got a message "Couldn't connect to cups-server". So
appearantly things didn't get better for me...

Martin, where you able to reproduce this with my cups config files?

I reinstalled the client machine which is now running Dapper. Printer sharing works like a charm now. I guess this can be closed if i was the only one with this problem.

thanks for checking this again!