
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2010 04:32 PM
Hi,
Just installed fresh copy of Lansweeper 3.5.2.16
Enabled Active Scanning but no computers shows up.
errorlog.txt contains only two lines:
17.02.2010 15:50:07: Database connection successful, starting up service
17.02.2010 16:05:28: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.
There are no firewalls between Lansweeper server and Domain Controllers.
Service user has Domain Admin rights.
Searched from forum any help, didn't find.
Any ideas are welcome.
Just installed fresh copy of Lansweeper 3.5.2.16
Enabled Active Scanning but no computers shows up.
errorlog.txt contains only two lines:
17.02.2010 15:50:07: Database connection successful, starting up service
17.02.2010 16:05:28: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.
There are no firewalls between Lansweeper server and Domain Controllers.
Service user has Domain Admin rights.
Searched from forum any help, didn't find.
Any ideas are welcome.
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2010 05:22 PM
Please contact us by e-mail lansweeper@hemoco.com to solve this problem.
Please provide screenshots of your config and the errorlog.txt file.
Please provide screenshots of your config and the errorlog.txt file.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2010 04:47 PM
yes and yes
triplechcked
triplechcked

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2010 04:38 PM
1) did you fill the dns domain name in correctly in the configuration tool
2) check if you can resolve the FQDN name of the domain and the domain controllers without any problems.
2) check if you can resolve the FQDN name of the domain and the domain controllers without any problems.
