Post reply

Cannot connect to SQL Server 2008 R2 remotely

  • July 26, 2012 at 7:37 am

    #264888

    I've attempting to create a Development box that host a SQL Server 2008 R2; however, I'm unable to connect to it remotely. I can't create an ODBC connection as well.

    My setup is this:

    Windows Server 2008 R2 Standard 64-bit

    Sql Server 2008 R2:

    Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1414 )

    Microsoft Analysis Services Client Tools 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )

    Microsoft Data Access Components (MDAC) 6.1.7601.17514 (win7sp1_rtm.101119-1850)

    Microsoft MSXML 3.0 6.0

    Microsoft .NET Framework 2.0.50727.5456

    I’ve installed SQL Server 2008 on the machine and did the following:

    1.I went to the server properties in Microsoft SQL Server Management Studio and checked the "Allow remote connections to this server" under Connections section.

    2.I also went to SQL Server Configuration Manager and under SQL Server Network Configuration I enabled the TCP/IP Protocol.

    3.Then went to Windows Firewall with Advanced Security and created an inbound rule for the Database Engine to allow connection for port 1433.

    I would imagine that doing all of this would grant me access remote access to the box and create ODBC connections but this is not the case.

    I have the error message attached to the this email.

    Is there something I’m forgetting to enable? Setup?

  • July 26, 2012 at 2:09 pm

    #1518169

    Did you make sure the proper services are running; i.e. SQL Server and SQL Server Browser?

    Jared
    CE - Microsoft

  • July 26, 2012 at 2:17 pm

    #1518174

    I have the error message attached to the this email.

    Did you forget to attach the error message? I cannot find it.

    Regards,

    TA

    Regards,
    SQLisAwe5oMe.

  • July 26, 2012 at 3:52 pm

    #1518216

    have you configured the windows firewall to allow SQL Server traffic? I have had that issue my self.

    http://msdn.microsoft.com/en-us/library/ms175043.aspx

    For faster help in answering any problems Please read How to post data/code on a forum to get the best help - Jeff Moden[/url] for the best way to ask your question.

    For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]

    Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
    Jeff Moden's Cross tab and Pivots Part 1[/url]
    Jeff Moden's Cross tab and Pivots Part 2[/url]

  • July 26, 2012 at 3:59 pm

    #1518217

    I've attached the error messages sorry about that.

    The inbound firewall rules were added already.

    All service running has also been confirmed.

    Same results.

  • July 31, 2012 at 1:14 am

    #1519547

    I have seen your attached error snapshot and have assumed two possiblities:

    1. TCP\IP Services seems to be disabled. Which is not allowing you to handshake with remote server.

    2. Please type correct Server\instance name.

    Thanks,

    Jitendra

  • July 31, 2012 at 7:10 am

    #1519700

    Thanks Jitendra.

    1. TCP\IP Services seems to be disabled. Which is not allowing you to handshake with remote server.

    Where would I go to enable the TCP\IP service?

    2. Please type correct Server\instance name.

    I have confirmed that the Server\instance name is correct; therefore, this is not an issue.

  • July 31, 2012 at 7:19 am

    #1519710

    emmanuel.constant (7/31/2012)

    Thanks Jitendra.

    1. TCP\IP Services seems to be disabled. Which is not allowing you to handshake with remote server.

    Where would I go to enable the TCP\IP service?

    2. Please type correct Server\instance name.

    I have confirmed that the Server\instance name is correct; therefore, this is not an issue.

    SQL Server Configuration Manager is where you will go to check tcp/ip settings. his will be under the SQL Server Network Configuration. Go to Protocols for MSSQLSERVER (or your named instance) and make sure tcp/ip is enabled.

    Jared
    CE - Microsoft

  • July 31, 2012 at 8:28 am

    #1519757

    Thanks Jared.

    Well then that has been addressed also. I made sure that was enabled as well.

    I did discover that I have the Win2008 server which host the SQL Server 2008 on one domain and I'm attempting to access it from a client PC from another domain. Not sure if it matters or not; however, i reckon there should be a handshaking between the two domain security wise before the exchange of packet happen no?

  • July 31, 2012 at 9:19 am

    #1519786

    If you are attempting to use windows authentication, I don't think it will work that way. They must both be on the same domain.

    Jared
    CE - Microsoft

  • July 31, 2012 at 9:36 am

    #1519803

    No windows authentication.

    I'm using SQL Server Authentication.

  • July 31, 2012 at 9:37 am

    #1519804

    Ok, then the domain is irrelevant.

    Jared
    CE - Microsoft

  • July 31, 2012 at 9:39 am

    #1519806

    So then it's seems that I've covered all bases for this to work but it doesn't.

    Is there any other reason why I'm receiving these messages.

  • July 31, 2012 at 9:56 am

    #1519819

    On your machine (maybe this was already asked, but I don't remember) can you ping the server from command line? "ping servername"

    Jared
    CE - Microsoft

  • July 31, 2012 at 10:01 am

    #1519822

    Yes that has been confirmed as well.

    I first it wasn't; then discovered that WinServer 2008 installs with ping replies disabled;

    therefore, I enabled it using this "netsh firewall set icmpsetting 8" command and was able

    to ping after.

Viewing 15 posts - 1 through 15 (of 34 total)

You must be logged in to reply to this topic. Login to reply