Re: Mysterious Port of SQL Server not shown by netstat

From: Stefan Delmarco [MSFT] (StefanDe_at_online.microsoft.com)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 09:23:31 -0000

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 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Abhishek Srivastava" <abhishek-srivastava@nospam.net> wrote in message
news:ewS0U%23YDEHA.3256@TK2MSFTNGP09.phx.gbl...
> In the general Tab.  I can see that the Enabled Protocols by Order has
> Tcp/Ip and Named Pipes. The port of Tcp/Ip is 1433. The default pipe for
> Named Pipe is sql\query.
>
> In the Alias tab, there is no entry.
>
> In the Db-Librarry objects I can see
>
> File name: c:\windows\system32\ntwdblib.dll
> version:8.00.194
> Date: 8/5/2000
> Size 274489 Bytes
>
> Automatic ANSI to OEM Conversion is checked
> Use international Settings is checked
>
> In Network Libraries Tab
>
> Named Pips    c:\windows\system32\dbnmpntw.dll    8.0.341  3/25/2003
> Tcp/Ip        c:\windows\system32\dbnetlib.dll    8.0.341  3/25/2003
> Multiprotocol c:\windows\system32\dbmsrpcn.dll    8.0.341  3/25/2003
> NWLink IPX/SPX c:\windows\system32\dbnetlib.dll   8.0.341  3/25/2003
>
>
> My query analyzer client from  local machine and remote machine
> successfully connects to my server. There is a jdbc client which wants
> to connect at port 1433 that fails saying could not establish network
> connection at port 1433.
>
> I did netstat -a and got completely confused when I didn't find that
> port 1433 listed there... even when the sql server and query analyzer
> client are working fine.
>
> regards,
> Abhishek.
>
> Tibor Karaszi wrote:
> > Did you run Server Network Utility?
> >

Relevant Pages

  • Re: Is there ever a reason to have a transaction around a select..
    ... cache-size rows are found during the SELECT operation, the client ... on the rowset state as the SELECT query walks the query plan fetch rowset. ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Default protocols ..
    ... I checked the default port in the Client Utility on the ... "I checked the default port fort the TCP and it is the good ... And are you in a totally SQL Server 2000 environment? ... I set the TCP has the only one default client protocol with the CLICONFG ...
    (microsoft.public.sqlserver.connect)
  • Re: Access To SQL Server Behind Firewall
    ... Using the Client Network Utility on the SQL Client to ... you tell the client what port the "listening" SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Change default port no.
    ... You must still have port 1434 open. ... > change on client side.Suppose, u r having two computers C1 and C2.C1 is ... > having SQL server installed and C2 does not. ... >>> while making connections related to this port number? ...
    (microsoft.public.sqlserver.connect)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.server)