Macos – How to scan the local network for connected devices? (Mac OS)

It looks like many people are having the same problem as you.

There seems to be no official solution out there yet. Here are some workarounds that might work.

1. Using a mix of Vista and Windows 7 drivers (link with step-by-step tutorial)

   After several hours we found the solution to install drivers and let the Toolbox fully work so far (push/pull scanning, faxing) using a mix of Vista and Windows 7 drivers.

2. Downgrade to Win7 32-bit (link, see 2009/11/9 reply)

   I was able to install the latest version of the software onto windows 7 32bit. The scanner and all functions work flawlessly. As for 64bit, you're out of luck. I doubt that hp will ever work on it. I ended up downgrading to 32bit so I can get all of the drivers to work with my laptop.

3. Using Windows Virtual PC XP Mode (link, see 2010/5/23 reply)

   ...
   This seems to be an easy workaround
   It works with ALL the features

4. Run Installer with Compatibillity Mode (link, see 2010/5/31 reply)

   I found way to install this scanner and finally works for me.
   ...
   Right click on file, than Property and finally tab "Compatibillity Mode". You need to select Windows Vista SP2 thank click on Apply.
   After the 5 files have been to run in "Compatibille Mode" double click the autorun and follow installation

(I have not tested any of the above methods. Hope these still helps.)

Having the same MAC address appear several times is not necessarily a problem. The mapping is one-way: from IP address to MAC address. The ARP table is the way through which the OS knows the MAC address which should be used to send a packet to a machine with a given IP address. If a given machine assumes several IP addresses simultaneously (or in close succession), all with the same hardware interface, then you will get several entries with the same MAC. While this is supported and not, in itself, a problem, this might indicate something fishy in your case.

The "redirect host" messages are traces of ICMP Redirect packets. Namely, a machine claiming to have IP address 10.100.100.130 is reacting to your "ping" request, and tells to your machine "hey you, 10.100.100.125, when you want to talk to 173.246.99.7, you should send the packet to router 10.100.100.1". Presumably, your machine sent the request to another gateway address, which worked (since the target host responded). Use netstat -rn to display your current routing table.

These messages seem to indicate that you have two routers on the local network. This is unusual. There again, this is not a lethal issue (the Internet was designed to be redundant with several paths from any two points) but may indicate some configuration problem, or possibly an ongoing (and inexpert) attack attempt (one of the other systems trying to redirect the traffic of the other hosts to itself).