Open makcakaya opened 7 years ago
Btw, now I tried to run Angry again, it did not find any hosts while Advanced IP Scanner finds the hosts. So the issue does not have a direct relation to first use.
I'm getting a similar problem pinging a device on my network from my Macbook.
AngryIP latest version shows that 192.168.1.1 is not alive, however using ping in my Mac terminal window I get:
64 bytes from 192.168.1.1: icmp_seq=299 ttl=64 time=0.442 ms
I get exactly the same results on a second Mac.
Any ideas?
@makcakaya What happens when you run Angry IP Scanner as administrator? Running it normally, for me, produces 0 host alive. However, after running it as an administrator, the scan functions as expected producing the correct number of alive hosts.
I have the same issue but on windows 10 & mac os x sierra... both are administrator accounts.... any new news on this issue?
@derek015 On your Win 10 machine, what happens if you try running Angry as administrator? I understand that your login account is an admin, but you'll likely still need to right-click the icon and select "Run as administrator".
Pretty much the same. A little update, I have a few PCs and a couple macs.
I was able to get this to work on my other pc windows 10 on 3.4.2. But I use my Mac the most so I’d like to get it to work there. It used to work on the Mac until I upgraded so I been trying to downgrade and see if it comes back but it still has not.
For me the problem was having multiple enabled networks. Disabling all the virtual networks (hyper-v, virtualbox, vpn) made AngryIP run successfully without Administrator permissions.
Still it's unacceptable for a network tool to not handle multiple NIC
I am still having issues with this... On my windows 10 machine, I have this working on an older version. On my iMac (most my machines are mac) I cannot get alive hosts to show at all... Firewall isn't turned on so I know that is not the issue... Can anyone from AngryIP assist?
Same issue, only works by running as administrator even though the machine only has 1 interface, the rest are disconnected VPN tunnels, which cannot be disabled on their own.
Same issue here with 3.5.5. Runs fine in my win10 VM. Threads stay at 1, it seems to scan then gives no results. I even disabled all virtual NICs and the firewall. :(
Same problem on Linux Mint. Try to ping a live known ip, no success.
So I think maybe the problem is the router.
Sometimes, when I search for hosts on my LAN after I just started Windows, no host can be found.
In this case I ran Angry IP Scanner first time after I started Windows and got no results:
Then I ran Advanved IP Scanner and got the expected results:
After that, I ran Angry IP Scanner again and got the expected results this time.
The application version is 3.4.2. I am running a Windows 10 Pro 10.0.14393 x64.