1

I have Spiceworks set to scan my domain, but it only seems to pick up one domain controller. I have set a domain admin account to be used and specified the domain in scan settings.

I have run a scan using IP ranges and all machines are picked up that way. But I have two domains on the same subnet and get loads of scan errors owing to failed authentication on machines from the other domain.

So I want to be able to have multiple scans, one for each domain. But this doesn’t seem to work. I can’t see anything that I’m doing wrong, so would be grateful if anyone who has a domain scan working could shed any light on it?

3 Spice ups
2

@ But I have two domains on the same subnet - Do you have overlapping IP address between domains or domain x is 1-50 and domain Y is 51-100 ?

3

this is a little tricky to set up but i beleve the best way to do it is make the following scan ranges

192.168.1.1-254 with domain1\admin

then make a second scan range with

192.168.1.2-254 with domain2\admin

so make one of the scan ranges scan everything minus 1 IP

or maybe setting up a trust between the 2 domains.

i hope you understand what i am saying.

4

W Bold wrote:

this is a little tricky to set up but i beleve the best way to do it is make the following scan ranges

192.168.1.1-254 with domain1\admin

then make a second scan range with

192.168.1.2-254 with domain2\admin

so make one of the scan ranges scan everything minus 1 IP

or maybe setting up a trust between the 2 domains.

i hope you understand what i am saying.

This is good suggestion but priorities between scan ranges may cause him to end up with scan errors. It will be best to use two subnets or different ranges.

5

I would use Collecting Remote Office Inventory using Multiple Spiceworks …

Your main installation for the domain x and the remote collector for domain y - OR -

main istallation for all but scanning and two remote collectors, each for scanning one domain.

6

Thanks for all the suggestions. For various reasons we have the 2 domains on the same subnet serviced by a single DHCP server. So separating the network into multiple subnets is not an option for us.

The main issue though, is that under scan settings it is impliedyou can specifiy a domain to scan, i.e. put in the domain name to scan the entire domain. If we leave out the second domain issue for now, the problem I have is that entering the domain does not get the scan to discover all devices on the domain, it only returns one domain controller as being found.

Am I correct then in assuming that a domain scan does not actually scan the domain? And that in order to discover anything on the domain I have to scan by IP range instead?

7

Hi

I am having exactly the same problem. The domain scan just returns the domain controller! Does anybody have any idea why this is or whether this is by design?

Thanks

Matt

2 Spice ups
8

I’m experiencing the same as gpc1501 and Matt…

2 Spice ups
9

Same issue here with the latest version… what was done to resolve this issue?

10

Any suggestions for this? I am currently running into this issue. What’s even more odd is that it was working last week and is no longer working this week.

11

I’ve not found a proper resolution to this yet I’m afraid. For now, I’ve just left the scan to run against the various subnets and when authentication errors occur I specify the alternate domain credentials. It’s a bit messy but it sort of works. It would be really good if the domain scan worked properly though.

12

Same issue for me. Has this been fixed?

I give spiceworks a domain to scan and it only returns the domain controllers…

1 Spice up