This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
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
- Re: Wrong domain
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-08-2009 06:25 PM
I have reinstalled windows 2003 (standard) recently and lansweeper with it...
The old database has been restored. However when i connect to the server with lsclient, nothing seems to happen.
The server itself has been added to a different domain within lansweeper... so the REAL domain is not updated anymore.
The server is connected to the domain "DOMAIN", but lansweeper sees it as connected to "THESERVER".
When running "net config workstation" in cmd i see i that the machine is connected to "DOMAIN".
When running lsclient manually it sees itself as connected to DOMAIN, so it wont update its own data.
Tried updating to the 3.5.2 beta files but without results. What is going on?
LOG:
-----------------------------------
08-07-2009 16:04:22: Database connection successful, starting up service
08-07-2009 16:04:57: THESERVER <> CLIENT1 DOMAIN: scanning multiple domains requires the premium version
08-07-2009 16:16:04: THESERVER <> THESERVER DOMAIN: scanning multiple domains requires the premium version
The old database has been restored. However when i connect to the server with lsclient, nothing seems to happen.
The server itself has been added to a different domain within lansweeper... so the REAL domain is not updated anymore.
The server is connected to the domain "DOMAIN", but lansweeper sees it as connected to "THESERVER".
When running "net config workstation" in cmd i see i that the machine is connected to "DOMAIN".
When running lsclient manually it sees itself as connected to DOMAIN, so it wont update its own data.
Tried updating to the 3.5.2 beta files but without results. What is going on?
LOG:
-----------------------------------
08-07-2009 16:04:22: Database connection successful, starting up service
08-07-2009 16:04:57: THESERVER <> CLIENT1 DOMAIN: scanning multiple domains requires the premium version
08-07-2009 16:16:04: THESERVER <> THESERVER DOMAIN: scanning multiple domains requires the premium version
Labels:
- Labels:
-
Archive
14 REPLIES 14
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2009 04:21 AM
Lansweeper wrote:
Did you change your lansweeper version?
not sure if it was 3.5 or 3.5.1... What is the release date of 3.5.1? couldn't find it
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2009 12:54 AM
This is a known problem.
(only windows 2000 domains and above are supported)
The problem is that the dotnet function to get the domain returns the wrong domain on samba and NT4 domains.
We might fix this in the next release.
(premium version don't has this problem)
(only windows 2000 domains and above are supported)
The problem is that the dotnet function to get the domain returns the wrong domain on samba and NT4 domains.
We might fix this in the next release.
(premium version don't has this problem)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2009 01:03 AM
Lansweeper wrote:
This is a known problem.
(only windows 2000 domains and above are supported)
The problem is that the dotnet function to get the domain returns the wrong domain on samba and NT4 domains.
We might fix this in the next release.
(premium version don't has this problem)
It is not clear to me why it was not an issue before i reinstalled the server (win2003 std) on which lansweeper is running...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2009 09:36 PM
Which kind on domain is "DOMAIN", is it a windows 2000 or higher domain?
Under which account is the lansweeper service running? Is it a domain account?
Under which account is the lansweeper service running? Is it a domain account?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2009 09:48 PM
Lansweeper wrote:
Which kind on domain is "DOMAIN", is it a windows 2000 or higher domain?
Under which account is the lansweeper service running? Is it a domain account?
It's a samba domain to be precise. The account is member of domain admins (yes it is a domain account).
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
- Whitelisting Lansweeper Cloud by IP Address in Technical Support Solutions
- What is an Unknown asset? in Technical Support Solutions
- Rename Detection - Identify the correct use case in Technical Support Solutions
- How can I track the location of my assets? in Technical Support Solutions
- Wrong user scaning in General Discussions
