SLQ Server 2008 express edition remote connectivity issue

M.K

unread,

Nov 19, 2009, 10:37:23 PM11/19/09

to

Hi,

Running SQL Server 2k8 Express Edition with Advanced Services on Windows XP
(SP3).

Everything fine is going but unable to connect remotely to SQL Server and
getting the following error message:

A network-related or instance-specific error occurred while establishing a
connection to SQL Server.
The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is configured
to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)

Already allowed remote connections to the server.

Anyone can help please?

Balaji

unread,

Nov 20, 2009, 6:19:18 AM11/20/09

to

Hi,

In SQL Express by default remote connections are disabled. i.e Named Pipes
and TCPIP protocols are disabled. If you have already enabled these
protocols make sure that your SQL Browser service is running because SQL
Express is installed as named instance and uses dynamic port each time it
starts.

Regards,
Balaji

"M.K" <miank...@yahoo.com> wrote in message
news:%23MsZJLZ...@TK2MSFTNGP04.phx.gbl...

M.K

unread,

Nov 20, 2009, 8:36:31 AM11/20/09

to

Already enabled Named Pipes and TCIP and started SQL Browser service as
well.

"Balaji" <tbalaj...@gmail.com> wrote in message
news:elPEMNda...@TK2MSFTNGP04.phx.gbl...

Rick Byham, MSFT

unread,

Nov 20, 2009, 11:36:25 AM11/20/09

to

Firewall? Use firewall.cpl to open the UPP port 1434 for the SQL Server
Browser service.
And open the TCP port used by you instance of SQL Server. This is probably
port 1433, but Express installs using dynamic ports. This is probably only a
problem if you have another instance of SQL Server running on the computer.
--
Rick Byham, MSFT
(Implies no warranty or rights)

"M.K" <miank...@yahoo.com> wrote in message

news:O9m$7ZeaKH...@TK2MSFTNGP02.phx.gbl...

Erland Sommarskog

unread,

Nov 20, 2009, 5:24:32 PM11/20/09

to

M.K (miank...@yahoo.com) writes:
> Already enabled Named Pipes and TCIP and started SQL Browser service as
> well.

You restarted the server after enabling TCP, didn't you?

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

M.K

unread,

Nov 24, 2009, 11:54:32 PM11/24/09

to

Yes I already has restarted the machine after enabling TCP

"Erland Sommarskog" <esq...@sommarskog.se> wrote in message
news:Xns9CC9EE294...@127.0.0.1...

Rick Byham, MSFT

unread,

Nov 25, 2009, 11:26:20 AM11/25/09

to

Still, check the firewall.
However if you've already done that, let's check TCP connections.
On the client, can you PING the server by IP address?
Can you PING the server by name? If not, perhaps your DNS cache is stale.
ipconfig /flushdns will clear it.
On the client what are you using as your tool? Consider installing the
client tools are the client. Try connecting with sqlcmd.exe.
Check the SQL Server error log. It will list the port that SQL Server is
listening on.
Can you connect to the IP address and port, in the format
xxx.xxx.xxx.xxx,port# like 123.123.123.123,1433

--
Rick Byham, MSFT
(Implies no warranty or rights)

"M.K" <miank...@yahoo.com> wrote in message

news:O3jlltYb...@TK2MSFTNGP04.phx.gbl...