December 9, 2003 at 11:01 am
I have 2 instances on my DB Server. One is default and second is called QA. I can connect to my default without setting anything in the "Client Network Utility", but I need to set up "Named Pipes" as the protocol for the QA instance.
Here is what I tried:
1. Default is listening on 1433 and QA on 1455. Can connect to default but not to QA.
2. Changed the port of the default instance to 1455. Tried to connect, it connects via Query Analyzer. (There is no entry when I look at "Client Network Utility"
3. I change the QA instance to listen on 1433. Tried to connect, cannot connect. (Still no entry in "Client Network Utility"
4. I put an entry in "Client Network Utility" to use named pipes for QA and I can connect to it.
What am I missing? I wish to know what am I doing wrong that I cannot connect to this QA instance via TCP/IP (or with no extra configuration).
Thanks for your time
CB
December 9, 2003 at 1:30 pm
If the default was already listening on 1433, when you restarted the named instance, it wouldn't have been able to bind to port 1433. Hene the reason you can't connect to it.
Choose a different port. See if that port is in use on the system by running the following from the command prompt:
netstat -an | findstr :<port>
If you get anything back where the Proto is TCP and the Local Address has that port number, choose a different port number and run netstat again to see if that port is in use.
Change to the new port and restart the service. Then check the event logs and the SQL Server log to see if it SQL Server had trouble binding to the port. This is what usually happens.
K. Brian Kelley, GSEC
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply