Actually it's off by default in all versions of SQL Server 2K SP3 and up. I've also had problems accesing the server from a client PC and solved by is configuring a server alias with the CLICONFG tool.

Just in case you wanted to know!



>I found it -- needed to turn on TCP/IP to the MSDE installation (which is off by default in all MSDE installations, it seems). Ran SVRNETCN and enabled TCP/IP, and all worked fine.
>
>Thanks for the assistance.
>
>Evan
>
>>When you try and register the server can you type in the name of the instance which has been installed by MSDE? I think the sa password should be blank, inless its been changed by the install process itself.
>>
>>>Hi all,
>>>
>>>I've been using SQL Developer's Edition for a while now on a particular box. Recently I've installed MS Small Business Accounting 2006 on the same box, which uses and installs MSDE 2000 without asking permission or checking for an existing SQL installation (that's another issue).
>>>
>>>I'd like to use Enterprise Manager to administer this MSDE installation -- but I don't know its name or how to make EM see it. It doesn't show up in the Available Servers list when I try to register it, and the Service Manager shows an extra *blank line* in the Server drop-down. I also have NO idea what the user ID and password would be for MSDE if it did show up as available.
>>>
>>>I also viewed the Registry (after noodling around BOL and MSDN for info on this) and determined (I think) that MSDE was installed as a named instance called MSSQL$MICROSOFTSMLBIZ, with a different set of registry keys under HKLM/Software/Microsoft SQL Server/MICROSOFTSMLBIZ (my normal installation is at HKLM/Software/MSSQLServer). The normal keys also have a "Client" folder/branch that the MSDE keys don't have.
>>>
>>>I've searched MSDN for *hours* with no luck. I've also searched enough of the prior posts here to know that this should be possible. Anybody out there know how I can get EM to register and/or administer this fool thing?
>>>
>>>TIA,