Wednesday, March 28, 2012

Netware, MS SQL Server , Logins

Posted in Sql Server Setup Newsgroup as well.
I have a MS Sql Server 2000 application. The LAN environment is Novell Netw
are 5.x. with NO Windows domain. The network layer is TCP/IP and IPX/SPX. L
arge network with many users (500+), thus slow to change.
The client workstation OS that is going to attach to the Sql Server app are
Windows NT 4.0. The workstations load the Novell Netware client as the prim
ary client and authenicate there. The Novell Netware client is "checked" t
o logon to Windows Workstat
ion locally.
Here is the delimma. No Windows domain seems to rule out NT Authenicated se
curity on Sql Server. Sql Server authenication will be tough to maintain du
e to number of users.
1. Can the Novell login name/ psw be used in any way?
2. Can the Sql Server and the Novell LAN be intergrated in a way that would
help in this situation?
3. What would you do?
Thanks,
BrianPrevious Post:
Here is the delimma. No Windows domain seems to rule out NT Authenicated
security on Sql Server. Sql Server authenication will be tough to maintain
due to number of users.
1. Can the Novell login name/ psw be used in any way?
2. Can the Sql Server and the Novell LAN be intergrated in a way that would
help in this situation?
3. What would you do?
Reply:
1. No. You'd have to login to both Novell and a Windows DC.
2. Without a domain. You can only use SQL Standard Security with TCP or
IPX/SPX.
3. Use TCP/IP. Enable Protocol Encryption to encrypt the traffic and the
logins. Just putting a server certificate on the SQL machine will encrypt
the logins. Enabling protocol encryption will encrypt all the traffic as
well.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

No comments:

Post a Comment