Popular Content

Showing content with the highest reputation on 01/13/2012 in all areas

  1. -1 points
    You would be much better off trying to find the CUPS or LP forums and asking there. But, port 9100? Is it capable of being set up as a IP printer like most net enabled printers? Or can you access it's webserver and just submit pdfs or what not like that? Sure, its not ideal, but setting up a PS or PDF printer on your linux box and then dropping the pdf to the printer's http server (or ftp server) can get you running for now. Apparently, Lexmark does not use regular standards, or support Linux at all. If you have a Mac or OSX box, there are mac drivers for it, and OSX uses CUPS just like linux. That should help guide you towards a quicker result than trying to work from Windows drivers.
  2. -1 points
    I recently got a Lexmark x4690 wifi printer. It is a quite nice printer, except for the fact that it doesn't work with Linux. I can use my brother's computer that runs Windows to print, but I'd like to be able to print from Linux. I've installed the printer so that it connects wirelessly to my router as a network printer, to avoid the trouble of going through a computer that must sit there waiting for printing jobs. A network printer protocol is probably much easier to reverse engineer and program for than reverse engineering a USB printer driver and then writing a new one. I've used wireshark to capture the packets as I was printing the test page (the test page the software asks you to print to test that the printer is working fine). Wireshark seems to be putting protocol names that are close to what the printer is using but not exactly it (it reports checksum errors in the packets, probably some kind of checksum used by the protocol it thinks it is, but the checksum must be different with this printer protocol). I've uploaded the wireshark packet capture here for other people to study it. In the packet capture, is the computer from which I was printing and is the printer. I also ran nmap to see what services were running on the printer: Interesting ports on Not shown: 1709 closed ports PORT STATE SERVICE 21/tcp open ftp 80/tcp open http 8000/tcp open http-alt 9100/tcp open jetdirect 10000/tcp open snet-sensor-mgmt 50000/tcp open iiimsf Not all of the services shown by nmap seem to be used in the packet capture, maybe the printer supports other network printing protocols? No idea. All ideas are welcome.