|
|
|
|
Change default port no.
Hi,
As we know,SQL server listens on port 1433 by default. Is there any
dependency between client and SQL server for this port number?I mean, how
will know the client that on which port the target SQL server listens?
Suppose I change this port number to 1533 and restarted the SQL server.Now I
tries to connect to SQL server from a client.What will happnen on client side
while making connections related to this port number?
With rgds
Mon, 10 Jan 2005 01:21:02 -0800
"=?Utf-8?B?UmFqZW5kcmE=?="
|
Re: Change default port no.
You will need to change the port the client looks for as well. Open the
client network utility and you will see a Properties button that will allow
you to set the TCP port that the client will use by default.
--
Andrew J. Kelly SQL MVP
"Rajendra" wrote in message
news:3B2040E2-9C6A-4941-B442-AD8A265A4765@microsoft.com...
> Hi,
>
> As we know,SQL server listens on port 1433 by default. Is there any
> dependency between client and SQL server for this port number?I mean, how
> will know the client that on which port the target SQL server listens?
>
> Suppose I change this port number to 1533 and restarted the SQL server.Now
> I
> tries to connect to SQL server from a client.What will happnen on client
> side
> while making connections related to this port number?
>
> With rgds
Mon, 10 Jan 2005 08:48:51 -0500
"Andrew J. Kelly"
|
Re: Change default port no.
You must still have port 1434 open. SQL Server uses port 1434 to establish
connections with clients. They interrogate this port to find suitable Sql
Server hosts but the actual data is sent thru 1433 or what ever port you
changed it to. There is plenty of good information in BooksOnLine. You
might want to try starting here: "Net-Library, overview"
--
Andrew J. Kelly SQL MVP
"Rajendra" wrote in message
news:15C84574-02D6-4BDD-8A90-A36530D22751@microsoft.com...
> Hi Andrew,
>
> Thanx for the reply. But if I am right then I think there is no need to
> m
Tue, 11 Jan 2005 08:41:19 -0500
"Andrew J. Kelly"
|
|