Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!

From: Howard Long (howard_at_howardlongxxx.com)
Date: 09/14/04


Date: Tue, 14 Sep 2004 09:41:12 +0000 (UTC)


"Teddy Smith" <teddy@smith.com> wrote in message
news:ci5d2a$ore$1@perki.connect.com.au...
> I am also wondering if it has something to do with TCP port allocation.
When
> I run "netstat -an" from the commaned prompt while the query is running I
> can see all the client ports being opened to 1433 on the SQL server and
this
> is working. Once the client gets to port 5000 it seems to stop and then
> start using ports from 1025 again (re-using them I suppose), this is about
> the time the error is thrown.

Are you suggesting that there loads and loads of SQL login/logouts over a
short period of time? I wonder if the sessions are not being dropped in time
at the TCP level. Normally I'd expect a different error from the SQL Server
(max connections reached) but you are not even achieving this. Can you see a
correctly negotiting SYN/ACK and FIN response on the NetMon when
establishing and dropping at the TCP level? Are you experiencing the same
number of SQL login/logouts on the Win2K box?

What is not clear here is that the error you get - [Microsoft][ODBC SQL
Server Driver][DBNETLIB]SQL Server does not exist or access denied - would
only occur at session establishment, not half way through a fetch.

On the other hand, the error - [Microsoft][ODBC SQL Server Driver] Timeout
expired - would occur part way through a query, usually when waiting for a
long running query to respond.

I wonder: are you getting the - [Microsoft][ODBC SQL Server Driver] Timeout
expired - which would implicitly sever the session, and then the client side
app attempts to reconnect?

Kind Regards, Howard



Relevant Pages

  • 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.odbc)
  • 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.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.clients)
  • Re: Default protocols ..
    ... "I checked the default port fort the TCP and it is the good one" did you mean you checked the default ... port for TCP/IP in the Client Network Utility on the client that can't connect? ... If your client has SQL Server 2005 installed, you may be using the SQL Server Native Client, and need to check the client protocol and port number using the SQL Server Configuration Manager. ... I set the TCP has the only one default client protocol with the CLICONFG tool. ...
    (microsoft.public.sqlserver.connect)
  • Re: Mysterious Port of SQL Server not shown by netstat
    ... If this fails then yoru SQL Server is not listening on 1433. ... port, only ms-sql-s). ... > 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. ...
    (microsoft.public.sqlserver.programming)