Opened 4 years ago

Last modified 3 years ago

#19 new defect

Network printers not detected with install via Realtek NIC

Reported by: robh Owned by:
Priority: major Milestone:
Component: Portdriver Version:
Severity: medium Keywords: install realtek
Cc:

Description

Recently I installed the latest driver (3.12.8) for the Realtek NIC on my motherboard (Gigabyte Z68X-UD3H-B3), and it works fine with connection to Internet and file transfer to and from a NAS. But when installing a new (network) printer via the eCups wizard menu 'Install CUPS printer' after selecting a brand+type no printer is found and manual install is the only choice. But even after specifying the correct IP address (ping works) nothing is ever printed. Job status is 'printer does not exist' (or similar words). However when installing a new printer by using an Intel NIC (on a PCI card) my network printers are detected properly and work fine, even after switching back to the Realtek NIC. So it seems purely an install issue with eCups and the Realtek NIC. The issue is reproducible.

Change History (4)

comment:1 Changed 4 years ago by David McKenna

Rob,

I am having a similar issue with eCUPS and a Realtek NIC. Unfortunately, I don't have another NIC to install. I was wondering if you could post here what appears next to 'Connection' on the working printers' page in the CUPS web interface on your system?

comment:2 Changed 4 years ago by David McKenna

Never mind... I figured it out...

comment:3 Changed 4 years ago by robh

I'm sorry for my slow reaction, I'm not monitoring this issue frequently. I could not find 'Connection' in the web interface, but that seems not needed anymore.. FWIW, the newest R8169 driver (16 feb 2014) doesn't make a difference.

comment:4 Changed 3 years ago by ataylor

I suggest you check the output of 'lpinfo -v' (you probably have to run this from the \cups\sbin directory) while using the Realtek NIC. Also compare it with the output of 'snmp' (run from the \cups\lib\cups\backend directory).

It would be interesting to see if one of these commands detects your printer but not the other, or if neither one does.

Note: See TracTickets for help on using tickets.