Changing a server's TCP/IP address.

We are going to be changing our SQL Server's TCP/IP address. Is there
anything I need to do within SQL to make sure it works correctly?
The machine is not doing replication.
TIA - Jeff.If it's not a cluster, none.
Linchi
"Mufasa" wrote:
> We are going to be changing our SQL Server's TCP/IP address. Is there
> anything I need to do within SQL to make sure it works correctly?
> The machine is not doing replication.
> TIA - Jeff.
>
>|||If it's not in a cluster, then just do the IP change and there's nothing
else to do, outside of restarting SQL Server. If it's a cluster, then:
http://support.microsoft.com/kb/230356
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Mufasa" <jb@.nowhere.com> wrote in message
news:eSPpRDqYIHA.4180@.TK2MSFTNGP06.phx.gbl...
We are going to be changing our SQL Server's TCP/IP address. Is there
anything I need to do within SQL to make sure it works correctly?
The machine is not doing replication.
TIA - Jeff.|||What about if the server is involved in mirroring or tlog shipping?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:D9BF238C-945E-47BE-B4D9-6B536A8BF9AE@.microsoft.com...
> If it's not a cluster, none.
> Linchi
> "Mufasa" wrote:
>> We are going to be changing our SQL Server's TCP/IP address. Is there
>> anything I need to do within SQL to make sure it works correctly?
>> The machine is not doing replication.
>> TIA - Jeff.
>>|||I don't believe they depend on the IP address, but I don't have a test
install to verify so I could be wrong. But in any event I certainly hope MS
knows much better than having an app component dependent on IP directly. But
then if an app directly depends on IP, perhaps we should have it failed so it
can fixed.
Linchi
"TheSQLGuru" wrote:
> What about if the server is involved in mirroring or tlog shipping?
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:D9BF238C-945E-47BE-B4D9-6B536A8BF9AE@.microsoft.com...
> > If it's not a cluster, none.
> >
> > Linchi
> >
> > "Mufasa" wrote:
> >
> >> We are going to be changing our SQL Server's TCP/IP address. Is there
> >> anything I need to do within SQL to make sure it works correctly?
> >>
> >> The machine is not doing replication.
> >>
> >> TIA - Jeff.
> >>
> >>
> >>
>
>|||Thanks everybody for your help.
J.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:u7pBQmqYIHA.4476@.TK2MSFTNGP06.phx.gbl...
> If it's not in a cluster, then just do the IP change and there's nothing
> else to do, outside of restarting SQL Server. If it's a cluster, then:
> http://support.microsoft.com/kb/230356
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Mufasa" <jb@.nowhere.com> wrote in message
> news:eSPpRDqYIHA.4180@.TK2MSFTNGP06.phx.gbl...
> We are going to be changing our SQL Server's TCP/IP address. Is there
> anything I need to do within SQL to make sure it works correctly?
> The machine is not doing replication.
> TIA - Jeff.
>
>sql

change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoonOn the clientside, you would just run Client Network Utility (cliconfg.exe).
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegroups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac...ds/default.aspx)
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegroups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>|||oj:
Thank you.
JCVoon

change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoonOn the clientside, you would just run Client Network Utility (cliconfg.exe).
--
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegroups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac/downloads/default.aspx)
--
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegroups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>|||oj:
Thank you.
JCVoon

change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoon
On the clientside, you would just run Client Network Utility (cliconfg.exe).
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegr oups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>
|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon
|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac/...s/default.aspx)
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegro ups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>
|||oj:
Thank you.
JCVoon

Change SQL Port doesnt change

I am trying to change the port of an instance via the SSCM. Afther changing
the TCP/IP protocol -> ALL IP -> Blank/1433 and restart the service it goes
back to previous configuration.
Any ideas why? I want all my named instances to be using 1433.
The Default port is 1433 so U need not have to configure for 1433
"ipconfig2" wrote:

> I am trying to change the port of an instance via the SSCM. Afther changing
> the TCP/IP protocol -> ALL IP -> Blank/1433 and restart the service it goes
> back to previous configuration.
> Any ideas why? I want all my named instances to be using 1433.
>
|||For some reason, SQL Server does not like assigning named instances to port
1433. Even though a clustered instance lives in its own virtual server and
should not have a problem with 1433, I have run into problems trying to get
it to work. I would suggest choosing another port and assigning all your
instances to that port.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"ipconfig2" <ipconfig2@.discussions.microsoft.com> wrote in message
news:9EFC71C2-CAD3-45CE-910E-A831ACCB8562@.microsoft.com...
>I am trying to change the port of an instance via the SSCM. Afther changing
> the TCP/IP protocol -> ALL IP -> Blank/1433 and restart the service it
> goes
> back to previous configuration.
> Any ideas why? I want all my named instances to be using 1433.
>
|||As I thought. But there is nothing in documentation that says that it's not
possible.
I have a x64 cluster where this works great and a x64wow cluster which is
troublesome.
I hoped MS would comment on this but I guess I have to file a support case.
To Khwaja - please read the manual. When installing clustered named
instances the port number is randomly assigned.
Thanks for replies.
Rune
"Geoff N. Hiten" wrote:

