This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
We’re currently experiencing a high volume of support requests, which may result in longer response times — Thank you for your patience and understanding.
Community FAQ
Register | Log In
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- Archive
- Scanning of computers on another domain fails
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Register to ask a question, start a topic or share an idea
Join the Community
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2009 01:24 PM
hello,
My problem is that i get rpc 135 error after lsclient is ran on another domain. Connection tester works if i specify alternative credentials. I have added the current domain credentials to premium feature configuration, but an i missing something? I have tried this on several computers / servers with same result. Computers in my domain (lansweeper installation domain) works correctly.
thanks!
My problem is that i get rpc 135 error after lsclient is ran on another domain. Connection tester works if i specify alternative credentials. I have added the current domain credentials to premium feature configuration, but an i missing something? I have tried this on several computers / servers with same result. Computers in my domain (lansweeper installation domain) works correctly.
thanks!
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2009 11:20 AM
Could you try the connection tester to the computername only (not the fqdn)
Do you scan these clients with active scanning or lsclient?
Note that alternate credentials requires the premium version.
Do you scan these clients with active scanning or lsclient?
Note that alternate credentials requires the premium version.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2009 04:23 PM
Could you post screenshots of your exact errors + output of the connectiontester.
Might be a dns resolution problem.
Might be a dns resolution problem.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2009 10:07 AM
Lansweeper wrote:
Could you post screenshots of your exact errors + output of the connectiontester.
Might be a dns resolution problem.
I'd say it's authentication error, since i can connect with connector. here you go:
http://img268.imageshack.us/img268/1406/capture1fyh.jpg
http://img66.imageshack.us/img66/7553/capture2f.jpg
I must say that i run the testing with fqdn name of computer. These domains has no trusts between, but just conditional forwarding on dns.
Archive
This board contains archived posts from the retired Lansweeper Forum and Insiders Community.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now
Related Content
