for past few days this is making me mad. i have enables tcp/ip connections, have tried diffrent domain logins,enabled mixed mode but still when i try to connect remotely to SQL Server 2005 it give me which is as follows
general network error - check your network documentation
ConnectionOpen (PreLoginHandshake())
kindly help me
I followed the steps outlined in a blog I found to setup SS2005 express for remote connections. Everything appeared to go smooth until I actually tried to logon ;)
I have Sql Server 2005 Express installed on my WinXP PRO machine at home (no domain). I have opened the ports on the firewall, etc.
When I try and login from the SQLCMD command line tool I get a Login Failed error. Here is the connection string that I'm trying to use:
SQLCMD -S **.***.**.*SQLEXPRESS -U Steve -P MyPassword
The error:
Login failed for user 'Steve'.
When I use Management Studio Express on the same machine running Sql Server, it shows the User name: NEVERSTILLSteve
'NEVERSTILL' is the name of my computer.
If I try and use that same username with a remote connection I get the same error.
I have googled for the error and msg code, but nothing fitting my situation is coming up.
Anyone have any ideas for me?
I had made an application which is using SQL Expresss.When I deploy that application on a server where only .Net Framework 2.0 is installed then it gives an error of remote connection.Does that need some prerequisite for SqlExpress or the reason of error is something else.
View 3 Replies View RelatedI am trying to connect to remote sql server 2005, I am using the Full Name of SERVER (computername.domain) and on server , Local and Remote connections are checked under Surface area configuration settings.
i am getting this error:
....... under the default settings SQL Server deos not allow remote connections.
Should I choose TCP/IP and named pipes option????
Thanks,
Fahim.
hello,
im trying to create an ODBC data source from a SQL SERVER 2005 database located in a remoted pc.
Client----------->PC1 : win 2000 sp4, not sql server
Remote server--->PC2 : win 2000 sp4, sql server 2005 express
From the Command Prompt, im typing "ping PC2" successfully.
After, in the ODBC datasource administrator-->System DNS tab, i choose "sql server" as a new data source , and in the server box , i'm typing PC2/SQLEXPRESS.
In the next steps, im typing the user-passwords.
The error :
connection failed
...
[microsoft][odbc sql server driver][named pipes]ConnectionOpen(CreateFile()).
Connection failed:
SQLState: '08001'
..
Client unable to establish connection
What goes wrong?
I follow the same steps locally, and everything is OK.
Sorry for my bad english:cool:
I am unable to connect to a SQL instance on the server from a workstation on the same network.
SQL Express SP1 is installed on the server, and allows mixed authentication. The instance name is <SERVERNAME>SQLEXPRESS.
Both the Database and Browser services are running.
Local and remote connections are enabled under SAC. I also used sp_configure to make the same changes.
All Protocols for SQLEXPRESS have been Enabled using the Configuration Manager.
The firewalls on both machines have been disabled.
Rebooting the server or restarting services after various changes hasn't affected the outcome.
Local connections made directly on the server are always successful using either authentication mode.
SQL Native Client Driver is installed on the workstation.
The workstation user is trusted. However, neither authentication mode is successful.
The connection string from the workstation uses the named instance above and the SQL Native Client driver.
Other services on the server are working and avaialble to the workstation, such as shared folders.
When I attempt a connection from the workstation I receive the following errors:
Connection failed:
SQLState: '08001'
SQL Server Error: -1
[Microsoft][SQL Native Client]SQL Networtk Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Connection failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timeout expired
Connection failed:
SQLState: '08001'
SQL Server Error: -1
[Microsoft][SQL Native Client]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 setting SQL Server does not allow remote connections.
I have tried all of the recommendations I can find here without any luck. What am I missing?
Hi,
I have an ASP.Net web application running in groupnamewebservername. I am trying to connect it to the remote database server groupnamedatabaseservername using the ASPNET user id. The remote database is SQL Server 2005 and the web server has IIS 6.0 installed. My web.config connection entry has username as "groupnamewebservernameaspnet" and I have a database user in remote database server under the login name groupnamewebservername$. When I try to connect, I keep getting the following error:
System.Data.SqlClient.SqlException: Login failed for user 'groupnamewebservernameaspnet'.
Could you please let me know what I am doing wrong here? Thanks.
Regards,
Gayathri.
When I create a new odbc connection to a SQL server 2005 Db I get a failure telling me dat de SQL server does not allow remote connections.
How can I allow the server to allow this.
Any help appreciated
regards
trying to connect to sql server 2005 over the internet. (its a third paty hosting company i'm using)
so i have to connect via tcp/ip using sql server authentication.
my laptop is running vista.
the version of sql server 2005 on my laptopis developer edition with service pack 2.
it worked fine from windows xp and the connection details are valid as it runa fine from .net on the hosting website.
i have added sql serer managemnt studio to the exceptions list in the firewall.
ihave made sure tcpip is enabled in the sql server connection management console.
i have also enabled it in the cliconfg tool
firewall on/off seems to make no difference.
its almost enough to make you turn to oracle and thats saying something considering how long i've been in the microsoft camp...
the error returned is:
Login failed for user 'SQL2005_152092_garethbowen'. (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
------------------------------
Server Name: 'xxxx',1433
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
Hi
i connect to remote Integration Service. i configure server for remote connection( on component services and DCOM config , ... ) .and now i can connect to Integration Service remotely and correctly.
but when i expand Stored Package and then click to expand MSDB this error will hapen:
login failed for user ... .(microsoft sql native client )
please help me
thanks in advance
Hi, all!
I am writing the VDI application to allow backup/restore MS SQL Server 2005. I would want to backup/restore remote servers as well as local. I have local instance of MS SQL 2005 and remote. Local instance has MSSQL2005_ZORG instance name, remote uses default (so it supposed to be MSSQLSERVER).
While connection to those server via SQL Server Management studio i see local server as "ZORGMSSQL2005_ZORG" and remote as "VM2000SRVZ2".
When i try to create VIrtualDeviceSet via CreateEx i pass "MSSQL2005_ZORG" as lpInstanceName parameter and all works fine. But I could't create same device set for remote 'MSSQLSERVER' instance. I passed any combination for that, such as "VM2000SRVZ2MSSQLSERVER", "MSSQLSERVER", "VM2000SRVZ2", "\VM2000SRVZ2MSSQLSERVER" and so on. No luck always get VD_E_INSTANCE_NAME (0x80770007).
Any idea?
--Thanks
Basically I've been using Visual Studio 2005 for a few weeks now moving a Pocket PC project from 2003 to 2005. When I hit the Start Debugging Button every time until today the project would rebuild and deploy to my pocket PC allowing me to debug etc but now I get
The remote connection to the device has been lost.
Please verify the device conection and restart debugging.
I used to get this problem in VS2003 sometimes and just like the numerous posts on different sites that I've looked at the problem eventually goes away and I'm none the wiser. One guy said that he found that if he went to bed the problem was resolved when he came back!
My PDA running Windows 2003 2nd Edition is directly connected to my PC via a USB port. I've rebooted my PC and done a soft reset on the PDA but it didn't help. I'm using ActiveSync 4.1.
Does anyone know how to resolve this problem?
I am having a problem connecting to a remote SQL server 2005 instance. The remote server is for a website hosting account of mine. I can connect to the server from computers other than the problem computer just fine. I cannot connect to the server using any software including SQL Server Management Studio Express, Visual Web Developer, or even when trying to use aspnet_regsql.exe on the problem computer. The request to connect to the remote server never seems to leave my computer. When talking to my hosting service, they replied that they did not receive a request to connect to their server from me. I have shut down Windows Firewall as well as my third-party firewall with no change. The error message that I receive is:
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: 53)
If anyone has any ideas they would be appreciated.
I am using the VB 2005 login controls in a web application together with a wizard created sqlserver 2005 database stored in the application's appData directory. The controls work ok on my local development computer but when I deploy the application to a web hosting server (ASP.Net) I get the following error message when using any of the log-in controls:
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Any suggestions on how to eliminate this error? Thanks for your help.
Ken McLean
I have a software to connect the SQL Server as DB, and it is ok to connect to the SQL Server 2000 on the remote server in our firm, but got errors when doing the connection to the SQL Server 2005. the error messages are:
Error #1:
ADO Error #-2147467259
Description SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Source Microsoft SQL Native Client
Error #2:
ADO Error ##-2147467259
Description An error has occurred while establishing a connection to the server. When connection to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Source Microsoft SQL Native Client
Error #3:
ADO Error ##-2147467259
Description Login timeout expired
Source Microsoft SQL Native Client
I'm using SQL Server 2005 version 9.00.1399.00, not the Express version. Should I update the SQL Server 2005 Network Configuration in SQL Server Configuation Manager? But I don't know what should be set to "Enable" or Disabled". Is any other place need be configured?
Thanks.
This has probably been answered before, but...
I have a local SQL Server 2005 instance running, and I would like to have another user on my network connect to this instance. However, when he tries to connect, he always receives the same error message:
"An error has occured 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: SQL Network Interfaces, error 28: - Server doesnt' support requested protocol)"
So, I checked the properties for the server, and under the connections tab the allow remote connection box is checked.
Any clue where to look next?
Hey all.
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)
I'm having a big problem with a SQL 2K5 cluster (using standard edition). I can get onto the box and connect to the sql server locally fine. However when I try to connect remotely I get errors.
Let's call the two sides of the cluster, CL1 and CL2 and the "virtual server" is CL3. Locally I can connect without any problem at all to the SQL server, but I just can't connect to it from any remote machine.
The server in question is instance name LMS_PRD running on CL3, port 10051. TCP/IP is definitely enabled for local and remote connections (I have checked this in the SQL server surface area configuration). I can connect locally without any problem. Also, locally, if I do,
telnet CL3 10051
it connects fine
From a SQL 2000 box - when I try to connect from sql query analyzer, I get
"Unable to connect to server LMS_PRD Server Msg 17 ... SQL server does not exist or access denied"
Client network utility shows server alias - LMS_PRD, TCP/IP, CL3LMS_PRD,10051
[I can connect to other SQL 2005 servers OK from this same server using this same method]
On this box, when I do telnet CL3 10051 , I get "Connecting to CL3...Could not open a connection to host on port 10051 : Connect failed"
[When I do a similar one for another SQL 2005 box, "telnet U01 10051", it connects fine]
From another SQL 2005 box - when I try to register the server, I get
"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: TCP provider, error 0 - No connection could be made because thew target machine actively refused it.) (Microsoft SQL Server, Error: 10061)"
IN the SQL native client configuration it shows alias name - CL3LMS_PRD, server=CL3LMS_PRD, protocol tcp, parameters 10051
Again if I do telnet CL3 10051, I get the error above.
From this same box I can register another SQL 2005 server without any problem and do the telnet to it OK
Just to emphasise:
(a) The SQL server configuration manager shows that TCP/IP is enabled, and that 10051 is the port (in IPALL, TCP port). Also I have checked the SQL server errorlog - it is definitely using 10051 as the port.
(b) The SQL server surface area configuration shows under local and remote connections using both TCP/IP and named pipes selected (I've tried both this and the using tcp/ip only option)
(c) SQL server browser is running
(d) There are NO firewalls etc involved
Any help or advice MUCH appreciated
Any thoughts anyone?
Hi, I have a SQL Server machine, which has SQL Server 2005 installed in it. I'm able to connect to this server remotely (Remote Desktop Connection)
But when I'm trying to connect this SQL Server using SSMS. I'm getting the following error.
TITLE: Connect to Server
------------------------------
Cannot connect to 10.192.24.253.
------------------------------
ADDITIONAL INFORMATION:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
-Senthil
Hi,
I have written a database application using .mdf in visual studio 2005 using vb.net (Windows XP sp2)
The app runs fine on the local machine. But I want to access the database from another computer (remote connection)
My Questions:
1. How to host the database file (mydb.mdf) on server machine?
2. How does connection string change on the client side?
Any other idea?
THanks!!
Good day.
I am trying to look at a friends database that they have developed. Not having used SQL Server Express before I am experiencing problems trying to remotely connect to their database.
He connects locally just fine of course.
I get the error message about remote connectionsand the default settings so I have enabled TCP/IP and Named Pipes as well as cleared SQLSERVER Express in my firewall settings. I also stopped and restarted the service, but still get the same error message.
My connection parameters are like:
Server type: Database Engine
Server name: http://sql.exampledatabase.net (should http be here? have tried with and without same error)
Authentication: SQL Server Authentication (windows authentication? If so, how do I change to such?)
Login: http://username (should http be here? have tried with and without same error)
Password: password
TITLE: Connect to Server
------------------------------
Cannot connect to http://sql.exampledatabase.net
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: 53)
Any help would be much appreciated.
BurntBack
I need help!
I have Outlook 2007 w/BCM running on XP Pro workstation connecting to a SBS 2003 R2 hosting my SQL 2005 database. I have two problems: First I can get the BCM to connect to the remote data but periodically the connection is lost and many times it requires a reboot to reconnect. Secondly related to teh first, I can never get MS Accounting 2007 to connect to the same server and database from my client.
I have already set up the server to use port 5356 via TCP amd added a hole through my client windows firewall for the same port. Both client and server are set to share files and printers.
Any suggestions?
I'm having a big problem with a SQL 2K5 cluster (using standard edition). I can get onto the box and connect to the sql server locally fine. However when I try to connect remotely I get errors.
Let's call the two sides of the cluster, CL1 and CL2 and the "virtual server" is CL3. Locally I can connect without any problem at all to the SQL server, but I just can't connect to it from any remote machine.
The server in question is instance name LMS_PRD running on CL3, port 10051. TCP/IP is definitely enabled for local and remote connections (I have checked this in the SQL server surface area configuration). I can connect locally without any problem. Also, locally, if I do,
telnet CL3 10051
it connects fine
From a SQL 2000 box - when I try to connect from sql query analyzer, I get
"Unable to connect to server LMS_PRD Server Msg 17 ... SQL server does not exist or access denied"
Client network utility shows server alias - LMS_PRD, TCP/IP, CL3LMS_PRD,10051
[I can connect to other SQL 2005 servers OK from this same server using this same method]
On this box, when I do telnet CL3 10051 , I get "Connecting to CL3...Could not open a connection to host on port 10051 : Connect failed"
[When I do a similar one for another SQL 2005 box, "telnet U01 10051", it connects fine]
From another SQL 2005 box - when I try to register the server, I get
"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: TCP provider, error 0 - No connection could be made because thew target machine actively refused it.) (Microsoft SQL Server, Error: 10061)"
IN the SQL native client configuration it shows alias name - CL3LMS_PRD, server=CL3LMS_PRD, protocol tcp, parameters 10051
Again if I do telnet CL3 10051, I get the error above.
From this same box I can register another SQL 2005 server without any problem and do the telnet to it OK
Just to emphasise:
(a) The SQL server configuration manager shows that TCP/IP is enabled, and that 10051 is the port (in IPALL, TCP port). Also I have checked the SQL server errorlog - it is definitely using 10051 as the port.
(b) The SQL server surface area configuration shows under local and remote connections using both TCP/IP and named pipes selected (I've tried both this and using the tcp/ip only option)
(c) SQL server browser is running
(d) There are NO firewalls etc involved
Any help or advice MUCH appreciated
Sir i am trying to connect sql from my LAN to my networked computers but whenever i tried to register it through Enterprise manager i get following "SQL Server registration failed because of the conection failure displayed below.Do you wish to Register anyway? Login failed for user 'SW17/Guest'
where SW17/ is my another computer name...
i have checked tcp and named pipes
and confirm username for sql authentication too
please help me as i being late submit my project
Help! My web-application worked fine last week. I have made some enhancements and it still works fine when I test in locally in VS 2005 and from IIS when I allow unauthenticated users (by commenting out "<deny users="?"/>" in my web.config. However, with not allowing unauthenticated users, I get redirected to a login application (which also worked last week), where I supply one of several user names and passwords and it is supposed to redirect me back to my default.aspx page. Only, now it is taking the authentication parameters from the login screen but is not redirecting me back to my app's page and instead is putting up this Error 26 that states SQL Server 2005 does not allow remote connections.
The included stack trace has no information about what server it seems to be trying to connect with, but the strangest thing about it is I/we are not using SQL Server 2005 yet (still a future upgrade not too far off). The application database, the authentication aspnetdb database, and the Session aspstate database are all on the same SQL Server 2000 managed server. And, these were all working last week (and are all accessible). I have not changed any connection strings and as I said, it works fine without the loging in part both locally and from IIS. It is only when using the Login in application, which is working with other apps and the developer insists the problem has to in my application (after all the first line of the error message states: Server Error in '/deployment1' Application, which is my app!)
I am lost in finding the culprit, can someone please give me some ideas?
I have Microsoft SQL express server 2005 setup on one server and I have a website setup on another server, I am trying to get some data from the SQL server on the other one.
I am currently getting this error: 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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) I have done plenty of searching on Google, and already been through the tutorial on changing the setting in ‘SQL Server 2005 Surface Area Configuration’ to allow remote connections
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspxhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
It works perfectly when I call data from my local machine.
Also I don’t know if it is a timeout issue, because I tested in on two other servers I have access to and it worked on one of them.
Any help would be very much appreciated.
Thanks in advance.
Hi,
I installed SQL server 2005 express edition on my windows server and I had no problem with connecting it remotely through Management Studio, then I removed it and installed a full edition SQL server 2005. That's when it's gone all wrong.
Now I can't remotely connect the server through Management Studio. The error I get is the same as some of the people in this forum has which is:
"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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"
The problem is that I have all protocols enabled and even when I disable firewall and unassign all the ip filters still no go.
I looked at te machine.config file at my server and the connection string bit goes like this:
<connectionStrings>
<add name="LocalSqlServer" connectionString="data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
</connectionStrings>
Can anybody tell me wether you think the problem lies here where it says SQLEXPRESS where I actually have Sql Server 2005 installed.
I've been in and out of every documentation regarding this but they all tell me to configure the protocols and nothing else which doesn't really help.
I have tried running .Net Sql server wizard on the server but it didn't connect probably for the same reasons why I cant connect remotely.
I would really appreciate any help
Thanks
I am using MSSQL Server 2005 Express Studio and tryig to connetch to the remore server but does not work.
I get this error.
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.
Though I have read like child and made changes according to it.
http://support.microsoft.com/kb/914277
Still says same error.
I am clueless how to do it.
Do any one know web based mssql editor where i can connect mssql?
Thanks in advance.
Hello,
2 weeks ago, I installed a SQL Server 2005 Express on one of my computer. I fought to configure the remote access, but finnaly it did work.
Yesterday I had to move my server on another computer and I've never succeeded in configuring the remote access. I don't understand why it is so complicated to install remote access.
I explain you what I did, and if you could say me what i missed, it could be amazing !!
I install SQL Server 2005 Express including the SQL Server Management Studio Express.
I went to the SQL Server surface area configuration and i enable Remote Access (TCP) and turn on the SQL Browser
I enabled Server authentication => SQL Server and Windows Authentication mode.
I created users with all the permission i can give to them.
I restart one million time all the services and nothing...I tried to connect to the database using my local Microsoft SQL Server Management Studio Express, using the Visual studio Sever Explorer and with C# script using this connection string :
sConnectionString = " Server=myIP\SQLEXPRESS; Initial Catalog='myDatabase'; user id = myLogin; password = myPassword";
And I've never succeeded in connecting, I have always the same error :
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)which means the database is not reached.
Please tell me i've just missed a stupid thing.
Hi!
I have this problem:
When I try to open database table under database explorer in VWD 2005
EE, it says that it failed to attempt connection due to user instance
and the connection will be closed.
When I try to right click on my database's file name under database
explorer and click connection to set the connection setting and click
on "Test Connection", it says the same thing.
This happen sometime, but after I restart my computer, I am able to access my database file again.
Anybody have any idea what's going on?
thanks !
I have a SQL Server 2005 database (called BDHSE) in a PC which i call PC1. I have a second PC (PC2) and both are within a network (a WLAN).
What i want is to have access to BDHSE from an application in VB6 (APP1) running in PC2. All the INSERT, DELETE, UPDATE records process is done through APP1.
APP1 ia currently running in PC1 and is to be installed on PC2.
I have these questions:
1. What do i need to install in PC2 since all the INSERT, DELETE, and UPDATE is done using APP1? I guess i only have to install the Microsoft SQL Native Client (with all the prerequisites of course) but i am not sure.
2. In the APP1 made in VB6, do i have to change the connectionstring since i am accesing the database which physically is at PC1 and the APP1 will be used in PC2?
3. Any advice you can give me on doing this will be well received.
Thanks in advance,
BSc Fernando Martinez
Hi,
I am having problem with remote connection via TCP/IP connection on default port 1433. TCP/IP connection are enabled on the server.
any possible solution ?
See problem below:
TITLE: Connect to Server
------------------------------
Cannot connect to ns1.iandigroupltd.com,1433.
------------------------------
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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Hey all!
I've tried all I know in an effort to get SQL 2005 Express to allow remote connections on my customer's 2K3 server and I'm not having any luck. I've followed MSKB 914277, including adding the exceptions to their Windows firewall...even disabled the firewall altogether (for testing purposes), and I still can't get remote clients to connect. As suggested by various other posts, I used netstat -an to confirm that SQL is listening on port 1433 for the desired IP on the server.....and saw that it is listening. Here's a snippet:
TCP 192.168.0.2:1433 0.0.0.0:0 LISTENING
TCP 192.168.0.2:1433 192.168.0.2:1738 ESTABLISHED
TCP 192.168.0.2:1738 192.168.0.2:1433 ESTABLISHED
TCP 127.0.0.1:1433 0.0.0.0:0 LISTENING
I can connect to the database locally (i.e. on the 2K3 server itself) using just the IP address .... tried with a DSN, UDL, ODBC, and SSMSE...all of which have no problems (as shown by the two, "ESTABLISHED" entries in the netstat results above which were from running SSMSE locally on the server at the time of the netstat). But if a remote computer on the network tries to connect, they cannot connect. Sorry, I don't have a copy of the error message the clients are getting yet.
I asked The customer's IT to confirm that the clients CAN can "see" the server (i.e. that there wasn't some kind of router or firewall blocking their path) and they sent me a copy of the server's pfirewall.log file. Here is an entry from the file that seems to show that client requests ARE getting to the server:
2007-12-17 19:12:13 OPEN-INBOUND TCP 192.168.0.4 192.168.0.2 1213 1433 - - - - - - - - -
2007-12-17 19:12:13 CLOSE TCP 192.168.0.2 192.168.0.4 1433 1213 - - - - - - - - -
I'm starting to get in over my head here (I'm a programmer, not a DBA or Net Admin), but doesn't the above suggest that an incoming request came in from .4 on port 1213 and attempted to connect to .2 on port 1433, but the connection was denied or dropped by the server? If so, why? Is this related to another MS KB I read about connection pooling? I'm way over my head here and could use some help. Did I miss something subtle during configuration of SQL Express?
Thanks in advance.