Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
AyadThey dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
Ayad
They dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing server name

Hi. Sorry to be asking this. I know there is a KB article with the steps for changing a SQL2K server name, but I can't find it for the life of me.
Anyone have it tagged?
TIASearch for "Renaming a SQL Server in Books Online. Should give you everything you need. I have even tried it myself, so I know it works.|||Try http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp|||Thanks foks. Why did I not think of BOL? I actually had it open under the dbForums window. DOH!

Changing from Administration Mode to Application Mode

I have a W2K server hosting SQL2K and have need to switch it to running in A
pplication mode as the number of remote SQL users has made it difficult to w
ork with only 2 allowed connections as in Administration mode. I am wonderi
ng what the best practice/m
ethod to use to go about accomplishing this task with the least disruption t
o the SQL server (as when I was about to do it I received an error message i
ndicating that SQL would break). Thanks for a quick response.Terminal services probably shouldn't be on the same box as SQL if you want
to run application mode, but the warning you are likely getting is not
neccesarily going to break SQL but since it was installed before App mode
Terminal services were enabled it thinks that this app will need to be
reinstalled to take advantage of Application mode terminal services.
I would purchase a copy of VMware (my favourite tool of all time
www.vmware.com ) and try it out. install a VM session, install Win2k OS into
it, enable term services in admin mode, install SQL and then flip it to app
mode. see what happens.
My guess is you will be fine, but the most impact would be a reboot so a
weekender would be a good idea, but this is a change I would recommend
against. it will adversely affect performance... my $0.02
Neil MacMurchy
"FColvais" <fcolvais1@.comcast.net> wrote in message
news:758C7A26-D01B-4228-89E0-3BB33205560F@.microsoft.com...
> I have a W2K server hosting SQL2K and have need to switch it to running in
Application mode as the number of remote SQL users has made it difficult to
work with only 2 allowed connections as in Administration mode. I am
wondering what the best practice/method to use to go about accomplishing
this task with the least disruption to the SQL server (as when I was about
to do it I received an error message indicating that SQL would break).
Thanks for a quick response.