Re: Distributed winforms application security
From: Robert (Robert_at_discussions.microsoft.com)
Date: 05/09/05
- Next message: Pierre: "Re: Form Authentication and new browser instance"
- Previous message: richlm: "Re: Web services domain authorization"
- In reply to: Nicole Calinoiu: "Re: Distributed winforms application security"
- Next in thread: Nicole Calinoiu: "Re: Distributed winforms application security"
- Reply: Nicole Calinoiu: "Re: Distributed winforms application security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 9 May 2005 07:08:02 -0700
I thought the same thing at first, and as we opened the database wide open,
no one could still connect.
We are using an SQL Server DB with Active Directory Windows Auth.
I dont have the actual thrown exception, as i used a user friendly generic
try and catch exception error. The exception is thrown if it cannot write the
information to the database and the only reson it could not write is if it
was not able to connect the user.
Actually I believe It works fine with any machine on the domain with
administrator status, but i dont know what else I can change to give access.
I have tried using mscorb to give user permissions and the assembly
permissions to no avail. Any further input you could provide would be
helpful. Thanks.
Robert
My Connection string is:
this.sqlConnection1.ConnectionString = "workstation id=myworkstation;packet
size=4096;integrated security=SSPI;data source=DataSource" +
";persist security info=False;initial catalog=InitialCatalog";
"Nicole Calinoiu" wrote:
> It sounds like the most likely cause is that the users don't have adequate
> permissions to the database. To confirm whether this is the case, might you
> be able to answer the following questions:
>
> 1. Is an exception thrown when attempting to connect the the database from
> the "user" machines? If so, could you please provide the exception details?
>
> 2. What kind of database are you using (e.g.: SQL Server, Oracle, Access,
> etc.)?
>
> 3. Are you authenticating against the database and, if so, are you using
> Windows or database accounts? (If you're not sure about the answer to this
> one, please provide the database connection string, replacing any real user
> credentials with garbage data.)
>
>
>
> "Robert" <Robert@discussions.microsoft.com> wrote in message
> news:56F72DB6-7C8E-4C4D-9AB0-1FB391B619C4@microsoft.com...
> > Hello all,
> >
> > I am writing a small application for work that connects to a database
> > (located on the company network) and writes some information. We use AD
> > for
> > windows auth and I have administrator staus on the domain and my
> > development
> > machine. The problem lies when I attempt to run the application from
> > another
> > users machine(not of administrator status on the domain), it won't allow
> > the
> > connection to the database. I used the VS connection wizards to make the
> > connections rather than writing all the code because i didnt think it
> > would
> > be a problem. Any ideas on what would be the easiest solution or which
> > direction to go from here? Thanks in advance.
> >
> > Robert
>
>
>
- Next message: Pierre: "Re: Form Authentication and new browser instance"
- Previous message: richlm: "Re: Web services domain authorization"
- In reply to: Nicole Calinoiu: "Re: Distributed winforms application security"
- Next in thread: Nicole Calinoiu: "Re: Distributed winforms application security"
- Reply: Nicole Calinoiu: "Re: Distributed winforms application security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|