August 2, 2005 at 2:10 am
Is there any way to change UDP port 1434 in sql server? I read in few threads that we can avoid using it by connecting to a specific port (instead of instance name) from the client and close the port in firewall.
This is bit of a pain but If I manage to do it somehow, does it work in case of a sql server cluster?
Appreciate answers.
Faiza
August 2, 2005 at 2:39 am
Is there any way to change UDP port 1434 in sql server?
No, 1434 is always the port used by the listener.
I read in few threads that we can avoid using it by connecting to a specific port (instead of instance name) from the client and close the port in firewall.
This is bit of a pain but If I manage to do it somehow, does it work in case of a sql server cluster?
I haven't actually done it myself, but I can't see why it wouldn't work. As long as the servers in the cluster use the same port.
August 4, 2005 at 6:41 am
It will work with a cluster. In a default instance, all nodes - when active - will listen on port 1433.
In a named instance, nodes will listen on another chosen port (find out by looking at the top of the errorlog), but that port number will be consistent across all nodes.
clients simply connect to <servername>,<portno>
or <ip addr>,<portno>
Although the port number for a number instance is pretty stable, I have seen it change in rare situations (eg. when sql comes up and something else is bound to that port).
Cheers,
- Mark
August 4, 2005 at 10:40 am
If you have a firewall nearby, you might be able to do some port redirection if needed.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply