[cups.bugs] Cannot print to jetdirect port 9101 (Fedora Core 5+cups-1.2-0.1.b2.3 + Gutenprint 5.0 Beta2)

[Miles Lane]

On 3/25/06, Michael Sweet <mike at easysw.com> wrote:
> Miles Lane wrote:
> > On 3/25/06, Michael Sweet <mike at easysw.com> wrote:
> >> Miles Lane wrote:
> >>> Hello,
> >>>
> >>> I have been trying to get Cups/Gutenprint to print to my Epson Stylus
> >>> Photo R340 which is connected to the USB port of my Airport Extreme
> >>> wireless access point.  I am able to print to this printer with both
> >>> Apple's OS/X and Windows XP.  A recent firmware upgrade for the access
> >>> point changed the jetdirect port from 9100 to 9101.  This has turned
> >>> ...
> >>> It seems to me that "192.168.1.1.jetdirect" should be
> >>> "192.168.1.1.9101".   When I previously tried to get this all working
> >> If you look in /etc/services, you'll probably see jetdirect listed
> >> multiple times for 9100, 9101, and 9102.
> >
> > Nope.  Jetdirect is only assigned to port 9100, so this is the same
> > problem I had before, where my nonstandard port selection is
> > being ignored my Cups.  In other words, Cups is not using port
> > 9101, even though I specified it in the socket definition.
>
> Highly unlikely, as the socket backend uses the httpSeparate API
> which returns the port from the URI, if supplied.
>
> Try doing a tcpdump without name lookups (-nn option) to see the
> raw port numbers.

This resulted in:

19:51:34.556944 IP 192.168.1.10.49568 > 192.168.1.1.9100: S
3771424590:3771424590(0) win 5840 <mss 1460,sackOK,timestamp 12027530
0,nop,wscale 2>
19:51:34.557910 IP 192.168.1.1.9100 > 192.168.1.10.49568: R 0:0(0) ack
3771424591 win 0

As you can see, I was right.  Cups is printing to port 9100, even
though my socket is defined as socket://192.168.1.1:9101

When I load http://localhost:631/printers, the Cups admin page shows
that my socket is defined as:  "socket://192.168.1.1:9101".  The Cups
admin page also shows the Cups version as "CUPS v1.2svn".  Oddly, when
I open gnome-cups-manager 0.31, it shows the port as 9100.  I should
point out that is doesn't matter whether I try to print the test page
from the gnome-print-manager or from the CUPS web admin interface. 
Both attempts use port 9100.

> >>> with the gimpprint stable drivers, instead of seeing
> >>> 192.168.1.1.jetdirect, I saw 192.168.1.1.9100.  Neither the 9100 or
> >>> jetdirect ports are getting output from my printer.  How can I fix
> >>> this?  Is this a CUPS or gutenprint bug?
> >> Neither, it is probably just that the access point may not be using
> >> the JetDirect "protocol"!
> >
> > As I said before, Windows XP and OS/X print to this port fine.
> > I am certain that the jetdirect protocol is supported.
> >
> >> Best thing to do is post a question to the Apple "printing" mailing
> >> list - go to "http://lists.apple.com" to subscribe.
> >
> > This isn't an Apple problem.  So, any ideas why this is failing in Cups?
>
> You are printing from Apple's version of CUPS to an Apple print
> server, which makes it an Apple problem.

Nope.  I am running into this problem on a PC.  I have both Fedora Rawhide
and Ubuntu Dapper + all updates.  I encounter this same failure on both
distros.  I just reproduced the issue with:

      cupsys         1.1.99.b1.r492
      cupsys-driver-gutenprint               4.3.99+cvs20051122.dfsg.1-2ubuntu1
      The driver is listed as "Stylus-Photo-R340---CUPS+Gutenprint-v5.0.0-rc2"
      foomatic-db-gutenprint                 4.3.99+cvs20051122.dfsg.1-2ubuntu1
      ijsgutenprint                          4.3.99+cvs20051122.dfsg.1-2ubuntu1
      libgutenprint2                         4.3.99+cvs20051122.dfsg.1-2ubuntu1

So, now what?  Any chance you could try to reproduce this problem?
Do you need additional diagnostic information from me?

I will send you the corresponding package details from my Fedora development
 installation in a couple of minutes, after rebooting.

Cheers,
         Miles