This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- General Discussions
- Mulitple Scanning Servers
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
‎01-22-2016 07:17 PM
Currently I have 25 Lan Sweeper scanning servers all connected to the same database on a SQL server; all of which are displayed properly on the Lan Sweeper Website. Upon adding number 26, the 26th server is not displaying.
Have I reached the limit of how many servers can be displayed?
Have I reached the limit of how many servers can be displayed?
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
‎01-28-2016 04:33 PM
We received and answered this question via email as well. Below is a copy of the response we sent via email, for anyone interested.
Your Support Company license has no limit on scanning servers. The 'tab' under Configuration\Scanning Methods for your new scanning server is most likely missing due to a recent change in the default database password used by our latest installer from mysecretpassword0* to Mysecretpassword0*. The password configured on the new (problem) scanning server may be Mysecretpassword0*, while the password configured in SQL Server is mysecretpassword0*
Could you do the following:
- Ensure that the database connection string in Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config (Lansweeper service configuration file) on the problem server matches the database connection string in Program Files (x86)\Lansweeper\Website\web.config (Lansweeper website configuration file) on the server hosting the console. Open the files with Notepad or another text editor, perform a search for connectionString and make sure the connection strings match. (On remote servers you will of course, have to replace "localhost" with the actual name or IP of your database server.) This information can also be found in step 7 of this article.
- Restart the Lansweeper Server service on the problem scanning server.
If the problem still persists we would like to compare the config files from your problem server and working scanning server. Could you please provide us with the following information without making any adjustments to these files:
- Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config file present on a working Lansweeper scanning server.
- Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config file present on a problem Lansweeper scanning server.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2016 04:33 PM
We received and answered this question via email as well. Below is a copy of the response we sent via email, for anyone interested.
Your Support Company license has no limit on scanning servers. The 'tab' under Configuration\Scanning Methods for your new scanning server is most likely missing due to a recent change in the default database password used by our latest installer from mysecretpassword0* to Mysecretpassword0*. The password configured on the new (problem) scanning server may be Mysecretpassword0*, while the password configured in SQL Server is mysecretpassword0*
Could you do the following:
- Ensure that the database connection string in Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config (Lansweeper service configuration file) on the problem server matches the database connection string in Program Files (x86)\Lansweeper\Website\web.config (Lansweeper website configuration file) on the server hosting the console. Open the files with Notepad or another text editor, perform a search for connectionString and make sure the connection strings match. (On remote servers you will of course, have to replace "localhost" with the actual name or IP of your database server.) This information can also be found in step 7 of this article.
- Restart the Lansweeper Server service on the problem scanning server.
If the problem still persists we would like to compare the config files from your problem server and working scanning server. Could you please provide us with the following information without making any adjustments to these files:
- Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config file present on a working Lansweeper scanning server.
- Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config file present on a problem Lansweeper scanning server.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now