cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Wii
Engaged Sweeper
Hi,
I have this scanning situation:

1) scanning domain with domain\user

2) scanning PCs that aren't in domain but in workgroup with .\user2

3) scanning PCs that aren't in domain but in workgroup with .\user3 because user2 is not valid as administrator in "workgroup at point 2" (there isn't a common administrator user between point 2 and 3)

Is there any way to bypass the error "violation of primary key"?

Maybe I can change the db constraints, but I don't think is a good and/or working way

Thanks

6 REPLIES 6
sjohnson
Engaged Sweeper
I'm also confused about this - can I scan WORKGROUP computers (all with same admin username and password) without requiring lsclient.exe? I have the premium version and am trying to use IP scanning right now but it doesn't seem to be working so far.
Hemoco
Lansweeper Alumni
sjohnson wrote:
I'm also confused about this - can I scan WORKGROUP computers (all with same admin username and password) without requiring lsclient.exe? I have the premium version and am trying to use IP scanning right now but it doesn't seem to be working so far.

Yes, but make sure you uncheck "ignore windows"
Wii
Engaged Sweeper
Thanks.
Another small question (sorry..) about this case.

For example, we could have

10.50.0.0-10.50.255.255 domain\username
10.150.0.0-10.150.255.255 workgroup1 .\username2
10.250.0.0-10.250.255.255 workgroup2 .\username3

The ip scanning check all these ranges.

The active scanning scans the first range because it can retrieve the machine list from the domain; for the second and third case, we need to launch lsclient.exe on the PCs, no other way to scan the "out-of-domain" automatically (even if the ip scan scans the range), right?

Regards
Hemoco
Lansweeper Alumni
Wii wrote:
Thanks.
Another small question (sorry..) about this case.

For example, we could have

10.50.0.0-10.50.255.255 domain\username
10.150.0.0-10.150.255.255 workgroup1 .\username2
10.250.0.0-10.250.255.255 workgroup2 .\username3

The ip scanning check all these ranges.

The active scanning scans the first range because it can retrieve the machine list from the domain; for the second and third case, we need to launch lsclient.exe on the PCs, no other way to scan the "out-of-domain" automatically (even if the ip scan scans the range), right?

Regards

You can scan ip range 2 and 3 with Ip scanning but make sure to uncheck "ignore windows" and add alternate credentials for both workgroups
Wii
Engaged Sweeper
Lansweeper wrote:
Wii wrote:
Thanks.
Another small question (sorry..) about this case.

For example, we could have

10.50.0.0-10.50.255.255 domain\username
10.150.0.0-10.150.255.255 workgroup1 .\username2
10.250.0.0-10.250.255.255 workgroup2 .\username3

The ip scanning check all these ranges.

The active scanning scans the first range because it can retrieve the machine list from the domain; for the second and third case, we need to launch lsclient.exe on the PCs, no other way to scan the "out-of-domain" automatically (even if the ip scan scans the range), right?

Regards

You can scan ip range 2 and 3 with Ip scanning but make sure to uncheck "ignore windows" and add alternate credentials for both workgroups


It works! 🙂
Thanks
Hemoco
Lansweeper Alumni
It won't work you will need a common administrator for the workgroup.