MSSQL Server 2008 R2 Named Pipes Error

I have installed MSSQL Server 2008 R2 but I am having trouble connecting to it remotely.  I am able to ping the server, enabled TCP/IP and Named Pipes, enabled remote connections, setup exceptions for port 1433, started SQL Server browser but still no luck.  what am i missing?

exact error message
TITLE: Connect to Server
------------------------------

Cannot connect to 172.20.244.85.

------------------------------
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: 53)

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

------------------------------
BUTTONS:

OK
------------------------------
szadrogaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
How was SQL server installed? "Default" or "Instance"?
If it was installed as instance must be accessed like
https://msdn.microsoft.com/en-ca/library/ms345332(v=sql.105).aspx
<<
A named instance displays as the computer name followed by a backward slash (\) and then the name of the instance. For SQL Server Express, the instance is named <computer_name>\sqlexpress unless the name was changed during setup.
>>
szadrogaAuthor Commented:
I'm not sure, i wasn't the one who installed SQL Server.  Is there a quick way for me to find out?

I opened the link and proceeded to the section 'To determine the name of the instance of the Database Engine" and after performing Step 4 i got the following error message.  Does this mean it is not "Instance"?

TITLE: No Local Servers Found
------------------------------

No local servers of type 'Database Engine' were found.

------------------------------
BUTTONS:

OK
------------------------------
lcohanDatabase AnalystCommented:
Can you access that actual box where SQL Server was installed via RDP and check the  Services to see the actual SQL Server Service name?
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Dave BaldwinFixer of ProblemsCommented:
If the SQL Server is not on your machine, you will have to install the appropriate driver which is usually SQL Native Client.  https://msdn.microsoft.com/en-us/data/ff658533

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
szadrogaAuthor Commented:
attached is a screenshot of my services.  does this indentify SQL Server Service Name?
services.png
szadrogaAuthor Commented:
Dave,

I am able to connect to other MS SQL SERVERS via my machine.  Would i still need to install SQL Native Client?
Dave BaldwinFixer of ProblemsCommented:
Probably not if they are the same version.  You can look in the ODBC manager to see what drivers you have.

The services you are showing should be running on the machine with the SQL Server.  SQL Native Client is a driver, not a service, so it would not show up in that list.  It should show up in the ODBC Manager.
szadrogaAuthor Commented:
Dave,

I went to the download link but there are several file choices to download.  Which one should I choose?  My machine is Windows 7 64 bit.  The MS SQL Server is 2008 R2 64 bit.
szadrogaAuthor Commented:
attached is a screenshot of my drivers
drivers.png
Dave BaldwinFixer of ProblemsCommented:
Yep, there are two versions there.  One of the things about using the drivers is that you have to Exactly quote the name for it to be recognized and use.  For the SQL Native Client listed, you must call it "SQL Server Native Client 10.0" to be recognized.
Dave BaldwinFixer of ProblemsCommented:
I forgot to mention that you can make a "User DSN" using that driver and the credentials that you are trying to use to see if the connection works.
szadrogaAuthor Commented:
Still no luck.  I tried creating a USER DSN connection using the SQL Server Native Client driver i have installed and got an error message (see attached).  Do i need to update my drivers for SQL Native?
error.png
Dave BaldwinFixer of ProblemsCommented:
No, you don't need to update your driver.  You may have to go into the Admin page for the SQL Native Client and make sure that TCP connections are enabled.  Or you may have to turn on TCP and remote connections on this particular server.

How are you connecting to other SQL instances?
szadrogaAuthor Commented:
Dave,

When you mention the SQL Native Client, is that on my machine or server?  On the server, i have the TCP enabled and "allow remote connections" (see attached screenshot)
settings.png
szadrogaAuthor Commented:
I am connecting to other SQL servers using SSMS 2008 on my local machine .
Dave BaldwinFixer of ProblemsCommented:
When you mention the SQL Native Client, is that on my machine or server?
It is installed on the server with the SQL Server.  However, you need a copy on your machine to make the connection.  You program isn't going to 'remotely' use the version on the server.

But as you showed above, you do have it on your machine which is why you can connect to other machines with SQL Server.  In your image above, look at the SQL Server protocols to see if they match the SQL Native Client protocols, in particular make sure TCP is enabled.
szadrogaAuthor Commented:
Issue had to do with firewall on my side.

Both experts provided great tips for troubleshooting this type of error message
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.