up vote 2 down vote favorite
share [g+] share [fb]

I want to deploy my Database to a web server but I can't get a connection to the SQL server installed in the web server using management studio 2008. I have already enabled TCP/IP protocol in sql server configuration manager. I also disabled the windows firewall but no result. I always get this error message :

TITLE: Connect to Server

Cannot connect to sql2008.metropol-beauty.com,1430.

ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

Any ideas?

link|improve this question
Is there a hardware firewall in between, if so, is it protocol aware (Watchguard Firewalls are the ones I have run into). If so, sometimes they like to detect a protocol and muck it up (esp. if it is an older version of the firmware, and the software you are using is newer). – jgv999 Aug 28 '11 at 0:33
No there isn't such a thing. I could connect once with the same options but just once I don't know what's wrong. – Milad Aug 28 '11 at 0:59
Can you try with an invalid login? Does it say "Login Failed"? – jgv999 Aug 28 '11 at 1:17
feedback

3 Answers

up vote 2 down vote accepted

You need to ensure that the SQL port which is 1433 is open between the web server and e database server. You also need to ensure that the SQL sever is listening for remote connections. This can be cycled in the SQL Server Configurion Tool.

link|improve this answer
feedback
up vote 0 down vote

Is your server running as a named instance? I have seen something like this before and ended up installing the native client tools on the server and configuring my SQL server up in that. Seemed to resolve my issue, give it ago and see what happens.

http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&id=8824

link|improve this answer
feedback
up vote -6 down vote

Consider trying the default SQL port... 3306. You might strike gold.

link|improve this answer
1430 is the port that the web server is using. I can't change it. – Milad Aug 28 '11 at 1:00
sql2008.metropol-beauty.com:1430 is that a webserver? or is the webserver just metropol-beauty.com:1430? is the sql2008 subdomain on a different IP? Because then the SQL server does not use port 1430. I'm not quite sure on the specifics of your setup. Can you please provide more detail? – U4iK_HaZe Aug 28 '11 at 16:15
7  
3306 is the mysql port, 1433 is the SQL Server port. – mrdenny♦ Aug 28 '11 at 21:09
Hm. On our servers we switched them. I don't know why. I just thought otherwise since we have this setup. But thanks denny, maybe I'll switch mine back. grumbles indistinctly – U4iK_HaZe Aug 29 '11 at 8:33
sql2008.metropol-beauty.com is the SQL Server address which is provided by the hosting company. Anyway I could connect to the server successfully with the same previous configurations. I don't know what was wrong.I think It was the port issue some software was using the port. Is there a program that I can monitor my tcp ports? – Milad Aug 29 '11 at 16:29
show 2 more comments
feedback

Your Answer

 
or
required, but never shown
discard

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