Re: SQL 7 Encryption Using Multiprotocol Network Library

From: John (johnremovethedash-oxenbridge@hotmail.com)
Date: 11/18/02 

From: "John" <johnremovethedash-oxenbridge@hotmail.com>
Date: Mon, 18 Nov 2002 08:19:14 -0000

Yes, that's correct. The client was configured via the Client Network
Utility with Multiprotocol enabled. I've tried it with "force protocol
encryption" enabled and disabled without success.

Regards, John

"Hal Berenson" <haroldb@truemountainconsulting.com> wrote in message
news:e$VS5amjCHA.1572@tkmsftngp09...
> You mention that the client is properly configured, but don't really say
> what you did there. Did you run the Client Network Utility on the Client
to
> make sure that Multiprotocol is enabled, and that it is first in the
stack?
>
> --
> Hal Berenson
> True Mountain Consulting
>
>
> "John" <johnremovethedash-oxenbridge@hotmail.com> wrote in message
> news:#0lb9UIjCHA.1860@tkmsftngp09...
> > I'm trying to configure SQL 7 network encryption using the multiprotocol
> > network library. SQL Server is installed on Windows 2000 Server.
> >
> > I've configured SQL via the "SQL Server Network Utility", and have
enabled
> > multi-protocol encryption. However when connecting from a configured
> Windows
> > 2000 Professonal client I get the error "Encryption not supported on SQL
> > Server".
> >
> > I believe this is to do with "named pipes" also being installed on the
SQL
> > Server box, and it being treated as the default network library. I have
> > tried to remove "named pipes" using the "SQL Server Network Utility",
but
> > the "Remove" button is greyed out for this library. Multiprotocol (and
any
> > other library I've tested with) can
> > be removed.
> >
> > Any ideas will be much appreciated. Unfortunately upgrading to SQL 2000
to
> > use SSL isn't an option!
> >
> > Thanks,
> > John
> >
> >
> >
>
>