Default protocols ..
- From: "Patrick B." <patrick@xxxxxxxxxxx>
- Date: Tue, 17 Jul 2007 17:48:49 +0200
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
.
- Follow-Ups:
- Re: Default protocols ..
- From: Rick Byham, \(MSFT\)
- Re: Default protocols ..
- Prev by Date: Re: error 25 trying to connect to sql server database on local machine
- Next by Date: Re: provider: Named Pipes Provider, error: 40 - Could not open a c
- Previous by thread: Re: error 25 trying to connect to sql server database on local machine
- Next by thread: Re: Default protocols ..
- Index(es):
Relevant Pages
|
Loading
