Re: Q: Named pipes and Windows (integrated) authentication
From: Michael C (nospam_at_lol.net)
Date: 07/20/04
- Next message: Lou Arnold: "Re: Q: Windows Authentication"
- Previous message: Michael C: "Re: Q: Windows Authentication"
- In reply to: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Next in thread: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Reply: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Jul 2004 00:41:46 GMT
SQL Tools - he's referring to SQL Query Analyzer and SQL Enterprise Manager
specifically. If you don't have a full copy of SQL Server 2K you're not
going to have these. I believe in the Windows credentials, he's referring
to the fact that you have to set up usernames on the SQL Server for your
Workgroup logins. The format, if I'm not mistaken, is similar to adding a
Domain user, but you'll replace the Domain with the Workgroup name.
I.e., if your workgroup is MSHOME and your username is BOB, you would add a
login for
MSHOME\BOB
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@nospam.com> wrote in message
news:40fc4a07.19880216@nntp.flfrd.phub.net.cable.rogers.com...
> Kevin...
> I log in as the Administrator on both machines.
>
> > Trusted Connections or Windows Authentication is when the client uses
> >his windows authentication to connect to the server. If you are not in a
> >domain, then you'd have to use Workgroup security to make this work.
> >A user needs first to be able to authenticate to the server either using:
> > a) Windows credentials
> > b) SQL username and password
> Lou>> Don't understand what you mean by Workgroup security. Are you
> saying I cannot use Windows Authentication? The other choices are
> Mixed or SQL Server security modes. The objective was to use Windows
> "credentials", but is this possible without a domain controller??
>
> >Once you've connected, it will check your credentials for permission to
> >create objects like databases or stored procedures.
> Lou>>Yes, understood.
>
> >Creating databases is only acomplished after you've already connected.
Try
> >using the SQL tools to see if your user has the correct privledges.
>
> Lou>>Don't know which SQL tools unless you are referring to osql.exe
> or MSDE Plus.
> Lou>> However, since I log onto the MS Access computer as the
> Administrator, will this not let me create a database on the server
> computer?? If not, How would I configure the permissions to allow me
> to do this?
> Lou>>Thanks.
>
- Next message: Lou Arnold: "Re: Q: Windows Authentication"
- Previous message: Michael C: "Re: Q: Windows Authentication"
- In reply to: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Next in thread: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Reply: Lou Arnold: "Re: Q: Named pipes and Windows (integrated) authentication"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|