Re: Blocking UDP Port 1434

anonymous_at_discussions.microsoft.com
Date: 03/30/04

  • Next message: Bill B: "Interesting issue connecting to Sql server through a firewall.." 
    Date: Tue, 30 Mar 2004 13:46:33 -0800

    Thank you, Sue, for the input. I thought for named
    instances, tcp ports can be coded on server and clients,
    but NOT UDP port 1434. The following is what I get from
    BOL. If it can be done without using UDP port 1434, how
    should I configure the client to go through gateways?

    ----------
    'Have the network administrator configure the firewall to
    forward the IP address and TCP port the instance of SQL
    Server is listening on (using either 1433 for a default
    instance, or the TCP port you configured a named instance
    to listen on). Also configure the firewall to forward
    requests for UDP port 1434 on the same IP address. SQL
    Server 2000 uses UDP port 1434 to establish communications
    links from applications.'
    ----------

    >-----Original Message-----
    >Don't know that you can change the SQL Server Resolution
    >Service running on UDP port 1434. However, you can still
    >connect without using the resolution service as long as
    the
    >client knows the port to go through. You don't have to
    HAVE
    >to go through UDP 1434 to connect to a named instance.
    >
    >-Sue
    >
    >On Tue, 30 Mar 2004 12:55:25 -0800, "Wayne"
    ><anonymous@discussions.microsoft.com> wrote:
    >
    >>In order to protect from 'slammer' kind of virus, we are
    >>planning to block UDP Port 1434 on all gateways. Named
    >>instances seem to rely on UDP Port 1434. Since TCP port
    >>the sql instance is listening on can be re-assigned, Can
    >>we reassign the UDP port 1434 as well? Any input will be
    >>appreciated. Thank you!
    >
    >.
    >

  • Next message: Bill B: "Interesting issue connecting to Sql server through a firewall.."

    Relevant Pages

    • Re: problem with NDIS test
      ... server uses UDP port 25000 to coordinate startup and shutdown. ... However, both the client ... > NDISTest claims to complete immediately. ...
      (microsoft.public.development.device.drivers)
    • RE: exchange server attempting to connect to odd ports
      ... It seems to me to be the new mail message notifications that are generated by the server to the client, which uses a UDP port between 1024 and 65535, which is determined by the client during logon. ...
      (Focus-Microsoft)
    • Re: find all computers in LAN submask
      ... server listen on some known UDP port. ... broadcast UDP message to that UDP port. ... the client then knows the IP address of the server. ... So, the server listens to the broadcast address, the client writes to it. ...
      (comp.os.linux.development.apps)
    • Re: find all computers in LAN submask
      ... server listen on some known UDP port. ... broadcast UDP message to that UDP port. ... the client then knows the IP address of the server. ...
      (comp.os.linux.development.apps)
    • Re: Windows 2003 Server NAT not allowing IPSEC to go through.
      ... connect to their server using IPSec. ... NIC and in NAT, no packet filtering on the NIC or in NAT... ... > The clients are using Nortal Extranet that connects through IPSec (their ... documentation asks that IP Port 50, UDP Port 500 and UDP Port 2001 be ...
      (microsoft.public.win2000.ras_routing)