Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 2
    The problem here is that the criteria ("Network Printer") is something that only makes sense to humans. Computer programs aren't going to have a clear sense of that idea. You might try doing a network sweep for IP addresses that successfully connect on the JetDirect port (tcp/9100). The list is still likely to be incomplete in the case of non-JetDirect printers such as desktop printers shared over SMB. Commented Jun 30, 2014 at 18:16
  • 1
    As you mention, a program can scan open ports of each IP on the LAN, and even do a little talking to those ports to gather data. I understand how this could be done. I'm just unaware of any command line utility that already does this (specifically for printers). Commented Jun 30, 2014 at 18:44
  • 1
    You can do sweeps to find a list of valid IP addresses and use nc to verify that it can connect on tcp/9100. You'd have to script something since this is a very specific problem you're trying to solve. So I doubt anyone's written a tool to do this. Commented Jun 30, 2014 at 19:33