Cannot install second LS-Service

[entiusr]

At my company we have to scan multiple domains with LanSweeper, but i am having some problems during installation in the test environment.

In the testenvironment I have 3 subnets:


In subnet 1 we have:
One MS-Windows Server 2008 Std x64 with MS-SQL 2008 Express
One MS-Windows Client with Report Builder

In subnet 2 we have
One MS-Windows Server 2008 Std x64 with LanSweeper Service, this service works and can connect to the database

In subnet 3 we also want to install de LanSweeper Server, the same way as in subnet 2, but during installation I get an error:

We checked the settings of the database and the settings comply to the documentation, between de subnets are no firewalls.

We made a networkscan during installation (with wireshark at LS-service en SQL-server sides) and the new client wants to connect with port 1433, while the documentation says it has to be 1938 ( we checked this with the working installation. )

Please advise how to solve this.

[Hemoco]

Please contact us by e-mail about this problem : lansweeper@hemoco.com

[Hemoco]

When you connect to the server do you use integrated authentication or username/password.

[Dominic]

Lansweeper wrote:
When you connect to the server do you use integrated authentication or username/password.

We don't use integrated authentication.
We've put the SQL-Server in Mixed-mode and created an SQL-Useraccount/Password.

[Hemoco]

1) The port you are refering to is a dynamic port, you don't need to connect to it directly.
2) Sql should still be listening on the default port (1433)

To connect to it you must be sure that the "sql browser service" is running.

Can you manually telnet to the server to port 1433 ?

[Dominic]

Lansweeper wrote:
1) The port you are refering to is a dynamic port, you don't need to connect to it directly.
2) Sql should still be listening on the default port (1433)

To connect to it you must be sure that the "sql browser service" is running.

Can you manually telnet to the server to port 1433 ?

The SQL-server is listening on the default ports. But 1433 is NEVER available trough telnet. We cheched this with our previous SQL-Cluster in the Production environment. Connecting by using the ODBC (Administrative Tools) was working correctly when we filled in 1938 in stead of dynamicly. When used Dynamicly the server is unable to make a connection.

[entiusr]

I have added a new image with the exact problem, the SQL server is configured according to the manual with port 1938 (manual page 3).

The first LS installation is okay and the second fails.

1. Is the port mentioned in the manual incorrect ?
2. Do we have to change the SQL port back to default?
3. Do we have to reconfigure the first installation?
4. We have to make 4 more installations, do they also connect to te default port?

Kind regardz,

Remy

[Hemoco]

Most likely the now server doesn't know about the changed port and uses the default port.
You can have the new server use the correct port by configuring it with "cliconfg.exe"

[Hemoco]

Normally your SQL server should be running on port 1433.
The installer tries to connect to your sql server.

[entiusr]

Lansweeper wrote:
Normally your SQL server should be running on port 1433.
The installer tries to connect to your sql server.

Then we are a bit confused, because in the manual page 3, the port is changed to 1938.

We made the change to port 1938 and the first installation did work.

Is this coincidence, or did we make a mistake ?