RE: Tracing SQL Server 2000 Connections

Hi Doug,
Thanks for your response.

In TCP/IP network model, there is no middle ground between Transport layer
and Application Layer. You said, "So is there no way of tracing a
connection request all the way from the wire (TCP/IP) into SQL Server?",
Netmon can do this.

Though Netmon capture all the network loads, you can filter the traces by
the destination TCP port. For example, if your SQL Server is listening on
1433, you can just filter the trace with the destination TCP port = 1433.
After the filter, you get all the requests all the way into your SQL Server.

To track the details, please ensure that all of your clients use TCP/IP to
connect to your SQL Server. You may only enable TCP/IP protocol on your
server side via Start -> Microsoft SQL Server -> Server Network Utility.
After you do this, you need to restart your SQL Server. You can also check
which TCP port your SQL Server is using via Server Network Utility (Click
Properties when you select TCP/IP).

If there is no requests found in the trace, please check if you can access
the TCP port from your clients via telnet command: telnet <servername> <TCP
port number>

Also you can manually test the connection via osql command:
[SQL Authentication]
osql -S <servername>\<instancename> -U <username> -P <password>
[Windows Authentication]
osql -S <servername>\<instancename> -E

If you have any other questions or concerns, please feel free to let me
know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================


.

Relevant Pages

  • Re: Umstieg von Access auf SQL-Server
    ... > Bei Port 1433 sabber ich dann immer gleich Named Pipes. ... Nein, TCP/IP. ... How To Change SQL Server Default Network Library Without ... How To Set the SQL Server Network Library in an ADO Connection String ...
    (microsoft.public.de.vb.datenbank)
  • Cannot connect to my local SQL Server
    ... TCP/IP from my VB app. ... If I add Network Library=dbmssocn to the ... Neither can I connect to the box from other computers, though again, if I don't specify the network library, the connection is made fine. ... I checked the network settings on the sql server and they seem fine. ...
    (microsoft.public.vb.general.discussion)
  • Re: Different NT Domains
    ... Please check your SQL client network configuration. ... In the event that TCP/IP ... I want to use SQL Server Authentication to have the "other" network ...
    (microsoft.public.sqlserver.security)
  • Re: sql server2000; TCP/IP vs Named Pipes
    ... wireshark.org have an excellent protocol analyser. ... My company is running an application that uses sql server 2000 sp3. ... We prefer to use TCP/IP but we are having issues with users losing there ... How can I isolate the problem to th network? ...
    (microsoft.public.sqlserver.tools)
  • Re: sa loginname being hacked
    ... exposed for requests from outside the network. ... Also it takes up a lot of network bandwidth which would never be ... Microsoft Certified Solution Developer ... > SQL Server they said EXACTLY the opposite of what you just said. ...
    (microsoft.public.sqlserver.security)
Loading