1 |
Hervé Guillemet <herve <at> guillemet.org> writes: |
2 |
|
3 |
|
4 |
> Le 12/07/2014 16:59, James a écrit : |
5 |
> > Hervé Guillemet <herve <at> guillemet.org> writes: |
6 |
|
7 |
> If someone else had success with these printers, please reply so that we |
8 |
> can see what differ in our installations. |
9 |
|
10 |
|
11 |
Sorry for the late response, I had some ideas last night....... |
12 |
|
13 |
Here are 4 packages/flags/protocols that you should research and |
14 |
see if they work. If Debian or Ubuntu have this printer working, |
15 |
it would be keen to put one of those machines and your printer |
16 |
on an isolated subnet and run wireshark to see what protocols |
17 |
are at work. |
18 |
|
19 |
|
20 |
avahi\zeroconf |
21 |
dbus |
22 |
foomatic |
23 |
snmp (snmpwalk, snmpget, |
24 |
net-analyzer/mbrowse |
25 |
|
26 |
Also connect to the 'embedded web server' built into most |
27 |
modern printers. First setup the IP address of the printer |
28 |
from the printer menu, then ping the printer from your linux |
29 |
system (fills arp table) and then type in the IP address |
30 |
from your browser on your linux system and the printers web server |
31 |
should respond. Maybe something needs to be turned on from |
32 |
the menu system in the printer's embedded web server? |
33 |
|
34 |
Have wireshark running on another linux system to sniff the sessions. |
35 |
Isolate (filter) wireshark to the protocol(s) you want to capture/study. |
36 |
|
37 |
SNMP might also give you clues as to the error. You are most likely |
38 |
just missing something simple (at least once you discover the |
39 |
problem)..... |
40 |
|
41 |
|
42 |
[1] https://bbs.archlinux.org/viewtopic.php?id=152519 |
43 |
|
44 |
[2] https://bbs.archlinux.org/viewtopic.php?id=148850 |
45 |
|
46 |
[3] http://gimp-print.sourceforge.net/p_Supported_Printers.php |
47 |
|
48 |
[4] http://avahi.org/wiki/AboutAvahi |
49 |
|
50 |
|
51 |
hth, |
52 |
James |