Had to play a bit to confirm some things. First, if you're looking for
advice in a domain environment, then stop reading. I don't do domains. Yet.
:-)
If you're talking peer networks with non-web based access though...
Minor segue, and something I needed to confirm. There are two sources for
Guest account credentials being used other than having simple file sharing
enabled on the Server host; blank passwords or the user on the remote system
not being defined to the host system.
So, assuming you're using passwords, you'll need to define all users on the
server host. You can create them as limited users on the host, but if create
an additional group on the server you can add them to that and grant the
group access to the specific databases/server instances. If an individual
needs a different set of access rights you can either configure individual
logons or create more groups.
--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.
[quoted text, click to view] "David" <David@discussions.microsoft.com> wrote in message
news:7BBB9639-EA85-4D54-8AEF-E4673DBDEFF3@microsoft.com...
> Thanks Walter, but I'm still having some issues...
>
> First, my computer (just running XP Pro) running the SQL Server does NOT
> have simple file sharing on. On my laptop I turned simple file sharing
> off,
> plus added a password to my user login account. Still doesn't work and
> gives
> me the same error.
>
> I would like to know how to configure the SQL server in the first place so
> that it's secure and I can add, modify and delete users who access the
> server.
>
> Any recommendations?
>
> Thanks,
>
> David
>
> "Walter Clayton" wrote:
>
>> You're authenticating to the server as "Guest". That implies you're
>> running
>> with simple file sharing enabled on the server host or possibly running
>> sans
>> passwords (I'm fuzzy on the last since I always use passwords).
>>
>> Two options. The first isn't really recommended. You can alter the
>> connection string to disable integrated security and pass a user name and
>> password with the request. Or, you can disable simple file sharing on the
>> server host and either use the same name/password on both the server host
>> and laptop, or at the minimum create a user on the server host with the
>> name
>> and password you're using on the laptop.
>>
>> --
>> Walter Clayton
>> Any technology distinguishable from magic is insufficiently advanced.
>>
>>
>> "David Block" <David Block@discussions.microsoft.com> wrote in message
>> news:C886DF5E-464C-4216-A54B-29C2E2C60EBB@microsoft.com...
>> > Hello,
>> >
>> > I have trouble connecting to the MSDE databsae via my laptop computer
>> > that
>> > is connected to my home network. I have MS SQL Server (MSDE) running
>> > on
>> > my
>> > main computer. I created a C# application to connect to the database
>> > from
>> > both computers. When I try to connect from the laptop, I get the error
>> > message:
>> >
>> > "Login failed for user '<server>\Guest'"
>> >
>> > Where <server> is the name of my home computer running the server.
>> >
>> > Here is my connection string:
>> > Integrated Security=SSPI;Initial Catalog=" + mDatabaseName + ";Data
>> > Source="
>> > + mServerName
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> >
>> > David
>> >
>>
>>