Re: Default protocols ..

Some low probability possibilities:
When you say, "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?
And are you in a totally SQL Server 2000 environment? 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. If your server is SQL Server 2005 there are additional things you can check, but it sounds like it's not.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Patrick B." <patrick@xxxxxxxxxxx> wrote in message news:eOPhBmIyHHA.484@xxxxxxxxxxxxxxxxxxxxxxx
Hi everyone,

I have something weird with an SQL Client connection and the default protocols.

I set the TCP has the only one default client protocol with the CLICONFG tool. On most of the computers, when a client wants to connect to a server with its IP (somewhere over Internet), it uses the default protocols perfectly.
Let's say, ie : osql -S IP -U usedID -P password

BUT. Sometimes, it doesn't. if I add the port to the server ip, then it works. But I don't want to (in fact, I can't do it into my distribued application) !
osql -S IP,1433 -U usedID -P password

Of course, I checked the default port fort the TCP and it is the good one.

If a run a netstat to see what happens, I can see something like that :
TCP POSTE1:2612 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2613 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2614 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2615 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2616 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2617 IP:ms-sql-s TIME_WAIT
TCP POSTE1:2618 IP:ms-sql-s TIME_WAIT

So, it uses the TCP, connects to the right port BUT does not makes the connection. If I just add this f**** ,1433, then it connects fine to the same port. Really crazy...

Does anyone have an idea please ?
Thanks a lot !

Patrick



.

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.server)
  • 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: 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)