cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
chubbard
Engaged Sweeper
We recently migrated to the premium version on a new server from the free version. Before the migration, we had a script running at user logon which triggered a scan. Now with AD scanning 94% of my clients are showing an RPC error. When testing fixes, I've used connection manager, repaired WMI, and removed firewalls as suggested in the knowledge base. I have noticed that I'm getting the following errors in my errorlog.txt:

The specified domain does not exist or cannot be contacted.
...
The LDAP server is unavailable.
...

Any suggestions on how to fix this?
1 ACCEPTED SOLUTION
Hemoco
Lansweeper Alumni
Make sure that your netbios domain and dns domain name are correct.
Make sure that your dns domain is resolvable: try "ping domain.local" (with the correct dns name)

View solution in original post

3 REPLIES 3
Hemoco
Lansweeper Alumni
please contact us by e-mail lansweeper@hemoco.com and provide your errorlog.txt file.
chubbard
Engaged Sweeper
Both are correct with domain.local and domain for netbios
Hemoco
Lansweeper Alumni
Make sure that your netbios domain and dns domain name are correct.
Make sure that your dns domain is resolvable: try "ping domain.local" (with the correct dns name)