Yes is not a default SQL instance, I forgot to mention.
The address is xxx.xxx.xxx.xxx\instance

But then, If he has disabled UDP, why it works the first time, and
then why I have to wait about 40 seconds to make another working
connection?
The first time, I see my UDP packet and sqlserver answers with another
UDP packet.

How? using xxx.xxx.xxx.xxx\instance,port ?
Does my customer has to tell me the instance port or can I get it in
some other way?

Then the fact that sqlserver is in a cluster, may be the cause?
The soft worked fine when we used a single sqlserver, then the
customer moved to a cluster and it worked fine for a few months, then
it stopped working.
I'm trying to find the cause other than the solution, because the
network administrator of my customer isn't helping me that much.

About crossposting, I never really understood: if a problem is about
clustering (because my sqlserver customer is on a cluster), security
(because I suspected that he may have close the UDP port), and
connection (that is my problem), isn't correct to post in the three
newsgroups? (I added borland because I use a borland compiler)

Thank you very much!



On Mon, 14 Feb 2005 12:41:43 -0500, "Geoff N. Hiten"
<SRDBA (AT) Careerbuilder (DOT) com> wrote:

Not sure on the whole connection/reconnection issue. You may have an MDAC
or connection pooling issue. Make sure your client systems are up to date
with the latest MDAC. Older MDAC versions have problems with named instance
resolution. Clustered instances look like named instances from a client
perspective, otherwise they are identical to a standard SQL server
implementation.

You specify ports with xxx.xxx.xxx.xxx,portnum.

You may also be running into a windows security issue. Windows attempts to
create a SSPI session for windows networking if there is a common security
context when a socket is created. This attempt and failure may also be
causing your problems.

Finally there could be DNS issues, but that seems very unlikely since you do
get one good connection..


--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

<mdurliSPAMFILTER (AT) hotmail (DOT) com> wrote

I understand, but the funny thing is that when I run the program just
executing it, it works everytime.
The problem is when I call it from the web server (on the same machine
where I run it by executing it).

Do you have an idea why when I run the software locally, launching the
exe, it originates only TCP/IP packets, and when I run it through the
webserver as a cgi it originates this UDP packet?

I mean, the oledb string is exactly the same.
It is because the user that executes the program the first time is the
local user, and the second time (when through the webserver) the user
is the INET user?

I'm sure the solution is there.

Thanks,
Mattia

On Mon, 14 Feb 2005 14:07:51 -0500, "Geoff N. Hiten"
<SRDBA (AT) Careerbuilder (DOT) com> wrote: