May 23, 2018 at 11:47 pm
hi everyone,
i try to connect two microsoft sql server management studio 2016(on Laptop) in LAN but not connect.
please send the properties to enable to connect two microsoft sql server management studio in LAN.
my server name -BKA-PCS-905207\SQLEXPRESS
destination server name - BKA-PCS-TEST\SQLEXPRESS
best regards
santosh ghogare
Best Regards
Santosh Ghogare
May 24, 2018 at 2:14 am
Management Studio is an application; you're trying to connect to Microsoft SQL Server; it's an important distinction you need to learn (You don't call the World Wide Web "FireFox" or "Safari" do you? 🙂 ).
I'm not a fan of clicking attachments I'm afraid; especially from very new users when on my work PC. You'll be better putting the image directly into your post.
What is the error you're getting when you try to connect? Are you able to connect the the instances from the server locally? If so, that implies that it's likely a firewall issue or perhaps named pipes isn't on. What are you using as the server name when trying to connect? Is the instance running on the default Port (and if you, are you supplying the port)? If you can't connect locally, sounds like the service isn't running; i suggest you start it. 🙂
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 24, 2018 at 8:54 am
santoshghogare2008 - Wednesday, May 23, 2018 11:47 PMhi everyone,
i try to connect two microsoft sql server management studio 2016(on Laptop) in LAN but not connect.
please send the properties to enable to connect two microsoft sql server management studio in LAN.my server name -BKA-PCS-905207\SQLEXPRESS
destination server name - BKA-PCS-TEST\SQLEXPRESSbest regards
santosh ghogare
Are you doing this at work or at home? If at work, you might need permission to even set up such a scenario, which might very well violate company security rules. If you're doing this at home, you have to be sure you've enabled the Named Pipes protocol and the TCP/IP protocol in the SQL Server Configuration Manager. Then you'll want to be sure the SQL Server Service has started.
Additionally, you need to be sure that your local firewall is either turned off or allows port 1433 to be open, or if you configured SQL Server to use some other port, that said other port is open. If you intend to connect in both directions, then do this on both machines. If you only intend to connect in one direction, then do this on the machine you intend to connect to. Just remember that turning off your firewall has serious risks associated with it, unless your LAN is at home and is NOT connected to the internet.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
May 24, 2018 at 10:14 am
As mentioned above, you need to understand what's happening.
SSMS is a client app. The SQL Server itself will have a name like those you've given. Note that you have a machine name (the Windows host name) and the instance name (SQLExpress). Both of those need to be put in the SSMS connection dialog to connect to the other machine.
The machine you're on doesn't matter. However, if you're connecting to a different windows host, as Steve mentioned, there are a lot of networking things to check. Does the other machine and instance allow remote connections? Is the network protocol enabled? Often local Express instances used named pipes. That can work across machines, but isn't usually used. TCP/IP is, but you need to enable it.
These days you also may need to open the firewall. TCP 1433 is used
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply