Changing the port that Reporting Services 2000 is running on after activation.

Hi,

I have just installed reporting services 2000 on a non-standard port and have used the rsactivate tool to activate it.

I then installed Microsoft CRM which seems not to like the non-standard port for reporting services, how do I go about deactivating the webservice so I can change the port and then activate it again?

Thanks

I am not too familiar with RS2000, but I think all you have to do is to change the port in IIS, then change the url in the report server and report manager config files. You do not need to run reactivate again.

changing the internet port number of MS RS Server

I tried to change the MS RS Server port from 80 to let's say 8080. But when
going back to MS RS home page I have an error page from MS RS with the
following message :
"The underlying connection was closed: Unable to connect to the remote
server."
I can't solve this
Could anybody help me.
Regards,
PS: OS is Win2K all Windows Updates, and IIS5Make sure to update the url in RSWebapplication.config to use the new port.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"jcredk" <jcredk@.discussions.microsoft.com> wrote in message
news:2F53430B-20F3-4BB4-A51F-2E60F5074592@.microsoft.com...
> I tried to change the MS RS Server port from 80 to let's say 8080. But
when
> going back to MS RS home page I have an error page from MS RS with the
> following message :
> "The underlying connection was closed: Unable to connect to the remote
> server."
> I can't solve this
> Could anybody help me.
> Regards,
> PS: OS is Win2K all Windows Updates, and IIS5
>|||Hi,
Thanks a lot that was the key I was searching.
Quick test has worked. I was accessing the homepage for reports ..!
"Daniel Reib [MSFT]" wrote:
> Make sure to update the url in RSWebapplication.config to use the new port.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "jcredk" <jcredk@.discussions.microsoft.com> wrote in message
> news:2F53430B-20F3-4BB4-A51F-2E60F5074592@.microsoft.com...
> > I tried to change the MS RS Server port from 80 to let's say 8080. But
> when
> > going back to MS RS home page I have an error page from MS RS with the
> > following message :
> > "The underlying connection was closed: Unable to connect to the remote
> > server."
> >
> > I can't solve this
> >
> > Could anybody help me.
> >
> > Regards,
> >
> > PS: OS is Win2K all Windows Updates, and IIS5
> >
>
>|||I try this,
but now i have a blank default page, with no poosibility ton configure
anything,
i have just Home, My subscription, help menu
no menu to add directory or ton configure security.
I have forgotten something ?
Thanks.
Bruno
"jcredk" wrote:
> Hi,
> Thanks a lot that was the key I was searching.
> Quick test has worked. I was accessing the homepage for reports ..!
> "Daniel Reib [MSFT]" wrote:
> > Make sure to update the url in RSWebapplication.config to use the new port.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "jcredk" <jcredk@.discussions.microsoft.com> wrote in message
> > news:2F53430B-20F3-4BB4-A51F-2E60F5074592@.microsoft.com...
> > > I tried to change the MS RS Server port from 80 to let's say 8080. But
> > when
> > > going back to MS RS home page I have an error page from MS RS with the
> > > following message :
> > > "The underlying connection was closed: Unable to connect to the remote
> > > server."
> > >
> > > I can't solve this
> > >
> > > Could anybody help me.
> > >
> > > Regards,
> > >
> > > PS: OS is Win2K all Windows Updates, and IIS5
> > >
> >
> >
> >|||Did you try to reset iis using command IISReset ?
Most of the times simply restarting IIS does not force IIS to read/reflect
registry or config changes.
I had same problem on CRM server using SRS after changing some of IIS
configuration, this trick resolved it.
"jcredk" wrote:
> I tried to change the MS RS Server port from 80 to let's say 8080. But when
> going back to MS RS home page I have an error page from MS RS with the
> following message :
> "The underlying connection was closed: Unable to connect to the remote
> server."
> I can't solve this
> Could anybody help me.
> Regards,
> PS: OS is Win2K all Windows Updates, and IIS5
>sql

changing the default port on a clustered 2005 server.

I am unclear as to which Ip address to change the standard port on. When setting up a cluster you have multiple IP address's including the nic that is used for the heartbeat. I have not found any documention on how to change both nodes to listen on a port other than 1433..

Any help would be greatly appreciated.

Set the one titled "IPAll" (you may need to scroll to the bottom of the list). The clustered SQL Server instance will apply it to the actual IP addresses of the cluster.

changing the default port on a clustered 2005 server.

I am unclear as to which Ip address to change the standard port on. When setting up a cluster you have multiple IP address's including the nic that is used for the heartbeat. I have not found any documention on how to change both nodes to listen on a port other than 1433..

Any help would be greatly appreciated.

Set the one titled "IPAll" (you may need to scroll to the bottom of the list). The clustered SQL Server instance will apply it to the actual IP addresses of the cluster.

Changing the default port number and still connecting

Hello,
I have SQL Server 2000 Enterprise Edition, and I'd like to change the
default port to something else (we'll use 2033 for this example). I've
tried to connect from another computer on the same subnet using
"ServerName:2033" as the server, but it doesn't connect. It will connect if
I change the Server to use the default port and change the server to connect
to on the client to "ServerName", but either I"m not referencing the new
port number properly or ?
Any help you could provide would be great.
Thanks In Advance!
Rick
Hi,
Stop all applications and Third party software services in the server.
After the applications and services are stopped, change the port and start
SQL Server
service. This should enable SQL Server to take control of new port. Open the
sql server error log and see if the new port is used.
See additional details from old post.
http://groups.google.co.in/groups?q=...ft.com&rnum=10
Thanks
Hari
SQL Server MVP
"RWC" <rcollens_SPAMONATOR_@.hemmingway.com> wrote in message
news:kUAde.1198452$8l.948157@.pd7tw1no...
> Hello,
> I have SQL Server 2000 Enterprise Edition, and I'd like to change the
> default port to something else (we'll use 2033 for this example). I've
> tried to connect from another computer on the same subnet using
> "ServerName:2033" as the server, but it doesn't connect. It will connect
if
> I change the Server to use the default port and change the server to
connect
> to on the client to "ServerName", but either I"m not referencing the new
> port number properly or ?
> Any help you could provide would be great.
> Thanks In Advance!
> Rick
>
|||Hi
"ServerName, 2033" is the correct format.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"RWC" wrote:

> Hello,
> I have SQL Server 2000 Enterprise Edition, and I'd like to change the
> default port to something else (we'll use 2033 for this example). I've
> tried to connect from another computer on the same subnet using
> "ServerName:2033" as the server, but it doesn't connect. It will connect if
> I change the Server to use the default port and change the server to connect
> to on the client to "ServerName", but either I"m not referencing the new
> port number properly or ?
> Any help you could provide would be great.
> Thanks In Advance!
> Rick
>
>
|||You're a GENIUS man! ;)
Thanks Mike, that worked like a charm. (I figured it would be the
connection syntax).
Thanks again!
Rick
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:C7FAFA8A-7B27-4E48-88CB-90E00FF63573@.microsoft.com...[vbcol=seagreen]
> Hi
> "ServerName, 2033" is the correct format.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "RWC" wrote:

Changing the default port number and still connecting

Hello,
I have SQL Server 2000 Enterprise Edition, and I'd like to change the
default port to something else (we'll use 2033 for this example). I've
tried to connect from another computer on the same subnet using
"ServerName:2033" as the server, but it doesn't connect. It will connect if
I change the Server to use the default port and change the server to connect
to on the client to "ServerName", but either I"m not referencing the new
port number properly or '
Any help you could provide would be great.
Thanks In Advance!
RickHi,
Stop all applications and Third party software services in the server.
After the applications and services are stopped, change the port and start
SQL Server
service. This should enable SQL Server to take control of new port. Open the
sql server error log and see if the new port is used.
See additional details from old post.
gVBHA.237%40cppssbbsa01.microsoft.com&rnum=10" target="_blank">http://groups.google.co.in/groups?q...oft.com&rnum=10
Thanks
Hari
SQL Server MVP
"RWC" <rcollens_SPAMONATOR_@.hemmingway.com> wrote in message
news:kUAde.1198452$8l.948157@.pd7tw1no...
> Hello,
> I have SQL Server 2000 Enterprise Edition, and I'd like to change the
> default port to something else (we'll use 2033 for this example). I've
> tried to connect from another computer on the same subnet using
> "ServerName:2033" as the server, but it doesn't connect. It will connect
if
> I change the Server to use the default port and change the server to
connect
> to on the client to "ServerName", but either I"m not referencing the new
> port number properly or '
> Any help you could provide would be great.
> Thanks In Advance!
> Rick
>|||Hi
"ServerName, 2033" is the correct format.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"RWC" wrote:

> Hello,
> I have SQL Server 2000 Enterprise Edition, and I'd like to change the
> default port to something else (we'll use 2033 for this example). I've
> tried to connect from another computer on the same subnet using
> "ServerName:2033" as the server, but it doesn't connect. It will connect
if
> I change the Server to use the default port and change the server to conne
ct
> to on the client to "ServerName", but either I"m not referencing the new
> port number properly or '
> Any help you could provide would be great.
> Thanks In Advance!
> Rick
>
>|||You're a GENIUS man! ;)
Thanks Mike, that worked like a charm. (I figured it would be the
connection syntax).
Thanks again!
Rick
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:C7FAFA8A-7B27-4E48-88CB-90E00FF63573@.microsoft.com...[vbcol=seagreen]
> Hi
> "ServerName, 2033" is the correct format.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "RWC" wrote:
>

Changing the default port number and still connecting

Hello,

I have SQL Server 2000 Enterprise Edition, and I'd like to change the
default port to something else (we'll use 2033 for this example). I've
tried to connect from another computer on the same subnet using
"ServerName:2033" as the server, but it doesn't connect. It will connect if
I change the Server to use the default port and change the server to connect
to on the client to "ServerName", but either I"m not referencing the new
port number properly or ??

Any help you could provide would be great.

Thanks In Advance!
RickHi,

Stop all applications and Third party software services in the server.
After the applications and services are stopped, change the port and start
SQL Server
service. This should enable SQL Server to take control of new port. Open the
sql server error log and see if the new port is used.

See additional details from old post.

http://groups.google.co.in/groups?q...oft.com&rnum=10

Thanks
Hari
SQL Server MVP

"RWC" <rcollens_SPAMONATOR_@.hemmingway.com> wrote in message
news:kUAde.1198452$8l.948157@.pd7tw1no...
> Hello,
> I have SQL Server 2000 Enterprise Edition, and I'd like to change the
> default port to something else (we'll use 2033 for this example). I've
> tried to connect from another computer on the same subnet using
> "ServerName:2033" as the server, but it doesn't connect. It will connect
if
> I change the Server to use the default port and change the server to
connect
> to on the client to "ServerName", but either I"m not referencing the new
> port number properly or ??
> Any help you could provide would be great.
> Thanks In Advance!
> Ricksql

Changing the Default Port

Is it possible to change the default port of 1433 for Sql Server after the
database has been installed? If so, can someone point me in the right
direction?Use Server Server Network Utility
"Simon" <nospam@.nospam.nospam> wrote in message
news:%23$HR7tzuDHA.2448@.TK2MSFTNGP09.phx.gbl...
> Is it possible to change the default port of 1433 for Sql Server after the
> database has been installed? If so, can someone point me in the right
> direction?
>|||Yes. You can do this from the Server Network Utility program. Select the
TCP/IP netlib and then click properties.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Simon" <nospam@.nospam.nospam> wrote in message
news:%23$HR7tzuDHA.2448@.TK2MSFTNGP09.phx.gbl...
> Is it possible to change the default port of 1433 for Sql Server after the
> database has been installed? If so, can someone point me in the right
> direction?
>|||Duh... Brian, thank you!
BTW, great articles in SQL Server magazine!
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:O9oOSxzuDHA.620@.TK2MSFTNGP10.phx.gbl...
> Yes. You can do this from the Server Network Utility program. Select the
> TCP/IP netlib and then click properties.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Simon" <nospam@.nospam.nospam> wrote in message
> news:%23$HR7tzuDHA.2448@.TK2MSFTNGP09.phx.gbl...
> >
> > Is it possible to change the default port of 1433 for Sql Server after
the
> > database has been installed? If so, can someone point me in the
right
> > direction?
> >
> >
>|||I'm glad you enjoy them!
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Simon" <nospam@.nospam.nospam> wrote in message
news:ebG5A2zuDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Duh... Brian, thank you!
> BTW, great articles in SQL Server magazine!
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in message
> news:O9oOSxzuDHA.620@.TK2MSFTNGP10.phx.gbl...
> > Yes. You can do this from the Server Network Utility program. Select the
> > TCP/IP netlib and then click properties.
> >
> > --
> >
> > Brian Moran
> > Principal Mentor
> > Solid Quality Learning
> > SQL Server MVP
> > http://www.solidqualitylearning.com
> >
> >
> > "Simon" <nospam@.nospam.nospam> wrote in message
> > news:%23$HR7tzuDHA.2448@.TK2MSFTNGP09.phx.gbl...
> > >
> > > Is it possible to change the default port of 1433 for Sql Server after
> the
> > > database has been installed? If so, can someone point me in the
> right
> > > direction?
> > >
> > >
> >
> >
>

changing TCP/IP port breaks "local" connection

Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIA
check 1434
and
delete
HKLM\software\microsoft\mssqlserver\client\superso cketnetlib\lastconnect key
<sql server name or ip>
"vze78se7@.verizon.net" wrote:

> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>
|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:

>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.

>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supers ocketnetlib\lastconnect key
><sql server name or ip>
I will try that, thanks.
[vbcol=seagreen]
>"vze78se7@.verizon.net" wrote:
|||
>check 1434
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supers ocketnetlib\lastconnect key
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?
|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:

>
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>

changing TCP/IP port breaks "local" connection

Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
I will try that, thanks.
>"vze78se7@.verizon.net" wrote:
>> Hi All:
>> I wanted to change the TCP/IP port a default instance of SQL was
>> running on (from 1433 to something random like 49576) on Win2K AS
>> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
>> MDAC 2.8 is installed.
>> The server has a base IP of 192.168.1.190 and a website running on
>> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
>> database using "local" for the server name.
>> This all runs fine when the SQL server's on 1433, but if I change it
>> to another port, it breaks the connection from the website to the SQL
>> server. Restarting services doesn't help, even rebooting doesn't
>> restore the connection. If I switch the SQL Server back to 1433 it
>> runs fine.
>> I tested the same thing on a server running Win2003, and the website
>> didn't have a problem connecting to the SQL server when I changed the
>> TCP/IP port.
>> Any ideas why this breaks on Win2K?
>> TIA|||>check 1434
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
> >check 1434
> >and
> >delete
> >HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
> ><sql server name or ip>
> >
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>sql

changing TCP/IP port breaks "local" connection

Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect ke
y
<sql server name or ip>
"vze78se7@.verizon.net" wrote:

> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:

>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.

>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
I will try that, thanks.
[vbcol=seagreen]
>"vze78se7@.verizon.net" wrote:
>|||
>check 1434
>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:

>
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>

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 SQL Port

Sorry for the bonehead questions, but how do I go about changing the SQL 200
5
port of 1433? Also, does it matter what I change it to, as long as its in
between 0-65,535?You can change the port in the SQL Server Configuration Manager tool, using
the Protocols for MSSQLSERVER folder and the TCP/IP properties dialog.
To find used ports which need avoiding you can use "NETSTAT -an" from the
command line, or check with your network guys.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hi,
To add on to Paul; After changing the port just restart the SQL Server
service to make the new port to listen on.
Thanks
Hari
SQL Server MVP
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uda07%23$zGHA.4116@.TK2MSFTNGP02.phx.gbl...
> You can change the port in the SQL Server Configuration Manager tool,
> using the Protocols for MSSQLSERVER folder and the TCP/IP properties
> dialog.
> To find used ports which need avoiding you can use "NETSTAT -an" from the
> command line, or check with your network guys.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Changing SQL Port

Sorry for the bonehead questions, but how do I go about changing the SQL 2005
port of 1433? Also, does it matter what I change it to, as long as its in
between 0-65,535?You can change the port in the SQL Server Configuration Manager tool, using
the Protocols for MSSQLSERVER folder and the TCP/IP properties dialog.
To find used ports which need avoiding you can use "NETSTAT -an" from the
command line, or check with your network guys.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hi,
To add on to Paul; After changing the port just restart the SQL Server
service to make the new port to listen on.
Thanks
Hari
SQL Server MVP
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uda07%23$zGHA.4116@.TK2MSFTNGP02.phx.gbl...
> You can change the port in the SQL Server Configuration Manager tool,
> using the Protocols for MSSQLSERVER folder and the TCP/IP properties
> dialog.
> To find used ports which need avoiding you can use "NETSTAT -an" from the
> command line, or check with your network guys.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Changing port numbers

On an active/active cluster what is the proper way of changing the port # on
the named instance after an install is complete and in use.
Use the Server Network Utility to assign a new port number. The utility is
not cluster-aware so make the changes on all nodes in the cluster
individually. SQL server requires a service stop-start to change port
numbers.
Geoff N, Hiten
Microsoft SQL Server MVP
"zach_john" <zach_john@.discussions.microsoft.com> wrote in message
news:01F5E155-2002-4C8A-8549-80DA732C7B7F@.microsoft.com...
> On an active/active cluster what is the proper way of changing the port #
> on
> the named instance after an install is complete and in use.
|||Thanks Geoff - just wanted to hear that confirmation.
Cheers,
Zach
"Geoff N. Hiten" wrote:

> Use the Server Network Utility to assign a new port number. The utility is
> not cluster-aware so make the changes on all nodes in the cluster
> individually. SQL server requires a service stop-start to change port
> numbers.
> Geoff N, Hiten
> Microsoft SQL Server MVP
> "zach_john" <zach_john@.discussions.microsoft.com> wrote in message
> news:01F5E155-2002-4C8A-8549-80DA732C7B7F@.microsoft.com...
>
>
|||It's always easier to learn from someone else's mistakes.
GNH
"zach_john" <zach_john@.discussions.microsoft.com> wrote in message
news:9C40F75E-2E21-4026-9A34-CF4857CF78DD@.microsoft.com...[vbcol=seagreen]
> Thanks Geoff - just wanted to hear that confirmation.
> Cheers,
> Zach
> "Geoff N. Hiten" wrote:

Changing Default SQL ports on SQL 2000 Server

Hi Group,
As part of best practices we would like to change the default port number
that SQL Server 2000 listens on.
Once this has been done, can the application client dynamically determine
the new port number using the SQL Server Reporting Service listening on udp
1434?
Please note that Named Pipes are being used to establish the connections and
that there is a firewall between the SQL Server and the
applications clients.
Regards
CMHi,
Just change the port via the SQL Server Network Utility. On the client
open the Client Network Utility and create a TCP/IP based alias that
dynamically determines the port. The client will then use port 1434 to
determine which port it needs to use. Make sure that your firewall has
both port 1434 and the port the SQL Server instance is listening on open.
Jonathan
CP wrote:
> Hi Group,
> As part of best practices we would like to change the default port number
> that SQL Server 2000 listens on.
> Once this has been done, can the application client dynamically determine
> the new port number using the SQL Server Reporting Service listening on ud
p
> 1434?
> Please note that Named Pipes are being used to establish the connections a
nd
> that there is a firewall between the SQL Server and the
> applications clients.
> Regards
> CM
>|||Hi Jonathan,
Thank you for your response. Can I still do this (creating the TCP/IP based)
if I am using Named Pipes as my connector on the client?
I have read a post somewhere that Named Pipes cannot dynamically determine
destination SQL port numbers in SQL Server 2000.
Regards
CM
"JPD" wrote:

> Hi,
> Just change the port via the SQL Server Network Utility. On the client
> open the Client Network Utility and create a TCP/IP based alias that
> dynamically determines the port. The client will then use port 1434 to
> determine which port it needs to use. Make sure that your firewall has
> both port 1434 and the port the SQL Server instance is listening on open.
> Jonathan
>
> CP wrote:
>|||Hi,
In your case you need to do nothing on the clients. Named Pipes on the
client will be able to negotiate a connection with the server.
Jonathan
CP wrote:[vbcol=seagreen]
> Hi Jonathan,
> Thank you for your response. Can I still do this (creating the TCP/IP base
d)
> if I am using Named Pipes as my connector on the client?
> I have read a post somewhere that Named Pipes cannot dynamically determine
> destination SQL port numbers in SQL Server 2000.
> Regards
> CM
> "JPD" wrote:
>|||Hi Jonathan,
Thank you again for your reply.
I am a bit confused here, as I had the understanding that Named Pipes and
TCP/IP were two different connectivity mechanisms and that if Named Pipes ar
e
used in SQL 2000, the connections will fail if the default port is changed a
s
Named Pipes in SQL 2000 cannot dynamically determine destination port number
s.
Regards
CM
"JPD" wrote:

> Hi,
> In your case you need to do nothing on the clients. Named Pipes on the
> client will be able to negotiate a connection with the server.
> Jonathan
>
>
> CP wrote:
>

Changing default port

I know this is not rocket science but I can't get it done. Used the Network
Utility to change the default port but SQL still says still listening on
1433. Stped-restarted the instance and then the entire server. Nothing else
is using the new port....netstat, Port Query, show nothing connected. Any
ideas?"Monty" <montysl@.nospam.hotmail.com> wrote in message
news:OqmQK1IgEHA.592@.TK2MSFTNGP11.phx.gbl...
> I know this is not rocket science but I can't get it done. Used the
Network
> Utility to change the default port but SQL still says still listening on
> 1433. Stped-restarted the instance and then the entire server. Nothing
else
> is using the new port....netstat, Port Query, show nothing connected. Any
> ideas?
That should have been enough to change the port assignment, check the
following article in case you missed something:
http://support.microsoft.com/defaul...kb;en-us;823938
Steve|||Just out of curiosity, are you using the Client Network Utility or the
Server Network Utility.
If it is the latter when you go back and check the setting does it reflect
the new value or 1433?
Rand
This posting is provided "as is" with no warranties and confers no rights.

CHanging default listing port sQL 7.0

How do I change th e default port SQL server 7.0 listens
to. I need some urgent asisstanceOpen up the server network utility (found in the SQL Server folder of the
start menu) and then highlight TCP and choose properties.
Andrew J. Kelly
SQL Server MVP
"lyle" <anonymous@.discussions.microsoft.com> wrote in message
news:1962a01c44ceb$bb9c1350$a501280a@.phx
.gbl...
> How do I change th e default port SQL server 7.0 listens
> to. I need some urgent asisstance

Changing default listening port

Hi,
I need to change the default listening port on sql server from 1433 to
another port. The server is being connected to by multiple web sites some
using DSN connections and others not and also via a number of connections
using Enterprise Manager. I'm worried that if I change the port, the
websites will not be able to connect. Can anyone give me some advice on what
will need to be changed to make this update smooth.
Many thanks,
Luke.You can create an alias on the client using "Client Network Utility" and there specify the port
number. Or, you can specify the port number in the server name/connection string. From memory, you
do like SERVERNAME;portnumber, I.e.:
MYSERVER;1067
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Luke Fields" <lfields228@.hotmaik.com> wrote in message
news:egS7UeluDHA.2520@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I need to change the default listening port on sql server from 1433 to
> another port. The server is being connected to by multiple web sites some
> using DSN connections and others not and also via a number of connections
> using Enterprise Manager. I'm worried that if I change the port, the
> websites will not be able to connect. Can anyone give me some advice on what
> will need to be changed to make this update smooth.
> Many thanks,
> Luke.
>|||You can change the port SQL Server is listening on use the Server Network
Utility in the SQL Server program group. If there are firewalls between the
server and the clients you will need to open the new port on the firewall
so the traffic can get through.
Also if you are using dynamic discovery of the SQL Server on the network
UDP port 1434 will need to be opened as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.