Re: Integrated Security in a Workgroup?
From: Stephen Dybing [MSFT] (stephd_at_online.microsoft.com)
Date: 12/03/03
- Next message: Kevin McDonnell [MSFT]: "RE: Windows authentication is SQL"
- Previous message: Don Walter: "SQL Agent Proxy Account"
- In reply to: Bill Cohagan: "Re: Integrated Security in a Workgroup?"
- Next in thread: Stephen Dybing [MSFT]: "Re: Integrated Security in a Workgroup?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 3 Dec 2003 14:43:13 -0800
Hmm, I had assumed, like Kevin mentioned earlier, that if you used those
workgroup users, where the only thing that changed was the name of the
workgroup, it would work. I've done similar sorts of things with accounts
crossing different domains before and figured this would work as well. If
not, then your problem is beyond what I can help with off the top of my
head, and I don't have workgroup machines here that I can test on. Sorry!
-- Sincerely, Stephen Dybing This posting is provided "AS IS" with no warranties, and confers no rights. Please reply to the newsgroups only, thanks. "Bill Cohagan" <bill@teraXNOSPAMXquest.com> wrote in message news:eXwPQHeuDHA.1888@TK2MSFTNGP10.phx.gbl... > Since I'm using integrated security I must select an existing NT user; thus > I can't specify a user, ASPNET (or whatever), unless that user exists as a > local user on the machine. I can of course create such a user, but then I've > got the password problem I already mentioned. Have I misunderstood your > suggestion? > > Bill > "Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message > news:%23nPgnyduDHA.2148@TK2MSFTNGP12.phx.gbl... > > No, sorry, what I meant was that when you set up the SQL Server > permissions, > > try it without including the A\ or B\. > > > > -- > > Sincerely, > > Stephen Dybing > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > Please reply to the newsgroups only, thanks. > > "Bill Cohagan" <bill@teraXNOSPAMXquest.com> wrote in message > > news:utxj$XduDHA.1596@TK2MSFTNGP10.phx.gbl... > > > The A\ASPNET and B\ASPNET machine accounts are created by IIS (I > think) -- > > > at least I know that I did NOT create them. These are the accounts used > by > > > IIS when executing ASP pages. Since these accounts are not created by me > I > > > don't know the passwords -- and I can't just change them in XP because > > then > > > IIS will likely fail due to using the old password. Perhaps I can > change > > > the default ASP account used by IIS on both machines -- then I can > create > > > local accounts with the same username and password. > > > > > > Thanks for the suggestion. > > > > > > Bill > > > > > > "Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message > > > news:uOFYrdRuDHA.3144@tk2msftngp13.phx.gbl... > > > > I believe that you do this without specifying the A\ or B\. > > > > > > > > -- > > > > Sincerely, > > > > Stephen Dybing > > > > > > > > This posting is provided "AS IS" with no warranties, and confers no > > > rights. > > > > Please reply to the newsgroups only, thanks. > > > > "Bill Cohagan" <bill@teraXNOSPAMXquest.com> wrote in message > > > > news:#aPrRKOuDHA.4056@TK2MSFTNGP11.phx.gbl... > > > > > Kevin > > > > > Thanks. I've tried this, but the account I need to create is the > > > > A\ASPNET > > > > > account on the B machine. I've tried doing that and it complains > that > > > the > > > > A > > > > > domain doesn't exist. There's already a B\ASPNET account on machine > B > > > and > > > > an > > > > > A\ASPNET account on machine A. Suggestions? > > > > > > > > > > Thanks again, > > > > > BIll > > > > > > > > > > PS - Yes this is a temporary environement, for development purposes > > > only. > > > > > > > > > > "Kevin McDonnell [MSFT]" <kevmc@online.microsoft.com> wrote in > message > > > > > news:bHu03vGuDHA.2436@cpmsftngxa06.phx.gbl... > > > > > > Assuming this is a temporary environment.. You'll need to > duplicate > > > the > > > > > > account used on the Dev box, with the same account and password on > > the > > > > SQL > > > > > > box. This is often referred to as "workgroup security". > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Kevin McDonnell > > > > > > Microsoft Corporation > > > > > > > > > > > > This posting is provided AS IS with no warranties, and confers no > > > > rights. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
- Next message: Kevin McDonnell [MSFT]: "RE: Windows authentication is SQL"
- Previous message: Don Walter: "SQL Agent Proxy Account"
- In reply to: Bill Cohagan: "Re: Integrated Security in a Workgroup?"
- Next in thread: Stephen Dybing [MSFT]: "Re: Integrated Security in a Workgroup?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
