How to create a public connection string

Question

My friend and I are developing a web application project. The SQL server is located here in Laos while he is in the Philippines. I tried to create a connection string but it gives me a "system.componentmodel.win32exception:the wait operation timed out".

Below is my connection string:

string con = "Data Source=public ip,1433; Network Library=DBMSSOCN; Initial Catalog=MyDB; TrustServerCertificate=True; User ID=myUser; Password=myPass";

Hoping someone can assist me in this. Thanks in advance.

Jignesh Kumar · Answer

Hi Hold, Please find below link. You can follow steps which given in below link https://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/

Jes Sie · Answer

I got the error below when I try to create a .udl file.

Jignesh Kumar · Answer

Hi Hold, Please Create a file with extension .udl anywhere on the web server, double click the file, it will open a dialog that will allow you to test the connection to the sql server. you select your servername and you database name and test connection once successfult you can go in file and check your connection string details.

Vincent Maverick Durano · Answer

Is your server where you hosted the database really accessible via the IP address you've provided? Have you tested it on your side to see if it works?

Kapil Gaur · Answer

This is how you can write a connection string in your web.config. You can use this easily throughout your application.

Kapil Gaur · Answer

If you are able to connect to your database using the UDL test suggested by Sourav then try increasing the session timeout time by following command. db.Database.CommandTimeout = int.MaxValue; So command Timeout can be any integer value here. Sometimes our query execution takes a lot time so because of that also you get timeout exception. But before all of this try check whether you are able to connect to you database from web using UDL test. Steps to perform udl test are available on below microsoft link. https://blogs.msdn.microsoft.com/farukcelik/2007/12/31/basics-first-udl-test/

Sourav Mukherjee · Answer

Did you try to do a UDL test making sure from web you can connect to SQL Server? Also do you have the appropriate Native Clients installed?