Re: Blocking UDP Port 1434
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 03/30/04
- Next message: Travis: "Re: Backing up transaction logs"
- Previous message: Sue Hoegemeier: "Re: Backing up transaction logs"
- In reply to: Wayne: "Blocking UDP Port 1434"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Blocking UDP Port 1434"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Blocking UDP Port 1434"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 30 Mar 2004 14:29:45 -0700
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: Travis: "Re: Backing up transaction logs"
- Previous message: Sue Hoegemeier: "Re: Backing up transaction logs"
- In reply to: Wayne: "Blocking UDP Port 1434"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Blocking UDP Port 1434"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Blocking UDP Port 1434"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]