Using SSMS, unable to connect to a remote (network) server

Thanks everyone for your help, it's appreciated. I apologize for not replying sooner, it's been a long process attempting to find out what's different when getting error 18452, considering I've read just about every 18452-related-literature. Although I mentioned above that all configuration parameters were identical for Computer A and Computer B, I discovered 1 difference: The Network Profile for Server A was PUBLIC; however, the Network Profile for Server B was PRIVATE. Once I changed the Network Profile to PUBLIC, I was about to remotely connect to Server B via SSMS. Again, I wish to thank everyone for their help.

Let's start with the simple stuff.

Does both Computer A and computer B have the same versions of SQL server running? If so what version of SQL are they?

Are these machines all on the same domain? If not then it is probably a credentials validation issues for a machine not on the domain.

Are you using Windows auth or SQL auth? If Windows auth then does your Windows account have permissions on both the SQL databases running on each computer? If SQL auth then is SQL auth enabled on the SQL servers running on each computer?

The error itself indicates a login error so something about your credentials is incorrect. Domain issues and/or mixed mode auth is the most common issue. Given that computer A and computer B would need to be hosting their own SQL Server instances and each instance may have separate security settings and/or database configurations then being able to connect to one computer but not the other doesn't really provide much insight here.

Getting integrated security to work in a workgroup can be a challenge, and it may be better to use SQL logins.

That said, it usually works it the username and password is the same on both machines. It may also work if you first map disk on the machine where SQL Server is running (since you provide the password this way). But that is a trick of the past that I have not tried with recent versions of Windows.

Hi @Giacomo Raucci ,

SQL Error 18452 indicates that there is an authentication issue with the login credentials you are using to connect to the SQL Server instance on Computer B. Here are a few suggestions you can try:

• Ensure that the SQL Server instance on Computer B is running and accessible over the network. You can use the Ping command to verify if the computer is reachable.
• Verify that the SQL Server instance on Computer B is configured to allow remote connections. You can do this by checking the SQL Server Configuration Manager and ensuring that the TCP/IP protocol is enabled and that the port number is set to 1433.
• If you are using Windows Authentication to connect to the SQL Server instance, ensure that the user account you are logged in with has the necessary permissions to connect remotely to the SQL Server instance on Computer B.
• If you are using SQL Server Authentication to connect to the SQL Server instance, ensure that the SQL Server instance is configured to allow SQL Server Authentication.
• You need go to SQL Server Configuration Manager and verify that the SQL Server and SQL Server Browser services are running.

Best regards,

Seeya

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".