Agent not detecting a Windows PC

[Automate 5]

Agent running on RPi is not detecting one of my Dell laptops running Win 7.  The laptop is on WiFi and does go to sleep when not in use but it's on enough that the agent should detect it.  16 devices have been detected by domotoz including 2 Win PCs.  Is there a way to force a scan of the network?   

[Lars 10]

No, there's no way to force a scan right now. 

That said, this sounds odd, as there's no reason why the device shouldn't show up.

[Automate 5]

Just tried, and I can't ping it from the network. I'm guessing it has the Windows firewall turned on.

[Giancarlo 31]

Actually, even if with the firewall enabled, the Domotz Agent should be able to detect it.

The scan is triggered periodically: therefore, if the Win 7 laptop is on for few minutes, it should be detected by Domotz. Are the RPi and the Laptop on the same class C subnet?

[Automate 5]

@Giancarlo  Yes, all devices are on the same class C subnet, both wired and wireless.

 

So my Agent has been running for 6 days and never detected this one computer.  All this time the computer was on (although during inactivity it does go to sleep) and at least 8 hours a day it was used by someone with internet access so I know it was on the network.  The user was a non-admin user.   I wanted to check how the firewall was configured so I logged in as an admin and saw the firewall was turned on but basically nothing was being blocked.  So I checked domotz and the computer just showed up for the first time ever.  I could also ping it on the network.  Strange 

 

Back to the topic of Windows firewall.  It can configured to block pings so what protocols/ports does the agent use to find devices?

Edited November 9, 2015 by Automate

[Giancarlo 31]

The Domotz Agent is working both with ping and ARP ping to identify devices which are alive. We will try to reproduce this scenario in our test bed and check if anything else can be done in such scenario. 

[System_Error_Message 2]

This would explain why domotz isnt detecting some of my network clients since they dont respond to pings. When using static IP they dont respond to pings but on my ISP network they have DHCP but arent being detected although they do respond when i ping them on the raspberry pi in the 10.xx network but not in the 192.xx network.

Edited November 10, 2015 by System_Error_Message

[Automate 5]

Found the problem.  Windows Firewall was set to block all incoming traffic (including pings) but only when connected to a public network.  Due to other network changes I had made, Windows did not recognize my home network and assumed it was on a public network and thus blocked the pings.

[Giancarlo 31]

Glad to hear about that. 

[System_Error_Message 2]

for me thats not an option since i use a static config so it will always say it is a public network.

[Automate 5]

1 hour ago, System_Error_Message said:

for me thats not an option since i use a static config so it will always say it is a public network.

Then you will have to create a Windows Firewall rule to allow incoming ping requests.