Re: Very strange behavior of SQLServer with connection from CGI

From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 14:07:51 -0500

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@hotmail.com> wrote in message
news:lgr111lmtd19n6j22gkgu4vsaq9vo8n8ae@4ax.com...
> 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.
>
> >you can modify the connection information to
> >include the port number of the named instance
>
> 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@Careerbuilder.com> wrote:
>
> >First guess, this is not a default SQL instance.  I think your customer
> >network has disabled UDP as a "security" measure.  SQL clients use a UDP
> >connection to port 1434 to resolve port numbers for named instances.  If
> >your customer won't allow UPD, you can modify the connection information
to
> >include the port number of the named instance or create a client alias
that
> >specifies a port number.  You can use the SQL Server Network utility to
lock
> >an instance to a port number.
> >
> >Finally, don't cross-post to the universe.
>

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... I believe the complete Windows auth user access is too complicate, ... which trusted connection is meant? ... it would still be listening on the old port. ... Microsoft, SQL Server Books Online ...
    (microsoft.public.sqlserver.connect)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... It seems that your SQL Server instances are Named Instances, ... Default Instances uses 1433 TCP port by default as a Static Port but not the ... If you change your Connection String as following, ...
    (microsoft.public.sqlserver.setup)
  • Re: Sql Remote Connection issue
    ... port 1433 TCP Allow ... Copyright 2006 Microsoft Corporation. ... osql does not support all features of SQL Server 2005. ... Sqlcmd: Error: Microsoft SQL Native Client: An error has occurred while establishing a connection to the server. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2005 Connection Problems
    ... - it is't completely clear what the SQL Server Browser is for. ... connection reqest was being rejected. ... I think the problem is still likely the the port is blocked by some ... firewall between the server and that client. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... enable network communication ... make sure that the port isn't blocked ... "An error has occurred while establishing connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ...
    (microsoft.public.sqlserver)