1

Hi all,

I am having trouble completing the network scan successfully. Receiving the “No open ports for this device were found to be responding. This typically means that there is a firewall or permission issue preventing remote access.” after scan for only windows 10 devices.

-All computers on AD Domain.

-Brand new install of Spiceworks ver. 7.5.00107

-Only windows 10. windows 7, windows 2012, printers, etc. all scan fine.

-Spiceworks install is on a windows 10 computer not part of the Active Directory

-Disable Windows Firewall

-Port 135 (WMI) Open

Thank you in advance for all the help.

1 Spice up
2

Sounds like firewall to me , can you ping one of these machines? Connect to it via RPC? If No then it is either firewall or the account does not have the rights to perform this.

3

Give the tool here a try:

https://community.spiceworks.com/support/inventory/docs/unknowns-tool

4

I’d enable the firewall and add the exceptions needed. Also, the agent works a lot better than scanning.

5

Thank you all for taking the time to reply.

Scott, firewall is disabled, can ping all machines, rpc working, using AD administrator account.

Big green, tool didn’t work.

Bryan, tried that already.

Still nothing. Still not working. Thanks again.

6

Did it give you any findings?

What edition of Windows?

7

To the right of “set firewall rules” - “Cannot check Windows Firewall Settings because the service is not running. If this is intended then the scan should work.”

If not then please start the Windows Firewall Service and run this tool again.The computers not scanned completely are Windows 10 pro 1803

8

If I add the computer that has the Spicework server installed on it to the AD domain everything works fine. The scan completes without a problem.

I cannot keep this computer on the AD. How can I complete the scans without adding the SW server computer to the AD?

9

So it’s likely a rights issue then, since the tool reports everything is set correctly, and you aren’t trying to scan Windows Home. Scan it with an admin account that exists on that computer, and tell Spiceworks to use .\username as an account, where username is the name of the admin account. The .\ tells Spiceworks to use credentials local to the machine it’s scanning.

10

That’s how I have Spiceworks set already. The .\admin account has been set from the start, since install. I am using the .\admin to scan, but even with the .\admin set it does not scan unless the computer on which SW is install is added to the AD.

Is there a way to scan without adding the SW computer to the AD?

11

Are you able to connect via remote WMI using the same credentials? See https://community.spiceworks.com/support/inventory/troubleshooting/windows-scanning-issues#check-for-wmi-connectivity

12

Hi Ben,

If the machine which has SW on it is joined to the domain, Yes. If the machine which has SW on it is not joined to the domain, No.

13

If we can get the remote WMI tests from command line working, we should then be able to copy that over to the Spiceworks configuration.

Are you using “DOMAIN/username” format when testing the remote WMI from command prompt?

What error are you getting when you try that?

14

Yes, I am using the domain\user format.

When the computer which has the SW installation is joined to the domain there is no error. When the computer that has the SW installation is not joined to the domain I receive the access denied error.

15

Hi all. Still having problems. Just wondering if anyone has any ideas. Thanks in advance for any replies.

16

I know this is an older post, but I just had a batch of new Win 10 machines not able to be scanned. The event logs on the machine says that there was no way for the credentials to logon to the machine. Found that Netlogon service was set to manual and not running. Once I enabled it for a test computer, spiceworks scanned with no issue. This was just the issue I found. Going to deploy the agent instead to avoid anymore issues.