Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...
SQL Server Forum / DB Engine / SQL Server / June 2008

Tip: Looking for answers? Try searching our database.

SQL Server 2005 Cluster - Non-default Port

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
JP - 26 Jun 2008 03:56 GMT
I have SQL Server 2005 on a 2 node Cluster, the default port number has been
changed.  However SQL Server accepts connections thru the default port 1433
and the non-default port as well.  There are no aliases defined.  How do I
configure SQL Server to listen on the non-default port only?  Thanks.

Signature

Regards,
JP

Reply to this Message
Uri Dimant - 26 Jun 2008 05:50 GMT
JP
Specify in connection string ServerName,2333

>I have SQL Server 2005 on a 2 node Cluster, the default port number has
>been
> changed.  However SQL Server accepts connections thru the default port
> 1433
> and the non-default port as well.  There are no aliases defined.  How do I
> configure SQL Server to listen on the non-default port only?  Thanks.
Reply to this Message
JP - 26 Jun 2008 14:43 GMT
Uri,

After changing the default PortNumber, I should be able to connect to the
SQL Server, ONLY by using <ServerName>,<Non-DefaultPortNumber>.  But to my
surprise I am able to connect to the SQL Server even without specifying the
PortNumber in the connection string which is odd because on our Non-Clustered
Servers, trying to connect without the PortNumber in the connection string
throws an error.

By the way I have installed only <Default> instance, no named instance.  The
log file states that SQL Server is listening to the non-default PortNumber.

Signature

Regards,
JP

> JP
> Specify in connection string ServerName,2333
[quoted text clipped - 5 lines]
> > and the non-default port as well.  There are no aliases defined.  How do I
> > configure SQL Server to listen on the non-default port only?  Thanks.
Reply to this Message
Linchi Shea - 26 Jun 2008 14:47 GMT
The client is able to connect to the non-default port without explicitly
specifying the port number because of the SQL Browser sevice. You can try to
stop SQL Browser service on the server, and try to connect again.

Linchi

> Uri,
>
[quoted text clipped - 17 lines]
> > > and the non-default port as well.  There are no aliases defined.  How do I
> > > configure SQL Server to listen on the non-default port only?  Thanks.
Reply to this Message
Tracy McKibben (http://www.realsqlguy.com) - 26 Jun 2008 15:13 GMT
On Jun 26, 8:47 am, Linchi Shea <LinchiS...@discussions.microsoft.com>
wrote:
> The client is able to connect to the non-default port without explicitly
> specifying the port number because of the SQL Browser sevice. You can try to
> stop SQL Browser service on the server, and try to connect again.

OR, you have an alias defined on the client that is handling the port
specification for you....
Reply to this Message
JP - 26 Jun 2008 20:01 GMT
Tracy,

No I don't have the Aliases defined.

Signature

Regards,
JP

"Tracy McKibben (http://www.realsqlguy.co" wrote:

> On Jun 26, 8:47 am, Linchi Shea <LinchiS...@discussions.microsoft.com>
> wrote:
[quoted text clipped - 4 lines]
> OR, you have an alias defined on the client that is handling the port
> specification for you....
Reply to this Message
JP - 26 Jun 2008 19:59 GMT
Linchi,

I stopped the SQL Browser service and disabled it on both the Cluster Nodes.
The client can still connect to Non-Default Port without explicitly
specifying the PortNumber in the connection string.

Any other suggestions?

Signature

Regards,
JP

> The client is able to connect to the non-default port without explicitly
> specifying the port number because of the SQL Browser sevice. You can try to
[quoted text clipped - 23 lines]
> > > > and the non-default port as well.  There are no aliases defined.  How do I
> > > > configure SQL Server to listen on the non-default port only?  Thanks.
Reply to this Message
Matthew Bando - 30 Jun 2008 15:25 GMT
Look at your SQL Server log and see what ports get listed from the start up
logging part of the log.  It should list all port numbers that your server is
listening on.

Also, you have followed all the steps shown here:

http://msdn.microsoft.com/en-us/library/ms177440.aspx

including turning off the dynamic ports?

Just trying to figure out what's going on.

Thanks,

Matt

> Linchi,
>
[quoted text clipped - 31 lines]
> > > > > and the non-default port as well.  There are no aliases defined.  How do I
> > > > > configure SQL Server to listen on the non-default port only?  Thanks.
Reply to this Message
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.