Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Remote Connection to SQL Server from Management Studio Express Expand / Collapse
Author
Message
Posted Sunday, July 06, 2008 10:35 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, November 12, 2008 4:12 AM
Points: 15, Visits: 56
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)
Post #529038
Posted Monday, July 07, 2008 6:20 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, April 11, 2014 2:47 AM
Points: 416, Visits: 540
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.


Regards..Vidhya Sagar
SQL-Articles
Post #529191
Posted Tuesday, July 08, 2008 3:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 04, 2009 5:51 AM
Points: 1, Visits: 7
Have you checked that your SQL Server browser service is running? Ensure that this is in auto start and that it is not stopped.
Post #529849
Posted Tuesday, July 08, 2008 6:55 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 13, 2009 5:41 PM
Points: 5, Visits: 21
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
Post #529985
Posted Tuesday, July 08, 2008 7:10 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, October 15, 2010 8:23 AM
Points: 371, Visits: 437
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
Post #529994
Posted Wednesday, July 09, 2008 6:38 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:36 PM
Points: 5,470, Visits: 23,487
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.


If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #530710
Posted Wednesday, July 09, 2008 7:44 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Thursday, January 02, 2014 10:30 AM
Points: 646, Visits: 731
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
Post #530806
Posted Wednesday, July 09, 2008 10:30 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, April 15, 2009 12:44 PM
Points: 192, Visits: 50
Are there any firewall or networking issues that might be causing this failure?
Post #531040
Posted Monday, July 21, 2008 12:17 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, November 12, 2008 4:12 AM
Points: 15, Visits: 56
thanks you are absolutely right

really appreciated

thank you very much

it worked
Post #537417
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse