Bug 199417 - can't get printer list from ipp server
can't get printer list from ipp server
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-07-19 10:00 EDT by Karsten Hopp
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-20 07:56:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
cupsd.conf (1.76 KB, text/plain)
2006-07-20 04:41 EDT, Karsten Hopp
no flags Details

  None (edit)
Description Karsten Hopp 2006-07-19 10:00:13 EDT
Description of problem:
lp, lpq, kprinter all report that no printers are found. 
The machine next to mine can see all configured printers.

Here are some commands we've tested vi IRC:
#lpstat -r
scheduler is running

#lpstat -s
no system default destination
lpstat: No destinations added.
lpstat: No destinations added.

#tcpdump udp port 631
16:05:19.569772 IP someprintserver.redhat.com.ipp > UDP,
length 160
16:05:21.569557 IP someprintserver.redhat.com.ipp > UDP,
length 157
16:05:22.568824 IP someprintserver.redhat.com.ipp > UDP,
length 143

At the same time in /var/log/cups/error_log:
D [19/Jul/2006:16:05:19 +0200] cupsdNetIFUpdate: "lo" = localhost...
D [19/Jul/2006:16:05:19 +0200] cupsdNetIFUpdate: "eth0" = printclient.redhat.com...
D [19/Jul/2006:16:05:19 +0200] cupsdUpdateCUPSBrowse: Refused 160 bytes from
D [19/Jul/2006:16:05:21 +0200] cupsdUpdateCUPSBrowse: Refused 157 bytes from
D [19/Jul/2006:16:05:22 +0200] cupsdUpdateCUPSBrowse: Refused 143 bytes from

Version-Release number of selected component (if applicable):

How reproducible:
Comment 3 Tim Waugh 2006-07-19 10:44:36 EDT
Could you attach your /etc/cups/cupsd.conf file please?  I haven't been able to
reproduce this problem here so far.
Comment 4 Karsten Hopp 2006-07-20 04:41:59 EDT
Created attachment 132731 [details]
Comment 6 Tim Waugh 2006-07-20 07:51:37 EDT
For the record: the browse packets don't match the local interface's address and
mask because they original outside a local VLAN.
Comment 7 Tim Waugh 2006-07-20 07:56:41 EDT
Reported upstream:


Note You need to log in before you can comment on or make changes to this bug.