Hi,

Did you restart the SQL Service after these changes?

Under the SQL Server Network Configuration section of SQL Server Configuration Manager, is TCP/IP enabled?

Have you enabled named pipes? (and restarted service after this)

Hi @Stabz about your information:
The Database server is in another VLAN, rules are ok on the firewall.

The network gateway for Veeam server and MSSQL is the same firewall ?

Hey @MicoolPaul 
Yes I forgot to mention it but yes I have enabled both.
 

I restarted the SQL service as well at every modification.

In addition, I created an udl file and the connection works properly with “Use Windows Nt” 

 
If I try to use the other option with my service account the connection Failed
 

Yes.
I tested the port from my Veeam server and the test succeeded
 

Can you resolve via DNS the server name from your Veeam server?  If not you might need a host entry for this.

Ok @Stabz after your last info about login error, I think service account is not on security login.

Ok @Stabz after your last info about login error, I think service account is not on security login.

 

 

Further to this I would try to set up a SQL Login account and then at the DB connection screen you showed don’t use Windows authentication but rather SQL Native with the credentials.

My personal account and service account are here

I ll try with a SQL Native credential.

No problem with the DNS, the servers are in the same Domain and the resolution works properly

My personal account and service account are here

I ll try with a SQL Native credential.

Do you have check if “svc_veeam” are dbo and dbsysadmin ?

Yep…
 

​​​

Hi @Stabz just to confirm, the SQL Server browser service is running yes? And can you show me the protocol tab on the TCP/IP configuration section.

Thanks

Yes the Browser service is running, but in the Veeam Install when I put the server the browse tab show nothing... 
 

Try checking this article for solutions as a SQL Engineer from MS replied - SQLSTATE = 08S02, SMux Provider Physical connection is not usable | Microsoft Learn

Hi,

That’s correct the browser won’t find it because it’s not in the same L2 network, but if you use SSMS from another server within the same subnet as the SQL server, does it appear? does the name appear as expected?

Oh ok! I learned something. Unfortunately I have only my Database Server in this Vlan

I have test to connect with a native SQL user but got this message

I ll try to install a new sql in the same vlan of my Veeam for test

Hi,

 

That’s correct the browser won’t find it because it’s not in the same L2 network, but if you use SSMS from another server within the same subnet as the SQL server, does it appear? does the name appear as expected?

Oh ok! I learned something. Unfortunately I have only my Database Server in this Vlan

I have test to connect with a native SQL user but got this message

I ll try to install a new sql in the same vlan of my Veeam for test

Try installing SSMS on the SQL Server itself and see if the browser discovers Veeam and then try another server in the network and see if it still appears as that will rule out any firewall/networking on the server itself, even if there are other network issues elsewhere it rules out the SQL Server endpoint being the issue.

Just an observation! If you wish to use the default port, please leave the tcp dynamic port blank. The sql server browser service is only required when using dynamic port! Therefore, some of the concerns on the IP Address properties need to be addressed.

I can see you have the listen all set to Yes! In this case, only the IPALL section is relevant and individual IPn sections will be ignored. 

Hi,

 

That’s correct the browser won’t find it because it’s not in the same L2 network, but if you use SSMS from another server within the same subnet as the SQL server, does it appear? does the name appear as expected?

Oh ok! I learned something. Unfortunately I have only my Database Server in this Vlan

I have test to connect with a native SQL user but got this message

I ll try to install a new sql in the same vlan of my Veeam for test

Perhaps, the services are not running. This is a typical error message for this as I found in my case. You can use the services manager or this Powershell “Get-Service | Where {$_.status -eq 'running' -and $_.DisplayName -like "sql server*"}” to determine the status of the services 

I doubt this is the case here! I recommend a cleanup of the TCP/IP properties tab. Also, since you temporarily disabled Windows FW, please inspect the external  Firewall logs as well. Most times human errors can happen!  

Hi,

 

Did you restart the SQL Service after these changes?

Under the SQL Server Network Configuration section of SQL Server Configuration Manager, is TCP/IP enabled?

Have you enabled named pipes? (and restarted service after this)

Hey @MicoolPaul 
Yes I forgot to mention it but yes I have enabled both.
 

I restarted the SQL service as well at every modification.

In addition, I created an udl file and the connection works properly with “Use Windows Nt” 

 
If I try to use the other option with my service account the connection Failed
 

 

try from universal data link to enter Ip, have you tried yet?

check this

A network-related or instance-specific error occurred - SQL Server | Microsoft Learn

SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified - Microsoft Community Hub

Every time client makes a connection to SQL Server named instance, we will send a SSRP UDP packet to the server machine UDP port 1434. We need this step to know configuration information of the SQL instance, e.g., protocols enabled, TCP port, pipe name etc. Without these information, client does know how to connect the server and it fails with this specified error message."

Hey hey guys! thank you for your involvement ! 

Yesterday night I tried to install a SQL Server in the same network as my Veeam and tadam it works without problem … ! 

So the problem come from the Network for sure after all the tests. So this morning I call my Network engineer, to find the cause, after a quick look the rules are ok to allow the traffic. In the logs we have the match of the connection.
 

But ! On the rule there is IDS Security Inspection enabled ! And this inspection block a packet !

It’s a false positive, so we changed the inspection to IDS until to create an exception, since the connection between my Veeam and SQL works properly ! 

After all my tests I m reinstalling a new SQL Server from scratch to have a proper install. @Iams3le  as you mentioned I always let the settings by default but for my tests I decided to force the port !

Thank again for your time and advices ! 

Hey hey guys! thank you for your involvement ! 

Yesterday night I tried to install a SQL Server in the same network as my Veeam and tadam it works without problem … ! 

So the problem come from the Network for sure after all the tests. So this morning I call my Network engineer, to find the cause, after a quick look the rules are ok to allow the traffic. In the logs we have the match of the connection.
 

But ! On the rule there is IDS Security Inspection enabled ! And this inspection block a packet !

It’s a false positive, so we changed the inspection to IDS until to create an exception, since the connection between my Veeam and SQL works properly ! 

After all my tests I m reinstalling a new SQL Server from scratch to have a proper install. @Iams3le  as you mentioned I always let the settings by default but for my tests I decided to force the port !

Thank again for your time and advices ! 

You are welcome! ... I am glad you got this sorted out and do not forget to resolve the best or closest answer to your issue -:)

Good troubleshooting thread everyone! 

Great to hear you resolved the issue and posted the solution here. This was a fun thread for troubleshooting and coming to the answer which was IDS.  Who knew. 

@Stabz then firewall !