Another option might be to hook up the network printer to an old school network *hub* and then hook up another computer, running Wireshark to sniff the packets.
Chris Chris On Mon, Nov 5, 2012 at 6:45 PM, David R. Wilson <[email protected]> wrote: > Hello Howard, > > Is there any chance of configuring a box as a firewall to the printer so > you could see if there is any traffic to the printer and exactly where > it is originating? No firewall rules need to be there, but it would > make it possible to see what the traffic looks like and find out a bit > about the origin. > > Beside the possibility that the software in the printer is corrupt, or > it has a hardware problem, that would tell which direction to go with > that problem. > > Dave > > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
