"Keith G Hicks" <krh@comcast.net> wrote in message
news:%23phBoIf9GHA.3620@TK2MSFTNGP04.phx.gbl...
> I'm confused about this. If I need MSDE installed on a server and have 10
> workstations accessing it AND I don't want to use port 1433, what's the
> process I need to go through to make that work right. I've fumbled around
> with it and am not sure I follow the process. It seems logical to me that
> I
> would run the server one on the server, set the port and then run the
> client
> one on the client and set it to match the server but I hvae a feelign
> that's
> not the case. Especially because since I'm not installing MSDE on any of
> the
> client machines there is no network utility installed (AFAIK).
>
> I'm also confused as to how DISABLENETWORKPROTOCOLS fits into this part of
> things (if at all).
>
> Thanks,
>
> Keith
>
>

"Norman Yuan" <NotReal@NotReal.not> wrote in message
news:%23v3k7Xf9GHA.3264@TK2MSFTNGP04.phx.gbl...
> Yes, your thought is very logical and workable if the client network
> utility is installed on workstations, so that you can have apps on
> workstation know whih port is used to communicate with SQL Server.
> Actually, if you to create a ODBC DSN to SQL Server, the DSN configuration
> provides you a dialog to specify network library to use (TCP, Named
> Pipe...) and port number (or dynamically determined).
>
> However, in most cases, you do not need to run the client network utiliy
> on workstations. The port number can be specified in the applications'
> ConnectionString (if the app is designed well, there should be someway to
> configure its connectionString, i.e. the database connection information).
>
> AS for DISABLENETWORKPROTOCOLS, it is an installtion parameter. if you do
> not explicitly set it to 0 when you install MSDE, by default, the MSDE is
> not accessible from other computer. If you want the MSDE being accessible
> by other computer, you either set it to 0 at installation or you can
> enable network access after installation.
>
>
> "Keith G Hicks" <krh@comcast.net> wrote in message
> news:%23phBoIf9GHA.3620@TK2MSFTNGP04.phx.gbl...
>> I'm confused about this. If I need MSDE installed on a server and have 10
>> workstations accessing it AND I don't want to use port 1433, what's the
>> process I need to go through to make that work right. I've fumbled around
>> with it and am not sure I follow the process. It seems logical to me that
>> I
>> would run the server one on the server, set the port and then run the
>> client
>> one on the client and set it to match the server but I hvae a feelign
>> that's
>> not the case. Especially because since I'm not installing MSDE on any of
>> the
>> client machines there is no network utility installed (AFAIK).
>>
>> I'm also confused as to how DISABLENETWORKPROTOCOLS fits into this part
>> of
>> things (if at all).
>>
>> Thanks,
>>
>> Keith
>>
>>
>
>

Bill Hicks wrote:
> Just wondering if there's a clear answer to this - if
> DISABLENETWORKPROTOCOLS is set to 0 for let's say an initial
> installation of MSDE sp3 so that the server is accessible from other
> workstations, what happens if I set DISABLENETWORKPROTOCOLS=1 for an
> upgrade to sp4? Will that basically disable the networkability for
> the specified instance of MSDE from that point forward, or is that
> only temporary for the installation process?