Networking is disabled by default


After seeing a number of issues about this, I realized that we needed to comment on this.

For SQL Express, all networking protocols except shared memory are disabled by default.  There is a command line setup switch called DISABLENETWORKPROTOCOLS which is always set to 1 in SQL Express installations.  You can override this by providing the switch DISABLENETWORKPROTOCOLS=0 to setup.exe on the command line.  On an already installed machine, you can use SQL Computer Manager to configure the networking protocols.

The SQL Browser service is also not started by default *unless* the command line switch DISABLENETWORKPROTOCOLS=0 is passed to setup.exe.  You can change SQL Browser’s startup type by using the Services control panel.

-Jeffrey Baker
SQL Server Setup Development

Comments (4)

  1. Wallym says:

    Thanks for the info.

    Waly

  2. haroldb says:

    An even bigger issue is that existing MDAC clients can’t talk to Express using shared memory. This is going to be a HUGE PSS call generator.

    The existing solutions just don’t cut it for reducing the support load/improving the out-of-box experience. Modifying the application (ie, changing the connect string) is not a good solution (e.g., older versions of MS Access hardcode the provider name). And enabling network access violates the entire security premise behind disabling it by default in the first place. And for many users, neither solution will even be discovered until they are highly frustrated with SQL Server 2005.

    Any plans to address this before RTM?

    Hal

  3. Dave Nettleton says:

    Hal, yes we have plans for this for Beta3 – the aim is to allow local machine MDAC client access to the Express named instance out of the box. (Protocols would still needing configuring to allow off-box access.)

    Thanks

    Dave.

  4. Stephen Dybing says:

    I think what’s missing here is that if you’re attempting to enable the protocols after SQL Express has been installed, you must also restart SQL Express in order for it to listen on the newly enabled protocols.

    Thanks,

    Steve