Re: Blocking UDP Port 1434

From: Jasper Smith (jasper_smith9_at_hotmail.com)
Date: 03/31/04 

Date: Tue, 30 Mar 2004 23:37:44 +0100

You can use the client network utility to set up an alias and specify the
port or you can specify it in a connection string 

-- 
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@discussions.microsoft.com> wrote in message
news:115da01c416a0$77cbcd40$a001280a@phx.gbl...
> 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!
> >
> >.
> >

Relevant Pages

  • Re: Mysterious Port of SQL Server not shown by netstat
    ... If this fails then yoru SQL Server is not listening on 1433. ... port, only ms-sql-s). ... > My query analyzer client from local machine and remote machine> successfully connects to my server. ... There is a jdbc client which wants> to connect at port 1433 that fails saying could not establish network> connection at port 1433. ...
    (microsoft.public.sqlserver.programming)
  • Re: Default protocols ..
    ... I checked the default port in the Client Utility on the ... "I checked the default port fort the TCP and it is the good ... And are you in a totally SQL Server 2000 environment? ... I set the TCP has the only one default client protocol with the CLICONFG ...
    (microsoft.public.sqlserver.connect)
  • Re: Access To SQL Server Behind Firewall
    ... Using the Client Network Utility on the SQL Client to ... you tell the client what port the "listening" SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.clients)