Classic ASP connection string not working in IIS 8.5 under Windows 2012 R2

We are in the process of migrating an existing ASP Classic web site
(IIS 7) to new hardware and are encountering a connection string
failure when connecting to our new SQL server from the web server
console using a browser.

Our current Web and SQL servers (both 2008 Server Enterprise) are run
as virtual machines on our current vmware host.  We are migrating to a
new Dell Quad server with Microsoft Hyper V (4 virtual servers). All
virtual servers and host run Windows 2012 R2 Data Center Edition. The
new virtual web server is running IIS 8.5, and the new virtual SQL
server is running SQL 2014.

The actual error is:  (this is the std. connection string error if the
SQL database server was turned off)
Microsoft OLE DB provider for SQL server error '80000-4005
DBNETLIB connection open SQL server does not exist or access denied.

The FQDN of the web server is resolved by an entry in the Hosts file.
The SQL and web virtual server can ping each other both by IP address
as well as host name.

Windows Firewall is off on both web and SQL virtual servers.

We have attempted to connect using the IP address in the connection
string instead of the host name and this also failed.

We have attempted to verify that the web server is actually opening a
port to the SQL server using packet capture and did not detect

We have confirmed that the connection string works properly when
running the identical ASP code on our existing Windows 2008 web server
(IIS 7). We are also able to create an ODBC connection from the new
web server to the virtual SQL server.

Since ASP appears to be deprecated in IIS 8.5 we are wondering if
there is an incompatibility or security settings that need to be
tweaked or if there is an issue with the Hyper v environment.
Who is Participating?

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

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.

Dave BaldwinFixer of ProblemsCommented:
DBNETLIB is a very old interface and is probably not available anymore.  It was part of SQLOLEDB.  You should probably be using the SQL Native Client.  That does mean you will have to rewrite some of your code.
This seems to suggest  that your SQL Server 2014 has not been enabled to accept remote connections.

Here is a walk through on how to accomplish that:

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
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
Windows Server 2012

From novice to tech pro — start learning today.