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

I am unable to connect the SQL instances without giving port number. Expand / Collapse
Author
Message
Posted Monday, January 20, 2014 11:43 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Sunday, April 13, 2014 1:50 PM
Points: 62, Visits: 214
Hi All,
I am unable to connect the SQL instances without giving port number. I am getting below error.

Please help me on this and let me know why its happend

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)





Post #1532763
Posted Monday, January 20, 2014 11:50 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Sunday, April 13, 2014 1:50 PM
Points: 62, Visits: 214
I got the result ..... i started the browser it started connecting..
Post #1532764
Posted Monday, January 20, 2014 3:51 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 9:45 PM
Points: 36,013, Visits: 30,300
rajeshjaiswalraj (1/20/2014)
I got the result ..... i started the browser it started connecting..


Some would say that's a bad thing. Hackers use the presence of Browser to more easily find servers.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1532805
Posted Tuesday, January 21, 2014 6:38 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, April 11, 2014 1:53 AM
Points: 339, Visits: 211
If you're connecting to SQL 2005, sometimes you get this when you're network admin has blocked UDP 1434 as protection against the SQLSlammer worm.

..and that would happen even if the Browser service is started.

Connecting to SQL2008 and above won't give you this problem, even if UDP 1434 gets blocked. Later versions connect using TCP 1434. But you still need to specify the port if the browser service isn't running





sqlmunkee
Bringing joy and happiness via SQL Server since 1998
Post #1533024
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse