How to allow remote connections to SQL Server Express

[@gass8]

Congrats for your initiative, it's very useful for lot of people especially to foreigners because you speak smoothly to helping people non native english speakers.

[@corrpside20]

3 year and still helps. Thanks for the tutorial and for you time.

[@AndrewCoody]

This was a perfect resolve for my connection issue! I have a Win7 ("server" with 2012) and a WinXP ("client" with 2008) and I was able to figure out on my own how to get 1433-1434 in the firewall listings, to also allow remote access, configure the DB for mix mode, and allow 100 compatibility. But, in all these efforts I could not get past the long logon error message. Searching Google yielded to add sqlbrowser as a firewall rule but that did nothing. Only via your video did I find out the only thing I missed was the custom SQL Server rule. Thank you!!!

[@VoluntaryDBA]

You're welcome!

[@AnthonyGriggs]

You are the Man!! Thanks... I really appreciate the walk through as many articles assume working hardware configuration knowledge. I'm just a developer who is used to developing in already configured environments... I've been setting up some environments myself lately... but a lot of times it's hard as so many who instruct you on these processes assume you are familiar with a lot of it!

[@VictorChavesVVBC]

Got it working, thank you! Tip for other viewers: If you are doing this for the default instance, remember it has no name and you only need to provide the IP adress to connect to it in SQL Management Studio. Do not type MSSQLSERVER, SQLEXPRESS, name of the machine or whatever.

[@VoluntaryDBA]

Victor Chaves Using the machine name should work to connect to a default instance under most circumstances, but you're right, using the IP address (plus the port number if it's non-standard) is always a fallback to connect over TCP/IP.

[@VictorChavesVVBC]

Yes, what I meant to say was to either provide adress or name, never both in case of default instance. I'm saying this because in most tutorials we see someone conecting to a named instance with 192.168.x.y\NAME and by analogy people may try IP\NAME with default instance too.

[@adityaraopandrapagada1894]

@@VoluntaryDBA Instead of going for Sql browser, i have used static tcp/ip (set to 62400) for my named instance and created an inbound rule for tcp/ip with the same port. I have a valid sql user authentication. But when i try to connect using ip,port(i.e.,62400) ,i am getting instance specific error... please walk me through to resolve this issue. Any help from @Victor Villas also appreciated.

[@davidyoo6183]

thank you so much!!! I've been reading articles about opening the firewall rule. but none of them worked. Yours is the first one to suggest the database instance. And it worked!

[@VoluntaryDBA]

You're welcome!

[@zoltanvarnai988]

I have tried many instruction from the WEB, but only yours working for me. Many thanks.

[@Rich-id8kc]

Really nice video. Clear, concise, and provided a simple process to follow to allow networked connections. Thank you for posting this, I really appreciate the time/effort you put into this.

[@jerry77hd]

BRAVO!!!! Well Done... Been battling with this for days then saw your video and it all came clear.... Thank you for everything you do!!!!!

[@turn1210]

I was fiddling about for ages until I saw this. Thank you so much Jon

[@BurmesegirlMay]

I really love to know about DBMS. As a developer , I just knew insert,update,delete,procedur,function , indexer. Its help me a lot to get knowledge overall , I hope you can upload more and more , I subscribed you and really appreciate you. :)

[@jamesyangcq]

Best video tutorial ever; very good quality of video, clear instructions with demo, good job. Hope to see more videos from you. Thanks a lot!

[@VoluntaryDBA]

You're welcome!

[@mikecaldera6360]

Thank you Million Times. Works. You got all the steps with firewall. I missed one step.

[@kantharao88]

Thanks a lot for the amazing video, this is what exactly I needed. Adding firewall to allow specific service is what I missed in my configuration, now it works like charm.

Thank you very much! I tried a bunch of tutorials on this and none worked but this one did! Thank you very, very much! :D

[@ImmacHn]

You have no idea how much this helped, thank you very very much!

[@VoluntaryDBA]

Immac (RockLeet) You're welcome!

[@donharned3226]

I want to thank you very much for taking the time to others such as myself.

[@VoluntaryDBA]

+Don Harned You're welcome. Thanks for watching. :)

[@Paschendale666]

Thank you so much for this video. Forgot I needed the SQL Browser service active to access my named instance.

[@TheRobertralph]

Really great! Thanks for the info. I liked the thoroughness and calm delivery.

[@JEEspinar]

Great job, You helped me a lot with this video, I've searched a lot of videos And I Must tell Your video is the best. Greetings from Ecuador.

[@L98.350]

Just the information I was looking for - Thank you so much!

[@vonslonaker]

Brilliant. Was struggling with this, but you made it so easy. Thanks very much!

[@briankita2044]

Thank you for this guide. Saved me hours of my time.

[@kevintipton4255]

This information helped us out. I'm glad I found this video!

[@ayedabboushi7221]

thank you for a cleared explanation

[@expat2010]

Well done. Clear and concise.

[@fouadbouyounes8885]

Very Informative and exactly what I needed

[@Alires007]

Great Explanation, and Great Tutorial

[@wolftng359]

Thank you for the clear explanation.

[@ilhanbasaran8293]

Thank you so much. This is very clear and easy with this video. It's working.

[@maz3x]

Thank you for your time. Excellent video and excellent demo.

[@jpmcfeely]

Great video, will this work outside of an internal network?

[@VoluntaryDBA]

John Paul Mc Feely Yes, but I don't recommend exposing a database server directly to the "outside" because it's a big security risk.

[@jpmcfeely]

Voluntary DBA What about updating the windows firewall rules to restrict an ip range from other premises, I am ideally looking to have a main database at hq site with connection to each shop through tcp/ip and a failover mirror at each shop, is this a feasible thing to do?

[@VoluntaryDBA]

John Paul Mc Feely If you're talking about Availability Groups, then that's out of my range of expertise; however, I do know there are more ports involved than just the main ones mentioned in this video, so adding other Firewall rules will be necessary. Restricting the incoming IP ranges would be a great start for sure, but I doubt that's sufficient to be completely secure. I would strongly recommend consulting an expert who is in a better position to evaluate your proposed architecture, and also knows how to securely implement Availability Groups... certainly that person isn't me. Sorry.

[@dmitryb.7897]

You saved my ass and my year project .Thank you .

[@jaehochoi8062]

I really appreciate your tutorial. It is super helpful.

[@voqk]

Still valid in 2020 for 2019 SQL Server Express. I had to also enable the SQL Server Browser service to connect from a remote machine. Not sure if that has changed since 2013 or my setup was different for some reason. Just posting here incase you can't connect after following these steps. Double check the SQL Server Browser service is running on (which is on the screen @3:35).

[@munavvarpatel3010]

You saved me bro... really helpful.. thanks man

[@SanamSindhooShaikh]

perfect .. Its so easy .. you made my day .. thanks alot

[@travistorres1739]

Thank you this helped a lot. I've been trying to connect PHP to SQL Express through PDO and kept receiving a Named Instance Error. Enabling SQL Server Browser did the trick!!! Thanks again

[@kimlanbu]

it worked :D thank you very much, i was struggling for days !

[@elevatenyc]

Hi, thanks for the video. when you createdconmevtion did you already have user e in database ?

[@sunesen88]

This video really helped me out! thank you so much!

[@sugelanandh6982]

Nice Help for Network Access Configuration...

[@Easywords-q9y]

Hello , i want to know if this method can connect two computers on the same lan thanks alot

[@firealemgebremichael360]

thanks! plain and simple. works fine

[@ilvaporizzatore]

You made my day. Thanks.

[@avinashshetty2618]

You are Brilliant Sir!!!

[@timonappleton2171]

thank you, work like a charm

[@paulobortolucci1]

Perfect video!!! Question...I have a laptop in the intranet connecting perfectly to the SQL server, but when connecting through a VPN I get 'unable to connect to the SQL server' and I can't find why! I set up a port forward for the port and no sucess!

[@giripriyatama972]

thanks bro, you save my first work..thanks so much

[@mohamedjhasim]

can you help me to connect the database with external network (ie. having data base in my office i want that database to be connected at my home)

[@VoluntaryDBA]

+mohamed jhasim I would suggest setting up a virtual private network (VPN) between the two locations -- then the server would appear on the "local" network at your home. Unfortunately, I can't help you with the specifics of how to do that; there should be some good tutorials around if you Google it.

[@grahamwebb5825]

Thank you! Great help!

[@atupelemboya3354]

Great, its worked for me. thanks a lot.

