Ma'am,
I think part of the problem is that we are trying to oversimplify our
application and 2005 doesn't like it.
Here's our scenario: We have a small network with only 10 users accessing a
very simple database. We do not have any security issues because we are on
an isolated network with all trusted users. Our only requirement for
accessing the database is that each user access with different
logins/passwords. In previous SQL Server versions, we were able to build a
user account (Student1) on the client workstation, SQL Server machine, and on
the SQL Server application and everything appeared to be fine. We are not on
a domain, only a workgroup.
With the new installation of SQL Server 2005, we have tried everything I
mentioned above but each time we are accessing the database using the Guest
account. They only way to shut down Guest is to "DISABLE" on server
computer. It is important to note that we are running XP SP2 on the SQL
Server machine and the clients.
Is there anyway to make a very simple client/server configuration to allow
users to access the database without using the guest account. We do not want
the user to be forced to login on the database server machine. We want the
client machine to authenticate with the SQL server machine transparently to
the user (Student1).
Any insight you can provide will be deeply appreciated.
[quoted text, click to view] "Sue Hoegemeier" wrote:
> With Simple File Sharing enabled, Windows authentication is
> done through guest account.
> Another option would be to use SQL Logins and enable SQL
> authentication for SQL Server.
>
> -Sue
>
> On Thu, 14 Jun 2007 13:46:01 -0700, SnapperHead
> <SnapperHead@no.mail> wrote:
>
> >When configuring SQL 2K5 on Windows XP Pro, Guest seems to be the only
> >authentication available. Is there a service that I'm missing?
> >
> >I prefer to keep File Sharing available. Individual username and passwords
> >are also required for the network. I've disabled firewall for now until I
> >can login as different users.
> >
>
It worked the same way on previous versions of SQL Server as
well when using simple file sharing. Refer to the following:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/kb/831133/en-us The answer is the same. Disable simple file sharing or use
SQL Logins.
-Sue
On Wed, 20 Jun 2007 06:44:00 -0700, SnapperHead
[quoted text, click to view] <SnapperHead@no.mail> wrote:
>Ma'am,
>
>I think part of the problem is that we are trying to oversimplify our
>application and 2005 doesn't like it.
>
>Here's our scenario: We have a small network with only 10 users accessing a
>very simple database. We do not have any security issues because we are on
>an isolated network with all trusted users. Our only requirement for
>accessing the database is that each user access with different
>logins/passwords. In previous SQL Server versions, we were able to build a
>user account (Student1) on the client workstation, SQL Server machine, and on
>the SQL Server application and everything appeared to be fine. We are not on
>a domain, only a workgroup.
>
>With the new installation of SQL Server 2005, we have tried everything I
>mentioned above but each time we are accessing the database using the Guest
>account. They only way to shut down Guest is to "DISABLE" on server
>computer. It is important to note that we are running XP SP2 on the SQL
>Server machine and the clients.
>
>Is there anyway to make a very simple client/server configuration to allow
>users to access the database without using the guest account. We do not want
>the user to be forced to login on the database server machine. We want the
>client machine to authenticate with the SQL server machine transparently to
>the user (Student1).
>
>Any insight you can provide will be deeply appreciated.
>
>"Sue Hoegemeier" wrote:
>
>> With Simple File Sharing enabled, Windows authentication is
>> done through guest account.
>> Another option would be to use SQL Logins and enable SQL
>> authentication for SQL Server.
>>
>> -Sue
>>
>> On Thu, 14 Jun 2007 13:46:01 -0700, SnapperHead
>> <SnapperHead@no.mail> wrote:
>>
>> >When configuring SQL 2K5 on Windows XP Pro, Guest seems to be the only
>> >authentication available. Is there a service that I'm missing?
>> >
>> >I prefer to keep File Sharing available. Individual username and passwords
>> >are also required for the network. I've disabled firewall for now until I
>> >can login as different users.
>> >
>>
>>
Don't see what you're looking for? Try a search.
