Re: SQL Server 2005 Connectivity

I am using SQL Server 2005 Developer edition and I am successfully connected
from one of Xp box as I mentioned in my post.


"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message
news:28AC1845-377E-4926-B71B-EAB80A8C5FB8@xxxxxxxxxxxxxxxx
Can you tell me what Edition of SQL Server 2005 do you use?

Because in SQL Server 2005 Express Edition and Standard Edition, remote
connections are not allowed by default. So if you are using on of these
Editions then you will need to make appropriate configuration settings
from SQL Server Surface Area Configuration.

--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT



"Noor" <naissani@xxxxxxxxxxx> wrote in message
news:OH5KyTY8HHA.4612@xxxxxxxxxxxxxxxxxxxxxxx
Dear Professional,

I would really appreciate if any one help me out.

I have a Windows 2003 RS Service Pack 2 Server that has SQL Server 2000
installed on Default instance and SQL Server 2005 Named Instance.

I enable all the Protocol, Add the SQLBrowser, SQLServ.exe into Exception
List in Firewall as well as enable remote connectivity.

I connected SQL Server 2005 and SQL Server 2000 from one of
our XP client through SQL Server Management Studio, works perfactly fine.

I have another box that has Windows 2003 installed as well as SQL
Server 2005 client installed when I tried to connect to SQL Server 2000
from
SQL Server Management Studio it works fine but when I tried to connect to
SQL Server 2005, I got the following error.

Cannot connect to ISTCL-VSERVER\ISTCLSQL05.

------------------------------
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server.
When
connecting to SQL Server 2005, this failure may be caused by the fact
that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection
to SQL Server) (Microsoft SQL Server, Error: 1326)


I would really appreciate if any one can guide me, may be when Server to
Server talk we have to enable any thing as Web Server has Windows 2003
installed and Database Server also has Windows 2003 installed?
I also updated the MDAC 2.8 on all the boxes but failed to connect.
Please advice.

Thanks






.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... I've tried to change the user connections to 0, ... "SQL server connection time out. ... The following message appears when restart the server and before login ... I receive Error message: “A connection could not be established to ...
    (microsoft.public.sqlserver.clients)
Loading