locked
Help! Server not listening on 1433. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I have a SQL 2008 R2 Standard on Microsoft Server 2008 R2. I have configured it so that TCP/IP is enabled and set all the Dynamic ports to Blank and set the TCP Port to 1433 for all of the IP's including IPALL. I have made sure that remote connections are allowed is set for the server. Also enabled TCP/IP as a protocol. I try to telnet from the server itself to its IP address and the loopback address and it fails to connect. I also run netstat -aco and it doesnt look like the IP is listening on port 1433. It does show Local Address 0.0.0.0: 1433  Foreign Address 0.0.0.0:0 LISTENING though but that doesnt sound right. Any help would be MUCH appreciated.

     

    David

    Tuesday, January 10, 2012 10:14 PM

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote

    Hi DavidB1982,

    Regarding to your description, seems be a connectivity issue, please try verify the following issues as below:

    1. Check Network: Make sure the Network is workable and stable when you connect to SQL Server on a remote machine. You can test the Network connection using the PING grogram:
    ping <Server Name>

    2. Enable remote connections for SQL Server:
    a) In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for <instancename>.
    b) In the details pane, right-click one of the available protocols, and then click Properties.
    c) To enable the TCP/IP protocol (or named pipes) for remote connections, set the Enabled box to Yes.

    3. Enable the SQL Server Browser service:
    If you connect to a named instance, make sure the SQL Server Browser service by using SQL Server Configuration Manager is enable or specify the TCP port when connecting to it.

    4. Create an exception for SQL Server in Windows Firewall:
    If firewall is enabled on the server, you need to put TCP port number of the instance, such as 1433 for the default instance. Then add UDP 1434 for SQL Server Browser Service.

    For TCP / IP connectivity problem troubleshooting process as below, please follow the steps.

    1. Check the server name you used.
    For a named instance, you need to type computer name\instance name. For a default server, you only need to type computer name.
    For server Configuration, please use netstat command.  Run  “netstat -an”command in DOS windows. The "netstat-an" command output in the removal of the part of the SQL Server port number as following：
    Active Connections
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
      TCP    169.254.173.244:1433   169.254.173.244:3952   ESTABLISHED

    2. Client TCP/IP configuration
    In most cases you do not need to configure the client, because the TCP / IP protocol is enabled by default. You can use the Client Network Utility (or SQL Server Configuration Manger) to configure TCP / IP protocol. Run cliconfg.exe or from Start -> Programs -> Microsoft SQL Server -> Client Network Utility can be transferred out

    3. Verify that SQL Server is actually listening for TCP / IP protocol
    In order to verify that SQL Server does monitor the TCP / IP protocol, but also need to see the SQL Server errorlog file.
    If you find that SQL Server does not listen for TCP / IP protocol, use the server-side network configuration tool (run svrnetcn.exe ) to confirm whether the configured SQL Server monitor TCP / IP protocol.

    4. Check the network connectivity.
    To ensure that only the server can ping the IP address of SQL Server, SQL Server can ping the server name. If you ping the server name in question, indicating the DNS or WINS server configuration problem, you can in your HOSTS file (HOSTS file in the system32 \ drivers \ etc directory) and manually add server IP address as follows:
    169.254.173.244  MySQLserver
    If you have a problem with ping IP address, then check the configuration of the network including hardware connections. On the server and client are using "ipconfig / all" command to check the server and client are on the same network.

    5. Use the TELNET command to check the SQL listening port.
    To verify that SQL Server listening port, you can use the TELNET command. Assume that SQL Server's IP address is 192.168.1.1, port 1234, you can run the following command:
    TELNET 192.168.1.1 1234
    If the TELNET successful, then the result will be a only a black screen with cursor in flash. If unsuccessful, then you will get an error message. These error messages need to continue troubleshooting the issue.

    From the remote machine can you telnet to SQL server on the port SQL server is running. On remote machine, open command prompt and type: telnet <SQLServerHostName> <PortNumber>
    SQLServerHostName is either IP address or hostname of the remote computer where SQL serve is running PortNumber is port number SQL server is listening for default instance it is 1433 but check SQL server configuration manager to make sure.

    6. Check the SQL Server login user access.

    7. You can try to specify protocol and port to connect SQL Server in the Query Analyzer as below:  TCP:MySQLServer,1433
    Through this method can force the specified query analyzer using the TCP / IP connection to the server specified port.

    8. If it does not work for you, please try to use Network Monitor to capture trace to analysis. For more information about Network Monitor, please refer to this article

    Additional, please refer the articles as below:
    1.  TCP/IP port numbers required to communicate to SQL over a firewall: http://support.microsoft.com/?id=287932
    2. How to Troubleshoot Basic TCP/IP Problems: http://support.microsoft.com/kb/169790

    Regards,
    Amber zhang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    • Edited by amber zhang Thursday, January 12, 2012 6:22 AM
    • Marked as answer by DavidB1982 Monday, January 16, 2012 1:04 PM
    Thursday, January 12, 2012 6:22 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Forgot to mention that Windows Firewall is turned off so this would not be a issue. Also SQL Browser services are started.
    Tuesday, January 10, 2012 10:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I now have it listening on (IP Address of server):1433   0.0.0.0:0 LISTENING.

     

    I still cannot telnet from the server to the loopback OR the server name/IP address. Please any ideas?

    Tuesday, January 10, 2012 10:47 PM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Hi DavidB1982,

    Regarding to your description, seems be a connectivity issue, please try verify the following issues as below:

    1. Check Network: Make sure the Network is workable and stable when you connect to SQL Server on a remote machine. You can test the Network connection using the PING grogram:
    ping <Server Name>

    2. Enable remote connections for SQL Server:
    a) In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for <instancename>.
    b) In the details pane, right-click one of the available protocols, and then click Properties.
    c) To enable the TCP/IP protocol (or named pipes) for remote connections, set the Enabled box to Yes.

    3. Enable the SQL Server Browser service:
    If you connect to a named instance, make sure the SQL Server Browser service by using SQL Server Configuration Manager is enable or specify the TCP port when connecting to it.

    4. Create an exception for SQL Server in Windows Firewall:
    If firewall is enabled on the server, you need to put TCP port number of the instance, such as 1433 for the default instance. Then add UDP 1434 for SQL Server Browser Service.

    For TCP / IP connectivity problem troubleshooting process as below, please follow the steps.

    1. Check the server name you used.
    For a named instance, you need to type computer name\instance name. For a default server, you only need to type computer name.
    For server Configuration, please use netstat command.  Run  “netstat -an”command in DOS windows. The "netstat-an" command output in the removal of the part of the SQL Server port number as following：
    Active Connections
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
      TCP    169.254.173.244:1433   169.254.173.244:3952   ESTABLISHED

    2. Client TCP/IP configuration
    In most cases you do not need to configure the client, because the TCP / IP protocol is enabled by default. You can use the Client Network Utility (or SQL Server Configuration Manger) to configure TCP / IP protocol. Run cliconfg.exe or from Start -> Programs -> Microsoft SQL Server -> Client Network Utility can be transferred out

    3. Verify that SQL Server is actually listening for TCP / IP protocol
    In order to verify that SQL Server does monitor the TCP / IP protocol, but also need to see the SQL Server errorlog file.
    If you find that SQL Server does not listen for TCP / IP protocol, use the server-side network configuration tool (run svrnetcn.exe ) to confirm whether the configured SQL Server monitor TCP / IP protocol.

    4. Check the network connectivity.
    To ensure that only the server can ping the IP address of SQL Server, SQL Server can ping the server name. If you ping the server name in question, indicating the DNS or WINS server configuration problem, you can in your HOSTS file (HOSTS file in the system32 \ drivers \ etc directory) and manually add server IP address as follows:
    169.254.173.244  MySQLserver
    If you have a problem with ping IP address, then check the configuration of the network including hardware connections. On the server and client are using "ipconfig / all" command to check the server and client are on the same network.

    5. Use the TELNET command to check the SQL listening port.
    To verify that SQL Server listening port, you can use the TELNET command. Assume that SQL Server's IP address is 192.168.1.1, port 1234, you can run the following command:
    TELNET 192.168.1.1 1234
    If the TELNET successful, then the result will be a only a black screen with cursor in flash. If unsuccessful, then you will get an error message. These error messages need to continue troubleshooting the issue.

    From the remote machine can you telnet to SQL server on the port SQL server is running. On remote machine, open command prompt and type: telnet <SQLServerHostName> <PortNumber>
    SQLServerHostName is either IP address or hostname of the remote computer where SQL serve is running PortNumber is port number SQL server is listening for default instance it is 1433 but check SQL server configuration manager to make sure.

    6. Check the SQL Server login user access.

    7. You can try to specify protocol and port to connect SQL Server in the Query Analyzer as below:  TCP:MySQLServer,1433
    Through this method can force the specified query analyzer using the TCP / IP connection to the server specified port.

    8. If it does not work for you, please try to use Network Monitor to capture trace to analysis. For more information about Network Monitor, please refer to this article

    Additional, please refer the articles as below:
    1.  TCP/IP port numbers required to communicate to SQL over a firewall: http://support.microsoft.com/?id=287932
    2. How to Troubleshoot Basic TCP/IP Problems: http://support.microsoft.com/kb/169790

    Regards,
    Amber zhang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    • Edited by amber zhang Thursday, January 12, 2012 6:22 AM
    • Marked as answer by DavidB1982 Monday, January 16, 2012 1:04 PM
    Thursday, January 12, 2012 6:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    All this was GREAT information. I checked all of this prior to this post but thank you so much for this info. I found out that our fiber providers must be blocking some ports. I changed the default listening port and it started working.
    Monday, January 16, 2012 1:04 PM