Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have installed Sql Server 2008 R2(express edition) on my server and now I want to connect to that server from my client.

But it shows the following error:

cannot connect to SMSERVER\SMTECH

How can I solve this?

share|improve this question
Can you definitely connect to it locally, using the same application that your client is using? – Dan Nov 16 '11 at 11:56
What have you tried so far? Can you connect locally? Have you enabled remote connections? Have you verified the appropriate firewall rules are in place? – MDMarra Nov 16 '11 at 12:03
ya i connect it locally using Sql Management Studio R2 – Kishore Jangid Nov 16 '11 at 12:15
up vote 1 down vote accepted

If you can connect locally but you cannot connect remotely there are a few things that you can try.

Windows Firewall
You might need to make an exception in Windows Firewall on the server to allow for connections. You need to open ports 1433 and 1434 by default. Obviously, this changes if you've changed the default ports.

Enable TCP/IP connections
Open SQL Server Configuration Manager and select your instance from Network Configuration and then enable TCP/IP as illustrated in the image below. Example

Check other firewalls between client and server
If both of those look good, then there is probably something else blocking the ports between the client and the server. Inspect the policies on any ACLs between the two and ensure that the necessary ports are allowed to reach their destination.

share|improve this answer

Due to my experiences with Microsoft SQL Server there are two things that might have to be set up to get SQL Server work with clients:

  1. Firewall on Server Site The newer Microsoft OS (Server and Client) have the Microsoft Firewall preinstalled and activated. So if you didn't open the appropriate Firewall port this would be the problem. There is a article in Microsoft Technet on how to configure the firewall:

  2. Protocol settings for SQL Server If your client program uses a protocol which is not activated for the SQL Server instance, than you also get a connection error. To show the protocols which are activated and to control them use the Microsoft SQL Server Configuration Manager utility. More details on this topic can also be found in Microsoft Technet:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.