
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-15-2018 12:27 PM
Hello,
For some obscure reasons my dba team decided to change the default listening port of our Lansweeper's database.
Of course, only this new port is allowed on the firewall between the future scanning servers and the main Lansweeper's database server.
When running the Lansweeper setup wizard on my first remote scanning server, I spent some times looking for the right SQL connection string to fill the fields of the "Lansweeper Database Configuration" window.
I finally succeeded with this convention :
It should be a comma instead of a colon before the port!!
BTW, I did not specify the instance name as it is unnecessary when you specify the listening port.
Hope this post will help others facing the same issue.
Sylvie
For some obscure reasons my dba team decided to change the default listening port of our Lansweeper's database.

Of course, only this new port is allowed on the firewall between the future scanning servers and the main Lansweeper's database server.
When running the Lansweeper setup wizard on my first remote scanning server, I spent some times looking for the right SQL connection string to fill the fields of the "Lansweeper Database Configuration" window.
I finally succeeded with this convention :
<database IP address>,<port>
It should be a comma instead of a colon before the port!!
BTW, I did not specify the instance name as it is unnecessary when you specify the listening port.
Hope this post will help others facing the same issue.
Sylvie
Labels:
- Labels:
-
General Discussion
0 REPLIES 0
