Cannot print to a printserver connected printer from ubuntu 8.04, while ubuntu 7.10 and 7.04 do the job without any problem.

I have exactly the same problem with a HP P2015 laserjet connected to a Planet FPS-1010 print server. It works fine on 7.10 but doesnt works on 8.04 and I can't find a solution.

I have the same trouble as above,with the following difference. My configuration is router,netgear print server,Samsung ML2010 printer set up as a LPD printer.
All worked great with 7.10 but reloaded the system to 8.04 and get the above message. printer ml-2010 may not be connected.

The same on another brand new system (1 is an AMD the other intel)

Sorry: another comment about the above.. The system that I reloaded from scratch was upgraded from 7.10 to 8.04 with no trouble but when I did a
complete reload for unrelated reason, thats when the trouble began

adonet, please provide the output of the printingbug info script when booted into Ubuntu 8.04.
The printingbug info script can be found here: https://wiki.ubuntu.com/PrintingBugInfoScript.

Hi,

I'm looking into a similar problem, but I am getting it with completely different Hardware..

I've got a samsung ML-1510 laser Printer and An Epson R800 Inkjet connected to a 3205uw print server. The connection is over wired ethernet and a Windows PC also uses these printers. The windows PC works faultlessly.

I have configured the Printers through cups (http://localhost:631). Both printers have the correct drivers and are being addressed correctly via IPP. I can get an initial test print off each and then that's it. The cups screen shows no active jobs but the status of both printers as "waiting for active job to complete". In Gutsy cancelling the job cleared this. It does not appear to do so in Hardy.

I've used Firestarter to allow incoming traffic from the Edimax Printserver, so I don't think it's a firewall problem.

Digging a bit deeper I had a look at /var/log/cups/error_log and found:
Code:

E [02/Jun/2008:08:22:12 +0100] [CGI] Unable to send 46 bytes to 192.168.0.255: Operation not permitted
E [09/Jun/2008:08:10:26 +0100] CUPS-Add-Modify-Printer: Unauthorized
E [09/Jun/2008:08:10:48 +0100] cupsdAuthorize: pam_authenticate() returned 10 (User not known to the underlying authentication module)!
E [09/Jun/2008:08:10:48 +0100] CUPS-Add-Modify-Printer: Unauthorized
E [09/Jun/2008:08:12:24 +0100] CUPS-Add-Modify-Printer: Unauthorized
E [09/Jun/2008:08:13:18 +0100] [Job 1] Destination printer does not exist!
E [09/Jun/2008:08:13:18 +0100] PID 21074 (/usr/lib/cups/backend/ipp) stopped with status 4!
E [09/Jun/2008:08:16:29 +0100] CUPS-Add-Modify-Printer: Unauthorized
E [09/Jun/2008:08:17:41 +0100] Purge-Jobs: Unauthorized
E [09/Jun/2008:08:20:02 +0100] CUPS-Add-Modify-Printer: Unauthorized

It looks like some sort of permissions problem but I can't figure out what as yet. I suspect it's in CUPS, but I'm not clear what. I've tried setting the CUPS Server to allow any user to cancel jobs, but that has not worked

That's where I'm at - I've attached the printbuginfo output file. The only thing that strikes me is that there is no (apparent) driver for the Epson R800 even though i installed one from the CUPS configuration page and there are Konica Minolta and HP drivers I didn't install.

Andy

Sorry just noticed I missed the make of the Print server - It's an Edimax.

I am also running the latest kernel update

Andy

Dear Pascal de Vuyst

I attached the output of printingbuginfo

I m running the newest kernel 2.6.24-18-generic

Jeroen

I can make my print server work only booting with a kernel 2.6.22-14-generic Kernel. With any other version it's impossible to print, including the last one right now (2.6.24-18-generic). I think there's something related to the kernel...

I didn't realize that there was two bug reports for the same problem. Perhaps the administrators should be merging Bug#235197 and Bug#237759 together?

I am having the same problem using Ubuntu 8.04, a wired ethernet print server (Zonet ZPS3603), and an HP Laserjet 1100 printer.

Do I need to attach a PrintingBugInfo report?

Thank you.

Never mind.
As of the 2.6.24-19-generic kernel update today, I am now able to print!!!! :)

Thank you.

Thats not really the case with my system. I 've been able to print one page out of a document of three pages and it took me half an hour to print. They seem to be on their way, but still a long way to go.

I keep on using ubuntu Gutsy 7.10

I've updated to kernel 2.6.24-19 and like adonet I'm not seeing any change. "Document Print Status" continues to show "processing" and there is no indication of activity of the printer. I've added an updated printingbuginfo report to the message.

Same problem here:

- Hardy with kernel 2.6.24.19-rt cannot print to IP printer (socket://192.168.x.x) using LogiLink PS0001 parallel printserver and HP-Lj-2-compatible printer (IBM-4037-5E in HP compatible mode) with "HP LaserJet 2 Foomatic/laserjet (recommended)" driver. Printer accepts some data, then switches to "waiting".

- Same printer works flawlessly from virtualbox Windows XP as a guest under Hardy with bridged networking.

Did not try older kernels so far, as recommended by some.

Patrick

P.S.: Sorry about the Windows virtual machine bit, no trolling intended. I mentioned it only as an indicator that it is no hardware issue in my case.

Patrikc

Tested same configuration with 2.6.22-14-generic kernel (from gutsy repos), printer works.

Seems to be a kernel problem with the 2.6.24 series, as already suggested by others.

Patrick

Marked as duplicate after further research. The workaround is also mentioned in the other bug report:

add a line with

net.ipv4.tcp_frto = 0

to /etc/sysctl.conf. Works a charm here :-)

I am sorry, but this doesn't work either on my system. Still getting the same messages asking whether or not the printer is connected.

I have /home on a separate partition from my system and when I upgraded i simply reformatted the system partition and reinstalled. When you do this you create a new user, which might be the same username and password as you used on the old install, but as far as the system is concerned is different. Consequently your new login can not access the .XXXXXX configuration files on /home.

Thanks to nelz at linuxformat.co.uk for spotting this. The solution is to run in the terminal:
    sudo chown -R username: ~username

Where username is the username you login with after a restart. You should reboot after doing this.

I can now print multiple docs to both printers on my Edimax printserver, provided I go into the print queue and cancel the document when it has come off the printer. So I am Now back to where I was with Gutsy

Hope this helps

Andy

Note: Andy Coulson's problem is not the one described by this bug nor by bug 213081.