There are few instances wherein errors occur when connecting to SQL Server Express 2005 using remote client software although there is no error in connecting to it on the local device. Examples of these errors are the failure of SQL Server to permit remote connections, absence of Server or access denied, or error on SQL Network Interfaces. These errors happen because SQL Server Express is manually constructed for remote access during the setting up. But there is nothing to worry about because this can be enabled. Meaning, the problem is not a bug but a feature. Great news!

The following are the gist of the actions you need to make to deal with the errors:

•    Enable the TCP/IP protocol through the Surface Area Configuration Utility

•    Confirm that the TCP/IP protocol is facilitated in the SQL Server Configuration Utility

•    Make sure to start the SQL Server browser. Although, this is not really mandatory. The SQL Server instance may also be set to utilize a permanent IP address, even though this is considered as substandard for named instances.

•    Ensure that both of the SQL Server and SQL Server Browser are excluded by the firewall on the server machine. This can be implemented by placing sqlservr.exe as well as sqlbrowser.exe as exclusions in the windows firewall.

Finally, to ensure that everything will work, the server machine should also be rebooted completely when the changes are done. This is because there have been reports that say stopping the software of SQL Server and SQL Server Browser alone is not enough.

Categories: News