The problem maybe caused by bugs in the printer's implementation of IPP. However my printer worked perfectly well using IPP under breezy. I get this bug on dapper though (see my previous posts in the bug report - Bug #43352). So I guess the http backend program changed in such a way that it didn't like mine and other printers' IPP stacks. My printer works fine using lpd under dapper.
On my dapper machine with cupsys 1.2.2-0ubuntu0.6.06 I get:
user@ubuntu:~$ sudo /usr/lib/cups/backend-available/snmp
INFO: Using default SNMP Address @LOCAL
INFO: Using default SNMP Community public
network ipp://192.168.1.201:631/EPSON_IPP_Printer "EPSON EPL-5800" "EPSON EPL-5800 192.168.1.201" ""
The problem maybe caused by bugs in the printer's implementation of IPP. However my printer worked perfectly well using IPP under breezy. I get this bug on dapper though (see my previous posts in the bug report - Bug #43352). So I guess the http backend program changed in such a way that it didn't like mine and other printers' IPP stacks. My printer works fine using lpd under dapper.
On my dapper machine with cupsys 1.2.2-0ubuntu0.6.06 I get:
user@ubuntu:~$ sudo /usr/lib/ cups/backend- available/ snmp 168.1.201: 631/EPSON_ IPP_Printer "EPSON EPL-5800" "EPSON EPL-5800 192.168.1.201" ""
INFO: Using default SNMP Address @LOCAL
INFO: Using default SNMP Community public
network ipp://192.