Re: Default protocols ..
- From: "Patrick B." <patrick@xxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 09:24:56 +0200
Hi,
Thank you for you reply.
Yes, it is in a totally SQL Server 2000 environment, and every server has an
instance. And yes, I checked the default port in the Client Utility on the
client that can't connect.
I found new things, more and more weird.
On a client that can't connect, I tried with the local server (we install an
instancied MSDE with all of our softwares, and the configuration on clients
and servers are the same). The problem is exactly the same with the
localhost.
osql -S 127.0.0.1 -E ==> failed
osql -S 127.0.0.1\INSTANCENAME -E ==> ok
osql -S 127.0.0.1,1433 -E ==> ok
But on most pcs, those 3 cases are working perfectly ! I really don't
understand...
Thanks again,
Patrick
(sorry for my poor english !)
"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de news: 99849E87-A62F-40B7-AF97-567C1A3E9A6F@xxxxxxxxxxxxxxxx
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
.
- References:
- Default protocols ..
- From: Patrick B.
- Re: Default protocols ..
- From: Rick Byham, \(MSFT\)
- Default protocols ..
- Prev by Date: sql 2005 connection string question
- Next by Date: Re: Access front-end to SQL back-end
- Previous by thread: Re: Default protocols ..
- Next by thread: Cannot connect to SQL 2000 remotely
- Index(es):
Relevant Pages
|
