March 22, 2008 at 8:44 am
Hi All,
I am not sure if this is a newbie question or not...
I have this website which allows me to use sql server. I cannot get it to connect to the remote server at all. First I used sms 2005 express, didn't work then i uninstalled it and installed sms 2005 developer edition and let it set all the defaults. I cannot for the life of me get it to connect to the remote server. Now the hosting company can connect to it. I keep 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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
I am running win2k. I also enabled named pipes and tcpip and cannot get connected...Anyone have any idea on this? the hosting company seems stumped.
I have no firewall running, no antivirus and my router is set to defaults no security.
March 22, 2008 at 8:36 pm
First, did you add named pipes to the server? I'm not sure named pipes works through routers. I think it's a networking issue. You can use sp_configure or EM to set the "allow remote connections" to on.
Be sure that the hosting company isn't filtering out 1433, which is the default method to connect.
Are you connecting from the web server or from your machine?
Lastly, please post in the appropriate forum. I moved this to the 2005 forum.
March 22, 2008 at 9:29 pm
Sorry about posting in the wrong area..
I spoke with my isp as well as the hosting company, neither is filtering out 1433.
i'm trying to connect from my pc. I have a website that allows me to use sql server db's and they can connect to it, but i keep getting the same error.
From my pc in the ssm express i have enabled remote connections..as for the sp_configure i really have no idea on how to use it.
I have connected to sql db's on intranets at a company that i used to work for but this kind of remote connection is new to me.
I have 2 pcs, one in the basement which has a router connected to the main modem and my pc ( that is upstairs ) that has a wireless card in it. my pc upstairs is the one i am trying to connect to.
March 24, 2008 at 1:07 am
Please check if the SQL Browser service is running or not?
March 24, 2008 at 2:12 am
Hi,
you need to enable remote connection at your Host server, follow and check the steps listed here http://support.microsoft.com/kb/914277
Hemantgiri S. Goswami | SQL Server Specialist & Consultant
SQL Server Citation[/url] | Follow me on Twitter
March 24, 2008 at 7:53 am
Hi Old, yes the sql server browser is running.
Hemant, I have spoke with hosting company they are allowing remote connections. They changed me over to a new server but that still doesn't work.
March 24, 2008 at 7:53 am
Hi Old, yes the sql server browser is running.
Hemant, I have spoke with hosting company they are allowing remote connections. They changed me over to a new server but that still doesn't work.
March 24, 2008 at 8:12 am
I had the same problem last week. I created a SQL 2005 database server on the same server I was running SQL 2000 on. When I tried to connect from an XP machine, I got the same error you describe. What I found to be my problem was not having File and Printer Sharing as an allowed Firewall exception along with the exceptions for sqlbrowser.exe and sqlserver.exe which I had created.
March 24, 2008 at 8:21 am
Hi Ed,
I don't have any firewall on my pc and file printer sharing is enabled. I also had a friend of mine try connecting the the host server and he gets the same error I do. I have sent a tracert to the hosting company and it times out just before their server.
They have this asp.net enterprise manager web app that i can use to do my database stuff but its very limited, and annoying to use.
March 24, 2008 at 8:21 am
Sorry for the delay, Chris.
Let me try and explain how this works and then maybe you'll see a hole in what's happening.
When you install SQL Server 2005, it runs on TCP/IP by default, port 1433, and allows you to connect with any Windows PC, using the standard ODBC dialogs. You connect using either the IP, the Windows name (+ /instancename if you use instances), or if you are on the console, then using "(local)".
SQL Server Express only allows local connections, meaning from the console of that server, by default, but the other editions should allow remote connections. However you need to check this using another machine. If the hosting company says they can connect from their workstations, not being the console, then that's not the issue.
When you connect with SSMS, SSMS is on your workstation and makes a socket connection to SQL Server, even if SQL Server is on your local machine. So you can't necessarily use SSMS to check settings on the server.
From what you're describing, it sounds like either they're a networking issue, or you are using Named Pipes by default to connect to a remote machine. Try opening the SSMS, typing in the address of the server, then hitting options. Manually choose TCP/IP to connect. See what happens.
alternatively, I'll try from here if you want to email me directly (sjones @ sqlservercentral.com). Set up a new user, or get the hosting company to change the password for a one time connect that you can change or remove after a test.
Steve
March 24, 2008 at 8:29 am
I was not speaking of a firewall on the PC you are using when trying to connect to the remote db. My firewall exceptions needed to be set on the Windows Server 2003 PC that I connect to that houses my SQL 2000 and SQL Server 2005 database servers. You would need to have the hosting server folks verify they have the firewall exceptions added that are needed, unless they have their firewall disabled, which I wouldn't think would be a great idea.
March 24, 2008 at 8:35 am
Ed has a good point. I'd also ask the hosting company if they allow direct, 1433 connections from your local PC to the remote SQL Server. They might not.
March 24, 2008 at 8:39 am
Thats what they told me that i am allowed to connect through 1433. Its getting to the point where i think i may need to get a new hosting company, because in all respect its not supposed to be this difficult. This has been going on since friday.
March 24, 2008 at 8:41 am
:), It certainly shouldn't be.
Willing to do a test if you like. If I mess it up, feel free to post a complaint here where everyone can see it 🙂
March 24, 2008 at 8:44 am
lol..Thanks Steve,
I sent you an email about 10 minutes with all the info you will need.
Again thanks for all the help. It seems as though the hosting company is stumped altogether on this..lol
I sent them 3 tracert's already and it times out outside their server.
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply