cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bobsensor
Engaged Sweeper
Currently, we have Lansweeper scanning our domain (we have Premium Version) and all is well, there. Now, we are trying to scan the remainder of the computers that are not in our domain and are part of their own separate workgroups.


these computers are in a workgroup called Tm and given them (each) a new administrative account in addition to the default. I followed the KB posting to scan workgroups and it is not working. The domain credentials screen has the following:

Domain: Tm
user: .\ls

IP scanning range is the same as the domain

firewalls are disabled

I can acces the workgroup computer from my computer w/ net use, so credentials are correct

Here is what I get in the error log file:

2010-08-17 10:53:14: Cannot convert netbiosdomain TM The specified domain canot be contacted or does not exist.
2010-08-17 10:53:16: Cannot convert netbiosdomain TM The specified domain canot be contacted or does not exist.

2010-08-17 10:53:16: TM\SALLEPAUSE$ Active directory computer lookup Erreur unknown (0x80005000)


What am I missing or doing wrong?

tahnk you
bob
9 REPLIES 9
bobsensor
Engaged Sweeper
I'm using lsclient
Hemoco
Lansweeper Alumni
bobsensor wrote:
I'm using lsclient

Lsclient doesn't do any actual scanning, it just informs the server "I'm here, please scan me"
Hemoco
Lansweeper Alumni
The problem with workgroups is that you can't control them by group policies to fix all settings.
bobsensor
Engaged Sweeper
I pinned out the correct modification:

Network Access: Sharing security model for local accounts - Set to Classic


and voila!... any reason for this?

bob
bobsensor wrote:
I pinned out the correct modification:

Network Access: Sharing security model for local accounts - Set to Classic


and voila!... any reason for this?

bob



I'm having the same problem w/ xp home computers. But in xp home you cannot change the security settings "Network Access: Sharing security model for local accounts - Set to Classic". So I'm gessing that it is impossible to use lansweeper to scan a xp home computers?

thank you
bob
Hemoco
Lansweeper Alumni
bobsensor wrote:
bobsensor wrote:
I pinned out the correct modification:

Network Access: Sharing security model for local accounts - Set to Classic


and voila!... any reason for this?

bob



I'm having the same problem w/ xp home computers. But in xp home you cannot change the security settings "Network Access: Sharing security model for local accounts - Set to Classic". So I'm gessing that it is impossible to use lansweeper to scan a xp home computers?

thank you
bob


You can't remotely scan windows home computers with Lansweeper (or with any other scanning tool that uses WMI)
bobsensor
Engaged Sweeper
I have made these changes as per "BendItLikeBednar " post and it worked.
But I don't wish to do this on my 50 workstations and not knowing why I need to do this?... please help

Made the below changes to my secpol and everything started working:

1. Start -> Control Panel -> Administrative Tools -> Local Security Policy
2. Navigate to Security\Local Policies\Security Options
a. Network Access: Let everyone permissions apply to anonymous users - Set to Enabled
c. DCOM: Machine Access Restrictions - Add Anonymous, Everyone, Interactive, Network, System with full rights options set.
d. Network Access: Let everyone permissions apply to anonymous users - Set to Enabled
e. Network Access: Sharing security model for local accounts - Set to Classic

I'm thinking 2c or 2e. was the problem, but I'm not sure...


bobsensor
Engaged Sweeper
No, I get these errors:

Wmierror Access is denied 0x80070005 (192.168.4.102) 2010-08-17 14:10:14
Wmierror Cannot connect to DCOM port 135 : Firewalled? (PCB073) 2010-08-17 14:10:14
Hemoco
Lansweeper Alumni
bobsensor wrote:

2010-08-17 10:53:14: Cannot convert netbiosdomain TM The specified domain canot be contacted or does not exist.
2010-08-17 10:53:16: Cannot convert netbiosdomain TM The specified domain canot be contacted or does not exist.

2010-08-17 10:53:16: TM\SALLEPAUSE$ Active directory computer lookup Erreur unknown (0x80005000)

You can safely ignore these errors.
Do you get a result from the scan or an error?