Re: Mysterious Port of SQL Server not shown by netstat

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Abhishek Srivastava (abhishek-srivastava_at_nospam.net)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 16:28:30 +0530

Hello Stefan,

> Make sure clients are connecting on TCP through Query Analyser and
> specifying the SQL Server as: "TCP:<SQLServerNameorIP>,1433" (for
example,

My query analyzer failed to connect to my sql server when I said
TCP:NTA21178,1433. The error message was SQL Server does not exist or
access denied. Message 17, Level 16 State 1

> For "service name" output use:
> netstat -ap TCP | findstr ms-sql-s
> For "numeric" output use:
> netstat -anp TCP | findstr 1433

I tried these commands. They return nothing.

> Have a look at the following file to see the mapping between service name
> and port:
> %SYSTEMROOT%\system32\drivers\etc\services

I have 2 sets of such enteries.

ms-sql-s 1433/tcp #Microsoft-SQL-Server
ms-sql-s 1433/udp #Microsoft-SQL-Server
ms-sql-m 1434/tcp #Microsoft-SQL-Monitor
ms-sql-m 1434/udp #Microsoft-SQL-Monitor

(I tried the above commands with ms-sql-s, ms-sql-m, 1433, 1434
options... but still the commands returned no results)

Even the TCPView program from sys internals does not show 1433 or 1434
being used.

OK so now I am convinced that I am not using TCP How can I configure TCP
and test whether its configured on my machine or not?

The network client utiltity shows me that two protocols are enabled on
my computer. TCP/IP and Named Pipes.

I have succesfully queried my sql server from a remote computer. Now
named pipes are for interprocess communication they cannot do remoting
between machines.

So how can the second computer query my machine unless TCP/IP was
enabled. However if TCP/IP is enabled why isn't it appear in any of the
utilities.

Thank you so much for your help and patience.

regards,
Abhishek.

Stefan Delmarco [MSFT] wrote:
> A couple of things to check:
>
> Make sure clients are connecting on TCP through Query Analyser and
> specifying the SQL Server as: "TCP:<SQLServerNameorIP>,1433" (for example,
> TCP:SQL01,1433).
> If this fails then yoru SQL Server is not listening on 1433.
>
> The output from netstat can either display well known ports by their
> "service name" or their numerical representation. "ms-sql-s" and 1433 are
> the same thing:
>
> For "service name" output use:
> netstat -ap TCP | findstr ms-sql-s
>
> For "numeric" output use:
> netstat -anp TCP | findstr 1433
>
> Download TCPView from http://www.sysinternals.com to easily see what ports
> sqlservr.exe has bound to. Note that TCPView.exe only uses the "name"
> output (i.e. if sqlservr.exe is listening on 1433 you won't see 1433 as the
> port, only ms-sql-s).
>
> Have a look at the following file to see the mapping between service name
> and port:
> %SYSTEMROOT%\system32\drivers\etc\services
>
> You'll find:
> ms-sql-s 1433/tcp #Microsoft-SQL-Server
> ms-sql-s 1433/udp #Microsoft-SQL-Server
>
>

Relevant Pages

  • Re: CONTAINS performance
    ... That said, and with the query plan, I can start to give you more ... relational join in the context of the free-text optimization, ... SQL Server tables. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Access to SQLServer GCE
    ... Actually, as Larry points out, the Access client does a good job of filtering only information that you need. ... If your query is bound to a report, and you open that report supplying a typical "where" for that report, then Access will NOT pull down all the records, but in most cases Access will only pull down the required records and respect your filter. ... So SQL server will respect the conditions and filtering placed into those queries, and therefore only pull down those records you require. ... The suggestion in these cases is to consider using a pass-through query since all of that summing is done before the row comes down the network pipe. ...
    (comp.databases.ms-access)
  • Re: Indexing Service, Openquery and sp_executesql
    ... SQL Server version and sp are you running? ... > data from the indexing service catalog when pasted into ... > query analyzer, but failed when put against sp_executesql ... I would choose Microsoft Indexing ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Problem using Access or Query Designer to run queries in SQL Serve
    ... >or Query Designer within Enterprise Manager, it works and I get data back. ... >ODBC Call Failed [ODBC SQL Server Driver] Timeout Expirederror in Access ... >[ODBC SQL Server Driver] Timeout Expired ...
    (microsoft.public.sqlserver.odbc)
  • Re: Transaction Isolation Level
    ... This means that while I initiate a transaction selecting all new orders it ... My query is executed on a SQL server 2005. ... the isolation level you should use is snapshot isolation. ...
    (comp.databases.ms-sqlserver)