Re: Connecting to SQL Without Windows Authentication
From: Arvind Shyamsundar (arvindsh@online.microsoft.com)
Date: 02/07/03
- Next message: Bill Ryan: "RE: .NET Framework SDK Developer SP3 Critical Update"
- Previous message: Bill Hollinshead [MSFT]: "RE: .NET Framework SDK Developer SP3 Critical Update"
- In reply to: Steve Thomas: "Connecting to SQL Without Windows Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Arvind Shyamsundar" <arvindsh@online.microsoft.com> Date: Fri, 7 Feb 2003 19:27:10 +0530
PMJI,
The beauty with CALs is that they're device-bound and not user account
bound. This is why the "license group" concept was introduced - to account
for the fact that multiple people share a single computer. Please do go
through this page:
http://www.microsoft.com/windows2000/en/server/help/sag_LICEconcepts_401.htm
which explains the license group fundamentals.
Also note that you not only need SQL CALs but also Windows CALs in case the
net lib is named pipes. I'd recommend you to use TCP/IP unless you have some
specific reasons to use Named Pipes.
HTH,
Arvind.
-- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- This posting is provided "AS IS" with no warranties, and confers no rights. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- "Steve Thomas" <sThomas@ic-group.net> wrote in message news:003b01c2cd49$207bb4c0$d7f82ecf@TK2MSFTNGXA14... > It seems the problem was that we had an NT server in one > Domain and our Windows 2000 server in another domain. > Since they did not have a trust, it was focing us to > supply it with a valid username and password. We moved > the Windows 2000 server into the domain where the NT > server was and it corrected the problem. So what I gather > from this is that we do not need seperate licenses. > > Thanks for anyone who tried to help. > >-----Original Message----- > >I just spent about an hour with Microsft Sales on this > >issue and I know as much as before the call. > > > >I have a Windows 2000 server(5 Client Licenses) > >Running SQL Server2000 (Per Processor License). I have > >several PC's running win95, Win98, win2000. > > > >Question 1: If I connect using SQL Authentication, do I > >need to have a license for each user on the WIndows 2000 > >machine. > > > >Question #2: if the answer to Question1 is no(I do not > >need more CALS on Windows 2000) then I am having > >difficulty on some PC's. I wrote a basic program that > >opens an ADO connection to the SQL server. > > > >Problem1: Windows 2000 PC's. Some of them come back > with > >a message "Access Denied". If I go into network > >neighborhood and doubleclick on the server, it will ask > me > >for a name and password. If I supply it with a valid > user > >name and password on the Windows 2000 server, it will > >connect. Then when I run my program, it will work fine. > >WHY?? > > > >Problem2: Windows 98 PC's. Unless I create a user ID on > >the Windows 2000 server that is identical to the UserID > on > >their PC they always get "Access Denied". Once I create > >the user, everything works fine. > > > >This make me think I need Licenses for each user on > >Windows 2000 even though I am using SQL authentication?? > > > > > >Any help on this issue would be appreciated. > > > >thanks > >. > >
- Next message: Bill Ryan: "RE: .NET Framework SDK Developer SP3 Critical Update"
- Previous message: Bill Hollinshead [MSFT]: "RE: .NET Framework SDK Developer SP3 Critical Update"
- In reply to: Steve Thomas: "Connecting to SQL Without Windows Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
