Re: Very strange behavior of SQLServer with connection from CGI

mdurliSPAMFILTER_at_hotmail.com
Date: 02/14/05 

Date: Mon, 14 Feb 2005 18:40:24 GMT

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: Very strange behavior of SQLServer with connection from CGI
    ... I see my UDP packet and sqlserver answers with another ... >include the port number of the named instance ... Then the fact that sqlserver is in a cluster, ... customer moved to a cluster and it worked fine for a few months, ...
    (microsoft.public.sqlserver.security)
  • Re: Very strange behavior of SQLServer with connection from CGI
    ... I see my UDP packet and sqlserver answers with another ... >include the port number of the named instance ... Then the fact that sqlserver is in a cluster, ... customer moved to a cluster and it worked fine for a few months, ...
    (microsoft.public.sqlserver.connect)
  • Re: setting up a LAT service via a terminal server
    ... > node in my hobbyist cluster. ... Żou can put the download incantations in NCP, ... HELP DEFINE PORT will give you a pretty good idea what to do. ... > connections, but just one address for OUTgoing connections as well, the ...
    (comp.os.vms)
  • Re: Block UDP Ports?
    ... I'm using Checkpoint Firewall-1. ... reasonable that Firewall-1 would leave UDP wide open. ... > UDP ICMP port unreachable scanning: This scanning method varies from the ...
    (comp.security.firewalls)
  • UDP DoS attack in Win2k via IKE
    ... This memo should clarify the issue discovered with the UDP DOS ... Sending of UDP traffic to port 500 UDP will cause windows to ... attacked host is an IPSec gateway). ...
    (Bugtraq)
Quantcast