IP Scanning not finding devices

[Ponchohobono]

There are several devices that are not showing up in the IP scan. I don't even see an entry in the errorlog.txt file of it pinging the device but not finding any open ports. What can I do to troubleshoot further?

[Ponchohobono]

It's an NT 4 workstation that is a DVR for cameras. It's not on the domain but as you can see it was being picked up by the IP scan as a NAS device until 8/28/2010. Did perhaps a Lansweeper upgrade change the way this device would be detected?

[Hemoco]

Ponchohobono wrote:
It's an NT 4 workstation that is a DVR for cameras. It's not on the domain but as you can see it was being picked up by the IP scan as a NAS device until 8/28/2010. Did perhaps a Lansweeper upgrade change the way this device would be detected?

Yes, it is (correctly) identified as a windows machine now.
If you can close port 135 on that computer (disable dcom) it will be detected as a nas again.

[Hemoco]

This device will be skipped because is is marked as a windows computer.
What kind of device is this?

[Ponchohobono]

I should also add that these devices were being detected until 8/28/2010. Below is a screenshot of the device & the device tester output.

SNMP Not active or community name wrong
Port 135 is open
Port 139 is open
Port 445 is closed
MAC address: 00-00-50-04-FE-02
Netbios information not accessible
FTP port is open
FTP enabled
220 accutrack-108 Microsoft FTP Service (Version 3.0).
SMTP port is closed
HTTP port is open
HTTP server: Microsoft-PWS/3.0
HTTP title: Diebold - DVR Login
HTTPS port is closed
SIP port 5060 is closed
HP jetdirect port 9100 is closed
SSH port 22 is closed

Scanning done!

[Hemoco]

You can try the device tester and check the output.
Make sure the device is pingable and increase the ping timeout if needed.