Prev: ANN: Database Workbench 4.0.3, the multi-DBMS IDE now available!
Next: Did this ever get resolved?
From: Erland Sommarskog on 15 Jul 2010 04:36
SAFEKOM (u61982(a)uwe) writes:
> What I already done:
> 1) SQL SERVER is up and the instance connect is running.
> 2) All required ports on Firewall is open/ also try to disable Firewall
> but no success.
> 3) TCP/IP protocol is ENABLE. SQL SERVER port is by Default 1433.
> 4) Also try this:
> the probelm is the Instance name from the client is not resolved, to do
> that follow the below shown steps.
> 1. navigate to C:\Windows\System32\drivers\etc
> 2. Open hosts file in notepad
> 3. add the entry at the end of line, as i did for example
> 213.165.131.65 KSSQLSRVR
> 213.165.131.65 KSSQLSRVR\SPDEV01

So are you trying to connect to a default instance or to a named instance?

Named instances, usually run on a port <> 1433, dynamically selected.
For this to work, the SQL Server Browser service must be running, and
UDP port 1434 must be open in the firewall.

Alternatively, you can specify the port when you connect:

SERVERNAME,4711

You can find the actual port number in SQL Server Configuration Manger.

It is not uncommon to disable the Browser service. In this case, it's
better to reconfigure the server in SSCM to use a fixed TCP port.



--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

From: SAFEKOM via SQLMonster.com on 15 Jul 2010 07:57
What i have give in Server name then S15er3226\SQLEXPRESS OR S15er3226,1433
(or another one) OR server IP address,1433(or another one).
let me tell you again i m connecting it over Internet.

Fred wrote:
>"SAFEKOM" <u61982(a)uwe> a écrit dans le message de groupe de discussion :
>aaf272a1d8d91(a)uwe...
>> Problem:
>> How can I access SQL server on WAN????????????????????????????????
>[quoted text clipped - 3 lines]
>> connection to
>> SQL Server) (Microsoft SQL Server, Error: 53)
>
>> In TCP/IP properties TCP Dynamic ports : 49157
>
>With SqlServer Configuration Manager, you must set a fixed port, and not
>use dynamic port.
>TCP Dynamic Ports : (erase and leave blank)
>TCP Port : 1433 (or another one)
>

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/201007/1

From: SAFEKOM via SQLMonster.com on 15 Jul 2010 14:41
TRIED:
servername,4711

RESULT:
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: TCP Provider, error: 0 - No such host is
known.) (Microsoft SQL Server, Error: 11001)
------------------------------------------------------------------------------
-----
TRIED:
ServerName\SQLEXPRESS

RESULT:
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)
------------------------------------------------------------------------------
-----
TRIED:
Server IP address only 213.343.43.32

RESULT:
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: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

TRIED:
213.343.43.32,1433

RESULT:
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: TCP Provider, error: 0 - A connection
attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has
failed to respond.) (Microsoft SQL Server, Error: 10060)

---------------------------------------------------------------------------

This is whole story, i dont know what going on.

AND

MsDtsSrvr.exe file is also missing from DTS/BINN folder?????????

Kindly help me out of this :(

Nasir.


Erland Sommarskog wrote:
>> What I already done:
>> 1) SQL SERVER is up and the instance connect is running.
>[quoted text clipped - 9 lines]
>> 213.165.131.65 KSSQLSRVR
>> 213.165.131.65 KSSQLSRVR\SPDEV01
>
>So are you trying to connect to a default instance or to a named instance?
>
>Named instances, usually run on a port <> 1433, dynamically selected.
>For this to work, the SQL Server Browser service must be running, and
>UDP port 1434 must be open in the firewall.
>
>Alternatively, you can specify the port when you connect:
>
> SERVERNAME,4711
>
>You can find the actual port number in SQL Server Configuration Manger.
>
>It is not uncommon to disable the Browser service. In this case, it's
>better to reconfigure the server in SSCM to use a fixed TCP port.
>

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/201007/1

From: SAFEKOM via SQLMonster.com on 15 Jul 2010 14:43
It is default Instance.

TRIED:
servername,4711

RESULT:
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: TCP Provider, error: 0 - No such host is
known.) (Microsoft SQL Server, Error: 11001)
------------------------------------------------------------------------------
-----
TRIED:
ServerName\SQLEXPRESS

RESULT:
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)
------------------------------------------------------------------------------
-----
TRIED:
Server IP address only 213.343.43.32

RESULT:
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: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

TRIED:
213.343.43.32,1433

RESULT:
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: TCP Provider, error: 0 - A connection
attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has
failed to respond.) (Microsoft SQL Server, Error: 10060)

---------------------------------------------------------------------------

This is whole story, i dont know what going on.

AND

MsDtsSrvr.exe file is also missing from DTS/BINN folder?????????

Kindly help me out of this :(

Nasir.


Erland Sommarskog wrote:
>> What I already done:
>> 1) SQL SERVER is up and the instance connect is running.
>[quoted text clipped - 9 lines]
>> 213.165.131.65 KSSQLSRVR
>> 213.165.131.65 KSSQLSRVR\SPDEV01
>
>So are you trying to connect to a default instance or to a named instance?
>
>Named instances, usually run on a port <> 1433, dynamically selected.
>For this to work, the SQL Server Browser service must be running, and
>UDP port 1434 must be open in the firewall.
>
>Alternatively, you can specify the port when you connect:
>
> SERVERNAME,4711
>
>You can find the actual port number in SQL Server Configuration Manger.
>
>It is not uncommon to disable the Browser service. In this case, it's
>better to reconfigure the server in SSCM to use a fixed TCP port.
>

--
Message posted via http://www.sqlmonster.com

From: Erland Sommarskog on 15 Jul 2010 17:23
SAFEKOM via SQLMonster.com (u61982(a)uwe) writes:
> It is default Instance.

Why then did your list include a named instance.

> TRIED:
> servername,4711

4711 was just an example. (Which you easily can tell by the number I
chose!) I said that you to use the actual port number.


> TRIED:
> ServerName\SQLEXPRESS

But if this is a default instance, why try with an instance name? Is
it an instance of Express edition, or do you have a different edition.

Could you locate this file:

"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG"

Note that the actual location may be different on your system, depending
on version, architecture and instance name. Find this file and post all
lines up to it says: "Starting up database 'msdb'."

--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: ANN: Database Workbench 4.0.3, the multi-DBMS IDE now available!
Next: Did this ever get resolved?