
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2009 11:27 AM
Hello!
We have one central domain, and 4 NT domains. Recently we tried to add NT domain computers to the lansweeper system. Assume that central domain is "central.local" NT domain name is "secondary".
with connection tester lansweeper server can ping computer1.secondary and computer1.secondary.central.local (with alternate credentials) but it cannot ping just computer1.
in configuration manager, there is:
active scanning:
Domain DNS name: secondary.central.local
Domain netBios name: secondary
domain credentials:
domain: secondary
username: secondary\user
After I run lsclient on computer 1, lansweeper gives me an error:
Wmierror The RPC server is unavailable 0x800706BA (computer1) 2009.11.16. 11:13:32
Wmierror Cannot connect to DCOM port 135 : Firewalled? (computer1) 2009.11.16. 11:13:32
If I try to run trigger scan - it triggers:
javascript:runApp('\\\\server\\lstools$\\LsTrigger\\lstrigger.exe%20server%20computer1%20secondary','false');
but cannot see computer1, it only can see computer1.secondary.central.local , so how to show the lansweeper to scan computer with full bios name, not just with single computername?
Thank you.
We have one central domain, and 4 NT domains. Recently we tried to add NT domain computers to the lansweeper system. Assume that central domain is "central.local" NT domain name is "secondary".
with connection tester lansweeper server can ping computer1.secondary and computer1.secondary.central.local (with alternate credentials) but it cannot ping just computer1.
in configuration manager, there is:
active scanning:
Domain DNS name: secondary.central.local
Domain netBios name: secondary
domain credentials:
domain: secondary
username: secondary\user
After I run lsclient on computer 1, lansweeper gives me an error:
Wmierror The RPC server is unavailable 0x800706BA (computer1) 2009.11.16. 11:13:32
Wmierror Cannot connect to DCOM port 135 : Firewalled? (computer1) 2009.11.16. 11:13:32
If I try to run trigger scan - it triggers:
javascript:runApp('\\\\server\\lstools$\\LsTrigger\\lstrigger.exe%20server%20computer1%20secondary','false');
but cannot see computer1, it only can see computer1.secondary.central.local , so how to show the lansweeper to scan computer with full bios name, not just with single computername?
Thank you.
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
‎11-16-2009 12:01 PM
For NT domains you can also scan on computername.
To solve this you can forward your dns servers to the ones in the NT4 domain and add "secondary.central.local" as dns search suffix.
See : http://www.lansweeper.com/kb/untrusted.aspx
To solve this you can forward your dns servers to the ones in the NT4 domain and add "secondary.central.local" as dns search suffix.
See : http://www.lansweeper.com/kb/untrusted.aspx
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2009 01:22 PM
Thank you for fast response. Your solution helped.


Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2009 12:01 PM
For NT domains you can also scan on computername.
To solve this you can forward your dns servers to the ones in the NT4 domain and add "secondary.central.local" as dns search suffix.
See : http://www.lansweeper.com/kb/untrusted.aspx
To solve this you can forward your dns servers to the ones in the NT4 domain and add "secondary.central.local" as dns search suffix.
See : http://www.lansweeper.com/kb/untrusted.aspx
