Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

SQL 2005 Not Using Configured Port

  
   Database Forums (Home) -> Connect RSS
Next:  TDS, RPC malformed packets with SQL Server 2005  
Author Message
Aaron Sanders

External


Since: Dec 12, 2006
Posts: 2



(Msg. 1) Posted: Thu Feb 14, 2008 8:06 am
Post subject: SQL 2005 Not Using Configured Port
Archived from groups: microsoft>public>sqlserver>connect (more info?)
I have a SQL Server 2005 cluster. when I open the configuration manager and
look at the ports configured for TCP/IP, it shows 1433. Yet, when I try to
connect using Management Studio from another machine, it can't connect on
port 1433. I used SQL Ping to scan the server, and it appears that SQL Server
is running on port 1437, and if I use 1437 in Management Studio, I can
connect. I don't understand why the configruation would show 1433 but it
would be running on a different port. Anyone else see this before?

 >> Stay informed about: SQL 2005 Not Using Configured Port 
Back to top
Login to vote
"Rick Byham,

External


Since: Jan 15, 2007
Posts: 80



(Msg. 2) Posted: Thu Feb 14, 2008 9:39 am
Post subject: Re: SQL 2005 Not Using Configured Port [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
I have seen something similar on my laptop, when I go to another building
and pick up a different IP address for the wireless port. SQL Server
sometimes doesn't understand that ports can change after installation. Try
restarting the SQL Server Browser service. That might solve the connection
problem.
As to why SQL Server doesn't start on the specified port, my guesses are
1) that you are not looking at the port for the cluster IP address
2) that you have a named instance using dynamic ports
3) that someone changed to port number in Configuration Manager but didn't
restart SQL Server
Of course you may have checked all this already.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Aaron Sanders" wrote in message

>I have a SQL Server 2005 cluster. when I open the configuration manager and
> look at the ports configured for TCP/IP, it shows 1433. Yet, when I try to
> connect using Management Studio from another machine, it can't connect on
> port 1433. I used SQL Ping to scan the server, and it appears that SQL
> Server
> is running on port 1437, and if I use 1437 in Management Studio, I can
> connect. I don't understand why the configruation would show 1433 but it
> would be running on a different port. Anyone else see this before?

 >> Stay informed about: SQL 2005 Not Using Configured Port 
Back to top
Login to vote
Aaron Sanders

External


Since: Dec 12, 2006
Posts: 2



(Msg. 3) Posted: Thu Feb 14, 2008 10:42 am
Post subject: Re: SQL 2005 Not Using Configured Port [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Thank you for the helpful suggestions. It actually ended up being the dynamic
port. It's a multi-instance failover clusterwith named instances, something I
didn't have a lot of detailed experience with before. And some programs, like
Management Studio, are either using shared memory, or when remote, are smart
enough to find the correct port without specifying it. So I didn't realize
that the port was different, and didn't notice the separate configuration for
dynamic port. But some other applications I'm trying to install needed the
port specified. Thanks for the help!

"Rick Byham, (MSFT)" wrote:

> I have seen something similar on my laptop, when I go to another building
> and pick up a different IP address for the wireless port. SQL Server
> sometimes doesn't understand that ports can change after installation. Try
> restarting the SQL Server Browser service. That might solve the connection
> problem.
> As to why SQL Server doesn't start on the specified port, my guesses are
> 1) that you are not looking at the port for the cluster IP address
> 2) that you have a named instance using dynamic ports
> 3) that someone changed to port number in Configuration Manager but didn't
> restart SQL Server
> Of course you may have checked all this already.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Aaron Sanders" wrote in message
>
> >I have a SQL Server 2005 cluster. when I open the configuration manager and
> > look at the ports configured for TCP/IP, it shows 1433. Yet, when I try to
> > connect using Management Studio from another machine, it can't connect on
> > port 1433. I used SQL Ping to scan the server, and it appears that SQL
> > Server
> > is running on port 1437, and if I use 1437 in Management Studio, I can
> > connect. I don't understand why the configruation would show 1433 but it
> > would be running on a different port. Anyone else see this before?
>
 >> Stay informed about: SQL 2005 Not Using Configured Port 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
who uses port 1709 - Hello, I set up a new SQL 2005 SP1 server. Everything was fine for 2 weeks. Suddently I got error "cannot generate SSPI context" when connecting to it from a client PC, as shown below. When I use setspn to check the server I see the line...

Cannot bind to port 1433 - I have an instance of SQL Server that gets recycled every night (SQL 2000 sp4, windows 2000 sp4). Every couple of weeks or so users can't connect in the morning, and I see in the SQL log the error message 'SuperSocket Info: Bind failed on TCP port..

Specifying Port SQL Server 2000 Listens On - I need to change the port SQL Server 2000 Listens on to 6521 I have went into the SQL Server Utility and changed the port to 6521 I have also added this port to windows firewall exception list. However when I restart SQL Server, and run..

SQL Server running on a different port. - Hello! I am trying to understand how connections are made to a SQL Server when the server is running on a different port. My SQL Server 2000 SP4 is configured to listen on port 465 for TCP/IP. I used the server network utility. My client has no idea....

Port forwarding on SQL Server - Hi, I am trying to set up port forwarding to my SQL Server 7 box (NT 4) so I can remove its external IP. I can access SQL Server on that box via the internal IP and its current external IP, but not via port forwarding. I set up a routing record this....
   Database Forums (Home) -> Connect All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]