October 22, 2010 at 3:50 pm
Hello everyone,
I just had the hardware firewall removed that was protecting my web/SQL 2005 server - after the removal of the firewall, I am now receiving the following error on all pages that use the DB:
Server Error in '/Locator' Application.
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)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
I thought I made the appropriate changes to SQL Server and checked SQL Server surface area configuration, etc. and thought everything was OK. Anyhow, I have got the feeling that when the hardware firewall was in place, SQL Server was using a different, local, IP address. Where/how can I point SQL Server to point to the 'public' IP address? I did the netstat command and did see that SQL server is 'listening' to the appropriate ports (1433) & was listening on the public IP...
I do not know what else to do/check (not experienced SQL Server either) . Any help would be kindly appreciated.
Thanks
October 22, 2010 at 4:16 pm
Follow up / Clarification question: The MSSQL service is not activating on the main IP address of the server - how can I activate to the main IP address?
October 22, 2010 at 7:58 pm
Yet another follow up to my problem...
In SQL Server Config Manager >> Network Config >> TCP/IP Properties >> IP address tab
I specified the IP address in IP1 and set it as active, and enabled it too - yet, when I restart the SQL server, the active value changes back to No.
I then changed the IP2 setting to the proper IP address, and made it active and enabled, then restarted the server - the active and enabled remain Yes, but I am still getting connection errors. [The IP1 active value still goes back to No]
I'm at my wits end and do not know what to do next.
Any advisement would be greatly appreciated.
--Thanks
October 25, 2010 at 9:57 am
For whatever its worth, fixed the issue, might be helpful for an inexperienced SQL person such as myself in the future:
The webconfig files for each of my apps were using an internal IP for the data source / connection string of 10.0.0.2 when my hardware firewall was in place; I had to change it to 127.0.0.1 and it was fixed.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply