Re: Re SQL Resolution Service

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 07/28/04 

Date: Wed, 28 Jul 2004 05:52:33 -0600

SQL Resolution Service on UDP 1434 is only used to support
multi-instances. It's not used with SQL Server 7 as that
version doesn't support named instances. It's not used by
the SQL Server instance or directly by clients to connect to
SQL Server. It's just to enumerate the instances on a server
and find the listening port for the specific instance.
If you try to connect to YourServer\YourNamedInstance and
that's what you specify for the connection, it hits UDP 1434
to use the SQL Server Resolution Service to find what port
number YourServer\YourNamedInstance is listening on. You can
bypass that by specifying the port yourself and then there
is no need to go through UDP 1434.

-Sue

On Wed, 28 Jul 2004 01:08:02 -0700, SqlJunkies User
<User@-NOSPAM-SqlJunkies.com> wrote:

>Hi,
>
>I am a novice to SQL Server. I work in the area of network security. In my study of the SQL Slammer/Sapphire worm, I came across SQL Resolution Service which listens on UDP Port 1434. It seems that this service is used by clients to get the list of named instances, to exchange keep-alive messages, and for opening a registry key (the slammer worm cause). I would like to know what are its other uses and other acceptable commands by the service. After my futile search on MSDN I am posting a message here.
>
>Any pointers or links regarding this are more than welcome.
>
>Thanks in advance,
>Bhagya
>
>---
>Posted using Wimdows.net NntpNews Component -
>
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

Relevant Pages