
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2010 12:43 AM
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?
The specified domain does not exist or cannot be contacted.
...
The LDAP server is unavailable.
...
Any suggestions on how to fix this?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2010 01:12 PM
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)
Make sure that your dns domain is resolvable: try "ping domain.local" (with the correct dns name)
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2010 10:44 PM
please contact us by e-mail lansweeper@hemoco.com and provide your errorlog.txt file.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2010 05:33 PM
Both are correct with domain.local and domain for netbios

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2010 01:12 PM
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)
Make sure that your dns domain is resolvable: try "ping domain.local" (with the correct dns name)