> For some reason, SQL Server does not like assigning named instances to port
> 1433. Even though a clustered instance lives in its own virtual server and
> should not have a problem with 1433, I have run into problems trying to get
> it to work. I would suggest choosing another port and assigning all your
> instances to that port.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "ipconfig2" <ipconfig2@.discussions.microsoft.com> wrote in message
> news:9EFC71C2-CAD3-45CE-910E-A831ACCB8562@.microsoft.com...
>
|||By default, the Default instance is assigned TCP 1433, Named Instances use
Dynamic Ports; however, this same manual states that the best practice when
supporting connectivity through firewalls is to declare a static port
assignment, and then proceeds to note how to do this through the SSCM. So,
I am not sure which "manual" you are referring to.
Anthony Thomas

"ipconfig2" <ipconfig2@.discussions.microsoft.com> wrote in message
news:4778F614-5C49-43C3-BD45-A9E24EE1535E@.microsoft.com...
> As I thought. But there is nothing in documentation that says that it's
not
> possible.
> I have a x64 cluster where this works great and a x64wow cluster which is
> troublesome.
> I hoped MS would comment on this but I guess I have to file a support
case.[vbcol=seagreen]
> To Khwaja - please read the manual. When installing clustered named
> instances the port number is randomly assigned.
> Thanks for replies.
> Rune
> "Geoff N. Hiten" wrote:
port[vbcol=seagreen]
and[vbcol=seagreen]
get[vbcol=seagreen]
your[vbcol=seagreen]
changing[vbcol=seagreen]
|||Hi Anthony
I cannot set the static port - it goes back to the dynamically set port when
I have changed it. The manual is BOL and Help file of SSCM. I have another
cluster where this is no problem so I wondered if there is a bug somewhere in
the software. I am using version 2153.
I want all my instances to use port 1433 since there are applications that
have hardcoded port 1433 as database port.
Regards
Rune
"Anthony Thomas" wrote:

> By default, the Default instance is assigned TCP 1433, Named Instances use
> Dynamic Ports; however, this same manual states that the best practice when
> supporting connectivity through firewalls is to declare a static port
> assignment, and then proceeds to note how to do this through the SSCM. So,
> I am not sure which "manual" you are referring to.
>
> Anthony Thomas
>
> --
> "ipconfig2" <ipconfig2@.discussions.microsoft.com> wrote in message
> news:4778F614-5C49-43C3-BD45-A9E24EE1535E@.microsoft.com...
> not
> case.
> port
> and
> get
> your
> changing
>
>
|||All instances in your enterprise or all instances on a multi-instanced
cluster? The former is achievable, the latter is impossible: each instance
on a single cluster must "listen" on a unique set of ports, one or more, as
the case may be, but unique from any other cohosted instance. These ports
can be static or dynamic per instance.
Now, Geoff has stated that he has had difficulty running named instance on
TCP 1433; however, I guarantee you that you can run on static ports. I
currently run multiple named instances running on TCP 11291, 11292, 11293,
etc. correlating the LSD with the named instance id. So, I know it works.
I've never tried to run a named instance under the default port, reserving
that for default (unnamed) instances.
I doubt your applications hard code ports. If they do, then you don't want
them running in your enterprise.
More likely, the other side hasn't a clue on how to configure named
instances or non-standard ports. Obviously, they have never worked with any
other DBMSes like Oracle or DB2, which all run, and make recommendations to
run, under non-standard ports, as a security measure.
SERVER = "MyServer\NamedInstanceN" is equivalent to SERVER =
"MyServer,PortN" where the former relies on dynamic discovery (UDP 1134)
while the latter is explicit.
I do not like embedding configuration parameters within code: SERVER =
"MyServerIPAddress,PortN" would work as well but defeats the purpose of
abstracting the name resolution.
You would be better off configuring your clients using SQL Server
client-side aliases (akin to OS host files) than to bury dynamic properties
within static code.
Sincerely,
Anthony Thomas

"ipconfig2" <ipconfig2@.discussions.microsoft.com> wrote in message
news:4F279F5A-E540-49D2-92C4-37E171D19719@.microsoft.com...
> Hi Anthony
> I cannot set the static port - it goes back to the dynamically set port
when
> I have changed it. The manual is BOL and Help file of SSCM. I have another
> cluster where this is no problem so I wondered if there is a bug somewhere
in[vbcol=seagreen]
> the software. I am using version 2153.
> I want all my instances to use port 1433 since there are applications that
> have hardcoded port 1433 as database port.
> Regards
> Rune
> "Anthony Thomas" wrote:
use[vbcol=seagreen]
when[vbcol=seagreen]
So,[vbcol=seagreen]
it's[vbcol=seagreen]
is[vbcol=seagreen]
to[vbcol=seagreen]
server[vbcol=seagreen]
to[vbcol=seagreen]
service it[vbcol=seagreen]