The section below is copied from http://www.datamasker.com/SSE2005_NetworkCfg.htm (just copying it in case the original disappears)
Although by the time I become a proper power user I'll hopefully be on the full monty - not the express!
Here's the instructions:
Here's a quick summary of the actions you need to take. The first three actions have a separate page which provides more details and some screen shots of the procedure.
- [Link] Enable the TCP/IP protocol using the Surface Area Configuration Utility
- [Link] Make sure the TCP/IP protocol is enabled in the SQL Server Configuration Utility
- [Link] Make sure the SQL Server browser is started. Note this step is optional. It is possible to set the SQL Server instance to use a fixed IP address - but this is non-standard for named instances. See sqlexpress's WebLog for details.
- Make sure SQL Server and SQL Server Browser are exempted by the firewall on the server machine. This is done by putting sqlservr.exe and sqlbrowser.exe as an exception in the windows firewall. Chris D. sent in a note which might help.
- Note: In order to get things to work. You might need to completely reboot the server machine after making the changes. There have been reports (thanks P.C.) that starting and stopping the SQL Server and Browser software is not enough.
No comments:
Post a Comment