Re: Restricting access via LAN
- From: "Andrew" <noone@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 26 May 2006 10:28:03 +1000
Thanks Sue - you have confirmed what I thought to be the case. Always worth
asking though.
"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:i1r972heqlj4dgo0hpmqn3k6pk8ds5ghgm@xxxxxxxxxx
Unfortunately, not really. You can implemented checks for
users that will kill the process after the fact if they
aren't logged in with whatever application. But that's after
they have logged in.
-Sue
On Thu, 25 May 2006 07:43:22 +1000, "Andrew"
<noone@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We have a third-party SQLS 2000 based client-server system where the
client
software uses SQLS logins (not LAN logins) to access the database. This
opens up the risk of users using tools like MS Access, MS Query, etc to
access the database directly rather than through the client software.
Is there a way of restricting access so that only connections from the
client software will work? Note we are very restricted on what can be done
with the application itself as it is third-party. We need to put something
in place on the server.
TIA
Andrew
.
- References:
- Restricting access via LAN
- From: Andrew
- Re: Restricting access via LAN
- From: Sue Hoegemeier
- Restricting access via LAN
- Prev by Date: Re: who dropped my table in SQL Server?
- Next by Date: Re: Migrating from 2 Instances to 1 Instance (SQL 2005)
- Previous by thread: Re: Restricting access via LAN
- Next by thread: Re: Migrating from 2 Instances to 1 Instance (SQL 2005)
- Index(es):