sql server connect: SQL Server drops off port 1433 on first request -- sql server connect

SQL Server drops off port 1433 on first request

J. R. Tessier
2/25/2005 11:49:04 AM

sql server connect:

I have what I see from this forum and other places is a common symptom: "SQL
Server does not exist or access denied". I have tried every approach I could
glean from the responses posted, but nothing's worked.

I did a little network sniffing (with Ethereal), and what I see when I try
to establish a connection from a client machine to the server is that an
ms-sql-s packet comes in on port 1433, but what immediately goes back is a
[RST, ACK] response, aborting the connection. The client tries again a few
times, but has no better luck.

When I run netstat just before this exchange, I see a sqlserver listening on
port 1433, but after this exchange there's no listener there. He must be as
discouraged as I am.

Conect string is

user id=uuuuu;password=ppppp;data source=srvrname; persist security
info=False;initial catalog=dbname

I'm running SS2000, XP Pro with SP2. TCP/IP is the only enabled SS
protocol. Using mixed authentication. I have an ASP.NET application running
on the server, and it works quite nicely with the database server.

I am able to run queries from the client machine using osql.

I'm going to spend some time at the gym and work off some frustration. Any

RE: SQL Server drops off port 1433 on first request - a clue?

J. R. Tessier
2/26/2005 2:17:03 PM

Acting on a suggestion I found in another post in this forum, I found what
may be relevant entries in the SS log.

(1) SQL Server is listening on 127.0.0.1:1433 AND another, internet
address:1433

(2) Right after the 2 "SQL Serve listening on" log entries, tere's one that
says "SuperSocket Info: Bind failed on TCP port 1433"

These may be clues, but I have been unable to decipher them.

[quoted text, click to view]

Re: SQL Server drops off port 1433 on first request - a clue?

Vikram Vamshi
2/28/2005 10:18:16 AM

Can you post your SQL Server Error Log here?
If I am right, SQL Server by default listens on all your network interfaces.
Your machine is assigned one ip per NIC, you always have at least one NIC
called the loopback adapter with IP address of 127.0.0.1

In your case it was able to bind to the loopback adapter on port 1433 but
not on your external NIC.

This normally happens if another process is holding on to the port 1433.
Shutdown SQL Server and make sure that no one else is using the port.

As a simple test you may want to change the deafault port number and see if
that works (when conencting to a non default port number you will have to
create an alias)

hth
--
Vikram Vamshi
Eclipsys Corporation
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.