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

[Robert L Krawitz]

   From: "Miles Lane" <miles.lane at gmail.com>
   Date: Fri, 24 Mar 2006 23:06:50 -0800

   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 out to be a huge problem for CUPS/Gutenprint.  I
   have selected the Gutenprint 5.0 B2 driver and set the printer port
   to socket://192.168.1.1:9101, but when I try to print the test
   page, what tcpdump shows me is this:

   22:37:17.999706 arp who-has 192.168.1.1 tell 192.168.1.10
   22:37:18.000818 arp reply 192.168.1.1 is-at 00:03:93:e0:5a:a8 (oui Unknown)
   22:37:18.807881 IP 192.168.1.10.38284 > 192.168.1.1.jetdirect: S
   1303058048:1303058048(0) win 5840 <mss 1460,sackOK,timestamp 6283757
   0,nop,wscale 2>
   22:37:18.808824 IP 192.168.1.1.jetdirect > 192.168.1.10.38284: R
   0:0(0) ack 1303058049 win 0
   22:37:28.812496 IP 192.168.1.10.38286 > 192.168.1.1.jetdirect: S
   1314878226:1314878226(0) win 5840 <mss 1460,sackOK,timestamp 6286258
   0,nop,wscale 2>
   22:37:28.813463 IP 192.168.1.1.jetdirect > 192.168.1.10.38286: R
   0:0(0) ack 1314878227 win 0
   22:37:43.817074 IP 192.168.1.10.38288 > 192.168.1.1.jetdirect: S
   1332271175:1332271175(0) win 5840 <mss 1460,sackOK,timestamp 6290009
   0,nop,wscale 2>
   22:37:43.818038 IP 192.168.1.1.jetdirect > 192.168.1.10.38288: R
   0:0(0) ack 1332271176 win 0

   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 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?

I can't see how this would be a Gutenprint problem, since Gutenprint
merely provides a PPD file (which doesn't know anything about output
ports) and the output byte stream, which also is independent of the
final output.  I suspect this is a configuration problem since you
managed to get it working before, unless perhaps you upgraded
something else in the interim.