July 6, 2008 at 10:35 pm
Hi all,
I m trying to get connected to SQL Server remotely from my machine. I've tried all the steps specified in forums and other questionaires, but still i m not able to get connected to the same. I've rectified all the points such connection strings, named pipes, enabling of remote connection etc.
but still i m getting following error. Please help me resolving the same.
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: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)
July 7, 2008 at 6:20 am
[font="Verdana"]Hi,
I hope the problem is with connection string, can you post the exact connection string you are using in application or the servername you are using in management studio to conenct.[/font]
Regards..Vidhya Sagar
SQL-Articles
July 8, 2008 at 3:54 am
Have you checked that your SQL Server browser service is running? Ensure that this is in auto start and that it is not stopped.
July 8, 2008 at 6:55 am
If you are connecting through Sql Sever Mgmt Studio, make sure that you put the port number after the IP address. (i.e. xxx.xxx.xx.xx:1433) 1433 typically is the open port, but I usually change mine. If you change it (port #) on your router, then make sure you change it in SQL server. Also make sure that SSMS is using Mixed Mode authentication, not just Windows.
Hope this helps
July 8, 2008 at 7:10 am
You have to do some diagnostics and post results unless you want to just get guessing answers.
on the db server in command prompt do:
telnet localhost 1433
do you get connected, or a "Could not open connection to the host" error?
then on your workstation do:
telnet --servername--1433
get connected?
you can also do a "netstat -a" and look for
TCP servername:ms-sql-s ... LISTENING
July 9, 2008 at 6:38 am
Most unusual - got the same identical error this morning using SSMS. Unusual in that last night about 10 PM all was fine. Decided to shut down my desktop an do a cold boot. And dear old Microsoft displayed the message that my computer was being automatically updated with 5 security updates - yes on the desk top I do subscribe to auto updates.
Let the machine shut itself down and then powered it back up, immediately ran SSMS and surprise no problems... seems that one of the updates was to the named-pipes dll to close some sort of security gap.
July 9, 2008 at 7:44 am
Are you trying to connect to SQL 2000 or SQL 2005
Did you try:
From SQL Server Mana Studio, when you click to connect-> click Options and Network Protocols-> Named Pipes.. Check if this works.
else.. Start-> RUN-> cliconfg then disable all Protocols in the right side of the SQL Server Client Network Utility window. then APPLY.
Again First Enable Named Pipes then TCP/IP.. Goto Alias TAB click on ADD, under named Pipes check Just add the SERVERNAME you are trying to conenct and click ok to com out of the window.
Try to connect through SSMS.
Maninder
www.dbanation.com
July 9, 2008 at 10:30 am
Are there any firewall or networking issues that might be causing this failure?
July 21, 2008 at 12:17 am
thanks you are absolutely right
really appreciated
thank you very much
it worked
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply