Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


After changing port on a cluster the proper way, default connection without port specified still...


After changing port on a cluster the proper way, default connection without port specified still working

Author
Message
GabyYYZ
GabyYYZ
Say Hey Kid
Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)

Group: General Forum Members
Points: 673 Visits: 2332
I have a strange issue on a SQL 2008 cluster (non-R2) that I changed the default port on. I went ahead and followed the instructions in this link and this one as well.

The change was from 1433 to 1599 and after following the instructions about removing checkpoints, changing IP on both nodes, and adding back the checkpoints, I verified via the log file the message: Server is listening to [XXX.XXX.XXX.XXX <ipv4> 1599]

I also took the liberty of disabling SQL Browser on both nodes.

The strangeness occurs when connecting from Management Studio. When connecting to the SQL Name without a port after, it resolves the port. I thought somehow that 1433 was still active, but when I connected to ServerName,1433 via Management Studio, the connection failed as it should. When I connected to ServerName,1599, the new port, it worked. But connecting just to ServerName resolved the connection, although I did notice there was a slight delay, almost as if something on the back end was taking an extra step to resolve.

Is there any way to permanently disable the default behavior, meaning I would require all connections, even those from Management Studio, to specify the correct port? Thanks very much.

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

GabyYYZ
GabyYYZ
Say Hey Kid
Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)

Group: General Forum Members
Points: 673 Visits: 2332
Attached are three lines that might be important from the Errorlog. Not sure if the \pipe connections matter.

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

Attachments
port.JPG (15 views, 24.00 KB)
GabyYYZ
GabyYYZ
Say Hey Kid
Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)

Group: General Forum Members
Points: 673 Visits: 2332
Anyone? :-(

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

DeadScorpius
DeadScorpius
SSC Journeyman
SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)SSC Journeyman (87 reputation)

Group: General Forum Members
Points: 87 Visits: 399
SQL Browser service turned on possibly?
GabyYYZ
GabyYYZ
Say Hey Kid
Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)

Group: General Forum Members
Points: 673 Visits: 2332
DeadScorpius (8/2/2013)
SQL Browser service turned on possibly?

No, it's off...it seems that 1433 indeed was not listening. However, we had to let the network admins open up our new port. If you don't, SQL was resolving through port 445, SMB. It connected, but was slow. Once he opened up the new port, everything went well.

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search