July 28, 2013 at 3:21 am
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[/url] 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
July 28, 2013 at 3:27 am
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
July 29, 2013 at 6:43 am
Anyone? 🙁
Gaby________________________________________________________________"In theory, theory and practice are the same. In practice, they are not." - Albert Einstein
August 2, 2013 at 2:11 pm
SQL Browser service turned on possibly?
August 6, 2013 at 2:39 pm
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply