Please help connecting to SQL !

  • First time I encountered this: I have a SQL2008 express instance on a remote server that I connect to from my local server, which is a SQL2008 standard 32 bit. I can connect no problem.

    Now I have a new server, and it's a SQL 2008 r2 x64 bit, and it will not connect to the remote SQL2008 express instance. On the server itself, I can use the ODBC connection manager to connect to it, but I'm assuming that it's using some 32bit driver to connect, and the SQL 2008 r2 is using some native x64 bit driver that doesn't work?

    Any suggestions on how to connect is greatly appreciated, thanks!

  • Do you get an error message when you try to connect?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Please answer GSquared's question.

  • thanks for the reply, the error is below. However, I CAN connect from a different SQL 2008 server

    TITLE: Connect to Server

    ------------------------------

    Cannot connect to 207.245.109.91.

    ------------------------------

    ADDITIONAL INFORMATION:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=1326&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

  • Is it on a different network, or different subnet? Try pinging the IP address you are using, from the server that can't connect. See if you get a reply.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • It's a completely different network, connecting over the internet, not internally. Ping is turned off though, b/c I cannot ping even from the SQL server that works. Again, odbc connections also work, but native SQL 10 connections from the x64 server do not, which is what led me to think it's a x32 vs. x64 driver issue that the 2008r2 version is using.

  • From the same server, I can go to the ODBC connections window and make an ODBC connection to the remote server no problem. But I just can't do it from SQL Server management studio. So I think the management studio is using a different driver that can't connect to SQL 2008 express?

    It can connect to other instances of SQL 2008.

    any help is greatly appreciated, thanks!

  • The error message you're getting says that Named Pipes may not be enabled on the server you're trying to connect to. Is it? (SQL Server Configuration Manager allows you to check and control this.)

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Just in case anyone runs into this issue, it is definitely a SQL 2008 r2 issue with the default driver. I compared the registry values and matched it to my older SQL 2008 x86 server, and low and behold it can now connect no problem.

    thanks for everyones assistance!

Viewing 9 posts - 1 through 8 (of 8 total)

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