Hopefully there's some SQL architect gurus reading...
I have a couple servers where none of the Net Protocols are enabled. I'm
not sure how they ended up that way. Usually we have at (default?) for
TCP/IP then Named Pipes, we have no need for other net protocols. However,
our apps and services are still able make SQL connections.
I'm verifying this via the SQL Network Client Utility. What else can
determine or configure Network Libraries? And what impacts might this have
on connectivity with no protocols enabled?
Thanks,
ThuanAre you saying that you use Client Network Utility on the server machine and in the Client Network
Utility on the server machine not netlibs are enabled? You should be using Server Network Utility on
the server machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols. However,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this have
> on connectivity with no protocols enabled?
> Thanks,
> Thuan|||Hi
If this is an MSDE instance then network access is not enabled by default on
the server. You should check out the Server Network Utility to see if
clients can connect and on each client check the Client Network Utility.
Enabling the protocols in the Client Network Utility will only affect the
client applications on the server.
John
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols.
> However,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this
> have
> on connectivity with no protocols enabled?
> Thanks,
> Thuansql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment