client network utility & server network utility - what's the difference?

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
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
>
|||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?
"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...
>
|||hi Bill,
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?
as per
http://msdn.microsoft.com/library/de...tsql_84xl.asp,
DISABLENETWORKPROTOCOLS=n
In SQL Server 2000 SP3 or later, specifies how the Installer configures the
network protocol support for the instance of the Desktop Engine being
installed or upgraded. n is an integer number, and should be set to either 0
or 1.
These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
Value Specified for n Installing New Instance
1:
Upgrading Existing Instance: Instance is configured with all server
Net-Libraries disabled.
Installing New Instance: Instance is configured with all server
Net-Libraries disabled.
0:
Upgrading Existing Instance: The existing server Net-Library configuration
is retained.
Installing New Instance: Instance is configured with default server
Net-Libraries and addresses enabled.
Parameter not specified, or is any value other than 0 or 1:
Upgrading Existing Instance: The existing server Net-Library configuration
is retained.
Installing New Instance: Instance is configured with all server
Net-Libraries disabled.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply