Monday, March 27, 2006
Posted on Monday, March 27, 2006 5:03:00 PM (Mountain Daylight Time, UTC-06:00)  Comments [0] | 
Categories: .NET | Security
I ran into a little trouble getting machines on my LAN to talk to the SQLExpress instance on my workstation, and thought I'd share the answer.

Very simply, all that complaining people did about how Microsoft ships server software in insecure configurations has had an effect. SQLExpress installs in such a way that the only enabled protocol is "Shared Memory" - which basically means localhost access only.

You can change this by opening the SQL Configuration Manager, and enabling TCP/IP and Named Pipes, and then re-starting the service. Then the other client applications can connect.

Comments are closed.