[@นพไกรใจดี]

Thank you, Very much for your kindness

[@ashka1629]

i need to send table in sql server 2008 to another computer now that computer performs some operation and send result to previous computer...is it possible to send and receive the data????

[@VoluntaryDBA]

As ka You could use something like a Linked Server or an SSIS package to transfer the data. Or possibly using one of the forms of Replication if this is for an ongoing process. All of this is way beyond the scope of this video, though, so if you have a specific issue, please ask a question on dba.stackexchange.com and someone will be happy to help you.

[@chaarions6759]

thnks for the vidéo !! When you get connexion between the two sqls server, Is that the change in the first change in the second.??

[@VoluntaryDBA]

chaari ons This method doesn't connect two instances of SQL Server together. What it does is allow a client application (SSMS, IIS, etc.) to connect to a single instance of SQL Server. The configuration changes are done on the server computer. I hope I understood your question correctly; let me know if I misunderstood.

[@chaarions6759]

Voluntary DBA I am sorry for the delay, you understood me very well and thank you for the answer. but can you help me solve my problem I am making a website with ql server as my database manager and i want my website to be connected to an application wich is also developped with sql qerver. thank you very much :)

[@VoluntaryDBA]

chaari ons If you have a specific question about it, I can probably answer, or at least point you in a direction to get an answer. (Please note that I don't know anything about your applications or infrastructure.)

[@chaarions6759]

ok thanks anyway, I am still searching for informations, if i needed your help i will ask ;) thank you very much,it was a pleasure to have this conversation with you.

[@VoluntaryDBA]

chaari ons You're welcome.

[@fatonbeqiri3363]

Hi this video was great and very helpful but can you tell me if can I use this way of connection to connect to the same database from two same apps in two different PCs. Thanks again for the video it was very helpful

[@VoluntaryDBA]

Hi Faton, yes, this technique is about configuring the server to allow incoming connections, so the number of clients could be 1 or it could be 1,000.

[@fatonbeqiri3363]

Thanks for the answer , i have still one last question. Do you prefer connecting these two PCs with a TCP cable it means peer-to-peer connection or via wireless.

[@VoluntaryDBA]

That's a tough question to answer, because I have no idea what your app is designed to do. Generally, wireless is less reliable and more prone to security issues. Enabling connection encryption would be a good idea, especially if you choose to use wireless.

[@logicmindautomation1458]

Hi, thanks for the nice tutorial. I have a problem though. I have my sql server on one computer and trying to connect to it from another computer and it doesn't seem to work. I am trying to connect using VB Script in Tia Portal. Any help would be highly appreciated.

[@hendafe]

Hi, I have tried everything here, but its not working for me! I can connect to the database on the same system using the IP Address but not remotely! Depends on what I try, I see server error 11001, error 6, error 08001. Any link for more help will be great!

[@VoluntaryDBA]

Henry Onovwaka All of those error codes indicate that the client can't reach the server over the network. Are you able to successfully ping the server or see other network resources on the server? If not, there's something going on at the network layer and you'll have to talk to your network admin to resolve it. If yes, is TCP/IP enabled in SQL Server Configuration Manager, and was the instance restarted so that setting takes effect?

[@scientist100]

I followed this and I cannot connect to the SQL Server. This SQL is hosted on a Windows Server 2016 machine thus, I don't know if there are other additional steps for this. I checked the port by using Test-NetConnection with Powershell and it returns true for the opened port. I don't know what else I'm missing; I tried all sorts of things, my instance is a named instance and I already specified the port to be 1433 under IPAll tab when double clicking the TCP/IP Protocol. I have also enabled "Allow remote connections" under the properties of the SQL Server instance. When I logon, it allows to logon on a different port (5 digit number) and it is my understanding that that logon is only for local access which points to 127.0.0.1. The rest says that it is listening on port 1433 for 'any'. I have tried different ways of logging on but still no go. Let me know if you happen to know what else is needed. Thank you.

[@maxfraire8934]

Will this work if the other computer is in a different network with different IP?

[@VoluntaryDBA]

All these instructions do is permit inbound connections to the server machine through the operating system-level firewall. As long as the client machine can reach the server on the same ports across whatever network architecture you've got set up, it should work.

[@maxfraire8934]

Thank you!! This is very helpful

[@bhys570]

Big thanks man , you are the best

[@andreyaraujos]

I did it! Thank you very much!

[@VoluntaryDBA]

Dante Sparda :)

[@kevins70300]

+Voluntary DBA Thank you very much. I followed the workflow, still my issue was not resolved. So turned off the firewall and tried again. Ultimately I found out that on my machine, SQL2014 . for some reason the Sql server browser was disabled. I had to change its start mode to automatic and then I was good to go.

[@shaikmohammedkhasim3024]

Can you prepare video for how to configure alwayson step by step with active directory services

[@PBRStreetGang68]

Thank you, I was struggling to connect 👍

[@MuhammadAdnan-bg6tn]

this is amazing .Thank you very much sir. i have a question, can i connect sql server instance from different network?? like through port forward etc method .

[@VoluntaryDBA]

Definitely! The basic technique in this video shows how to allow access through the *local* firewall hosting the SQL Server instance, which is where most people get stuck. If you can reach the machine over the network and the right ports are forwarded or allowed through, then you should be able to reach the SQL instance.

[@MuhammadAdnan-bg6tn]

I got it . Thank you :)

[@chrisp986]

Thank you so much for this!

[@adchannel7352]

Hi Sir, Do I need to add more user guests to the database? Or do I need any additional configuration with my database? Cause I followed you like above but it doesn't work? Thank you!

[@solarsrilanka]

Thanks a lot. You just saved my day :)

[@Andrew-wi3tv]

Is there any chance of this causing an issue with speed and resources for people that are using the DB Instance on the host itself? I am new to DBA but have to do a lot of it at my new job. Thanks for the video though, very helpful and exactly what I needed.

[@VoluntaryDBA]

Andrew Harrison If you're talking about installing SQL Server on the same host as, for example, IIS, then yes, potentially there can be a conflict of resources which can degrade performance. But there's nothing wrong with doing this if the host can handle both (or more) duties at the same time, and there are ways to allocate resources (particularly RAM) to help reduce the conflict. See this blog post for more on that: voluntarydba.com/post/2013/03/19/Is-my-SQL-Servers-memory-over-committed.aspx What you'd want to do is record metrics on how healthy the server is in terms of resource usage and headroom, and then adjust your strategy accordingly. In my experience this kind of setup is usually done to save costs associated with licencing a separate server when the app just doesn't need a lot of horsepower. It also results in less server infrastructure to manage. Having the two servers on the same host can potentially be a security risk because there are more ways for the same host to be compromised. It also limits independent scalability of the application tiers. There are pros and cons to each method. Hope this helps.

[@abidredlove]

thanks a lot .....it works great for me .....god bless u

[@jng88]

Thank you so much, I tried this and it really helped me. hehe

[@WardaUaE]

hi thank you very much for the amazing video, can you tell me how can I start sql server agent (SQLEXPRESS) ? I uploaded my website in some.com but I'm sill getting error (The network path was not found ) Thanks again

[@VoluntaryDBA]

Warda UAE Assuming the instance is Express edition, SQL Agent cannot be started because that feature is not available in that edition. With regards to your second point, I'm unclear on what the application architecture is -- if you want to provide more details I may be able to help.

[@foxtrot7800]

ty so much, worked great.

[@trevorneil9249]

Marvellous! Thank you!

[@adchannel7352]

Hi sir, I want to ask if port 1434 is the default with all computers? Because when I installed SQL Express Edition 2019 I got port 8391. And one thing is that you make it simple but I find it difficult :(

[@I677000]

Thanx! its awesome i was able to connect my app easily after I did all of this steps

[@VoluntaryDBA]

You're welcome!

[@diegodecoder1598]

Pls i want to ask if you want to set up remote connection do u have to get the sql server express installed on two systems

[@VoluntaryDBA]

diego decoder Installing a database engine instance is only necessary on one system.A remote system can then use SQL Server Management Studio (like I demonstrated), or another application, to connect to the server. It isn't necessary to install a database engine instance on the remote system.

[@KDOERAK]

excellent video!

[@markwilliams9771]

But you mention in the video that to connect using the name of the machine (not the instance), all we need is port 1433. Well, if that port is already open, why can I not connect using just the machine name?

[@VoluntaryDBA]

Hi Mark, Using only the machine name connects to the default (non-named) instance, why is on 1433 by default. Named instances by default are not exposed on 1433, which is why I show setting up a firewall rule on the database engine service, which allows connections in on any port(s) that service opens. If you installed a named instance and created a firewall rule that explicitly allows only 1433 in (instead of the service-based rule as I suggested), you won't be able to connect because the service isn't listening on that port. It's possible to configure a named instance to listen on 1433, but I didn't cover that in the video for the sake of simplicity.

[@RanjeetKumar-kt4zl]

Hi, It's a fine Tutorial to learn but i have some concerned in the case if i want to connect with SQL Authentication, then what can i do for this.

[@VoluntaryDBA]

Ranjeet Kumar Hi Ranjeet, the changes to the firewall are the same for all types of authentication in SQL Server. I only used Windows Authentication in the demo for simplicity.

[@monicaaitouali2265]

thank you for this intention , it is help to solve my problem

[@IsraIbrahim90]

So, using this method, I can make a windows application and let multiple PC's update and retrieve data from the database? Because I need to make a database windows application that can be used on 3-4 PC's

[@VoluntaryDBA]

isSs Ibrahim Correct. These steps allow access to a SQL Server instance from remote computers, without resorting to compromising other security features in Windows (i.e., by disabling Windows Firewall).

[@IsraIbrahim90]

That's awesome! I wouldn't need to install sql server on the other computers that will be using remote access right?

[@VoluntaryDBA]

isSs Ibrahim Exactly; for your purposes, the client computers would not need to install an instance of SQL Server. If your application isn't being written using a Microsoft client technology (such as ADO.NET), the client computers may require a small driver install to be able to connect to SQL Server.

[@IsraIbrahim90]

I will be using c# to build the application, I guess I would need to install .net framework on the devices but that's about it right?

[@VoluntaryDBA]

isSs Ibrahim Yep, if the version of .NET you're targeting isn't installed by default with the O/S, then you'll have to install it; otherwise, all you need are the app binaries. It would probably take you just a few minutes to whip up a test app that connects to the database to make sure everything works as expected.

[@grippnault]

Is this going to allow me to connect to a SQL Server 2014 Express Database via Visual Studio 2013?

[@VoluntaryDBA]

grippnault These steps would allow another computer to be able to connect to a SQL Server instance on your computer. If you're only connecting on the same computer, these steps are unnecessary. I don't remember if Visual Studio 2013 installs a full Express instance or an instance of LocalDB -- if it's the latter, this video does not apply at all.

[@grippnault]

Okay, thank you for responding.

[@robvincenttizon2181]

What if I create a C# app which uses SQL Server database then I want other users in my network to install and use it on their PCs? Can they still fetch data from my database even if I turn off my PC? Newbie here

[@ralph7503]

Hi, I did the same thing you did but my client computer won't connect to the server I have no idea what i am doing wrong I even disabled the firewall completely, can you private message me, Maybe we can skype and figure it out?

[@VoluntaryDBA]

Ralph Could you please tell me more about the scenario? What error are you getting? Are the two computers in a domain? Can you successfully ping the server from the client? Are you using Windows Authentication or SQL Authentication?

[@ralph7503]

Voluntary DBA Hi first of all thank you very much for replying to me so fast, lets start with what I am using in my Environment, my clients use "Microsoft RMS Store Operations" to connect to the SQL Server, previously i have installed SQL server 2005 and it worked perfectly without having to manage any settings but now the database has come to an point where the file group cannot accept more information because of the limitation of 2048MB, the database is 2.8GB and i am surprised it manage to get that far, now i have installed a new Windows server 2008 R2 standard 64x and downloaded SQLexpADV_64.exe and installed it correctly on the server, i managed all the settings in your video precisely the same and i use "SQL Server Authentication" user:SA no PASS to connect to the database, but the real issue starts now, when i go to my clients computer and manage the setting "Data Sources (ODBC)" to make a SQL server connection it refuses to connect regardless of which username i use, when i only select "With windows NT authentication using network login ID" i get to go to the next menu but cannot select the database as i didn't authenticate the "Connect to SQL server to obtain default settings for the additional configuration options" I tried to explain as much as I can but it would be better if i show you through a skype session with viewing screen, if you accept i can PM you my skype name. (All the above are virtual installed on ESXi Host)

[@VoluntaryDBA]

Ralph I'm sorry, I don't mean to be rude, but I honestly don't have time to try to troubleshoot a scenario this complex. I would try to solve this step by step: Start by looking at the networking to make sure there is connectivity -- can you successfully ping back and forth between the servers? Then establish you can connect to SQL Server from the *same* machine. It might be helpful to set up a test SQL login for this, because when you try to connect remotely, using SQL Authentication bypasses issues related to domains and Windows Authentication. Once you can connect remotely using the SQL login, you know the networking and firewall is configured correctly and the test user can be removed. Finally, connect remotely using Windows Authentication. If at any point it doesn't work, you have to solve that before moving on to the next step. I hope this helps.

[@ralph7503]

Voluntary DBA Hi, I completely understand, yes i can ping between machines, on the server with the SQL installed I tried to make a SQL server driver through Data Sources and it still doesn't connect, I tried a test username already, I cannot connect on the SQL server 2005 to SQl server 2008, but from the SQl server 2008 i can connect remotely to SQLserver 2005 does this help in anyway?

[@ralph7503]

Hi Voluntary DBA I manage to get a breakthrough on this, what i did is upgrade the SQL server 2005 to 2008 it was a bit tricky but i managed to make it work and the database file can now grow to 10 GB! but I it would be nice if we can still isolate the issue for clean install of a SQL server 2008 R2.

[@wilfredogr]

Great !!! thanks for sharing

[@Shahed-Al-Mahmud]

Thanks it's helpful

[@vietvo1061]

Why I get the error: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication? Please help me!!!

[@VoluntaryDBA]

Viet Vo The two computers are not in the same Active Directory domain (or they are not domain-joined at all), or you're not using pass-through authentication. This message is a good sign, though, because it means you have configured the firewall correctly!

[@vietvo1061]

Voluntary DBA thanks for replying me.

[@VoluntaryDBA]

Viet Vo You're welcome!

[@akokohjoel9854]

Pls I want to known can this connection be done via internet

[@LokeshSharma-wp5xv]

Thanks for the video. Could you make a video for sql server security - such as logins, principles, roles. How does it work

[@VoluntaryDBA]

Good idea, I'll add it to my list. Thanks.

[@almsys]

This works great on my network (non domain). I did this on a client's network a couple of years ago and it worked great. They just got a new server (MS 2016 Server) and I tried to set this up again. No go. Everything looks right, but I cannot connect to the server's SQL instance through the Management Studio. I completely dropped the firewall and uninstalled the antivirus on the server (thinking I was being blocked somehow), but still will not connect. I thought maybe it was a Windows permissions thing, but I can browse to that server through Windows Explorer and can see files and folders OK. I tried the connect using SQL authority via a logon I set up within SQL Server, but again, it will not connect. In reviewing the settings, the only thing your video did not cover was making sure that the SQL Server Browser was set to Automatic and started. It is started in this case and all of the settings match your video. This brings me back to my gut telling me that I somehow have a permissions thing going on. Any insights? (The workstation from which I am trying to connect has its firewall dropped.)

[@VoluntaryDBA]

Troubleshoot by starting close to SQL and work your way out. Did the service start correctly? Can you connect locally? Can you connect locally using TCP/IP? If you dropped the firewall and that didn't work, I think there's something going on with the local configuration that needs to be fixed first.

[@almsys]

Yes. It works fine locally. All of the settings have been checked at least 4 times. I have set this up quite a few times and this is the first time that I have run into a failure. I'll have to dig into this more in depth tomorrow. Perhaps there are other links on the web that cover this issue.

[@almsys]

I found a different way to do it. It involved setting the TCP/IP to a specific port on the Protocol's "IPALL" TCP Port property. In this case, I used port 49170 and wiped out the TCP Dynamic Ports property. I then set up an inbound firewall setting to the specific port 49170. Finally, I accessed SQL using the IP address of the server followed by a comma and 49170, such as 192.168.125.5,49170 and that worked perfectly. You are probably right that there was something screwy going on with the server's TCP/IP. This seems to bypass that issue.

[@VoluntaryDBA]

Weird. Glad you got it working!

[@adityaraopandrapagada1894]

@@almsys I did the same configuration. Enabled TCP/IP and given a static port and added an inbound rule for the same. And I am unable to connect through IP,Port. In my case connecting through Sql browser is working. Can we connect to sql server named instance using TCP, SQL Browser (Both ways)? Have you enabled Udp port in your case and allowed custom named instance service along with TCP/IP. Any help from @Voluntary DBA also appreciated.

[@bhavanagupta1737]

I have never done the set up part. I'm unable to set up the remote connection, it works fine on my local machine in 'windows Authentication' Mode though. Please correct me if I am wrong; My understanding is if I want to set up a remote connection it will be through 'SQL Server Authentication'. How will I know the which port number to enter ? Different videos say different port number like 1433, 1434, 14708... Your help will be highly appreciated. Thank you in advance.

[@VoluntaryDBA]

Hi Bhavana, make sure you can connect locally using SQL Server Authentication before proceeding with the rest of the steps. Windows Authentication mode can be used, but is more complicated to set up if the server is not domain-joined. To connect remotely, you can either use the port number that SQL Server exposes, or you can specify the instance name in the form: COMPUTERNAME\INSTANCENAME, which will use the SQL Browser service to resolve the port number. My recommendation would be to ensure you can connect locally first, then follow through the steps in the video one by one.

[@ninzanobita]

I have installed sql server 2008, and service pack 3, but I cannot come to the step you show at 3:19. It gives me this i1300.photobucket.com/albums/ag100/thichbanla/Untitledvf_zpsa35563a7.png Can you please help? Thank in advance.

[@VoluntaryDBA]

It doesn't appear that any database engine instances are installed, just the client tools. If there actually is a database engine installed (a permanent instance, not LocalDB), I would try a repair as a first step. Otherwise, I'm not sure what the problem is, sorry. You might try asking a question on dba.stackexchange.com (please add more details about the installation process you used) or contact Microsoft support.

[@ninzanobita]

Thank you very much for pointing out the problem. That makes me realize that sql server was not installed fully though it always show successful installation message.

[@VoluntaryDBA]

Okay, great. I'm glad that was an easy fix. :)

[@swapnilpednekarn]

How can I connect to a named instance using static port instead of dynamic port. Also I am not using windows firewall but a seperate firewall where i have done port forwarding for that port. I have used port 1435 for the same. Please help.

[@VoluntaryDBA]

Okay, a couple points here. First, an instance name gets converted to a port number by the SQL Browser service, so what you're asking doesn't really make sense... but you can configure an instance to use a specific static port number in Configuration Manager using the TCP/IP properties page. Second, regardless of whether you're using an external firewall or not, you need to poke a hole at the operating system level, either using the instructions I've presented here, or by disabling the firewall entirely (not recommended!).

[@cyberacademy3109]

I have connected the same way but not configured. can you please tell me where was the problem

[@ac-devfullstack9709]

Excellent video, but even enabling tcp from windows 10, it didn't work. I have a VPS on Hostinger, with Firewall and open port, and it gives the same error, what could it be?

[@edward3925]

thanks bro really helps me

[@VoluntaryDBA]

You're welcome!

[@hichamafe]

thanks a lot very helpful video

[@karthikj8085]

Thank you this was good :)

[@hkobzz3423]

Great video.. Though I've always opened the TCP port 1433 instead of UDP 1434 and it has always worked using names instances. I'm looking for a video to allow sql connection over the internet, can you make a video for that please.

[@VoluntaryDBA]

H Kobzz Hi, if you try to connect to a named instance locally, it will use Shared Memory first (which effectively bypasses the Browser service) unless you force it to use TCP/IP, in which case it won't connect. To connect remotely, you have to either turn on the Browser service, or know the port number of the instance, or there's something else going on in the network configuration that's impossible for me to know. As for exposing a SQL server directly to the internet, this is rarely a good idea, and I strongly recommend against it. I don't mean to be rude, but if you have to ask how, then you probably shouldn't be going there. To give you some perspective, I would not attempt to set that up myself, because I'm not familiar enough with everything that needs to be done. It's too risky, especially since there are almost always other ways to accomplish whatever it is that needs to be done. I hope that helps.

[@hkobzz3423]

Thanks a lot... Can you recommend an alternate method if I want to connect to a sql server over internet?

[@VoluntaryDBA]

H Kobzz It really depends on what the business goals and requirements are. Generally speaking, though, some kind of web application (either a front end or a web service) in the middle is a good starting point.