Connecting XP Home to BCM 2007 Installed on a domain controller

[P McCoy]

Sorry if this has been covered before...

I have set up BCM 2007 on a Windows 2003 PDC (it is a small domain). I want
to share the database across 3 users... some on the domain and some not. The
problem is that BCM only allows me to add domain users. So, when I go to
attach XP Home laptops to BCM, I can't seem to make it work.

I've tried running outlook as a domain user that was added to the user list
in BCM but that didn't work. No matter what I get the dialog box stating
"Your attempt to connect to the remote computer hsvpdc, where the database is
stored, could not be completed due to these possible reasons: ...."

Eventually, XP home will go away and we will be using either XP Pro or Vista
Business. But for now, is there a way to make this work? Is it possible to
force BCM running on the domain controller to use password authentication
rather than domain authentication? I'm willing to use passwords if BCM will
do everything I think it will. Thanks for any help/advice you can give.

- P. McCoy

 

[Luther]

Sorry if this has been covered before...

I have set up BCM 2007 on a Windows 2003 PDC (it is a small domain). I want
to share the database across 3 users... some on the domain and some not. The
problem is that BCM only allows me to add domain users. So, when I go to
attach XP Home laptops to BCM, I can't seem to make it work.

I've tried running outlook as a domain user that was added to the user list
in BCM but that didn't work. No matter what I get the dialog box stating
"Your attempt to connect to the remote computer hsvpdc, where the database is
stored, could not be completed due to these possible reasons: ...."

Eventually, XP home will go away and we will be using either XP Pro or Vista
Business. But for now, is there a way to make this work? Is it possible to
force BCM running on the domain controller to use password authentication
rather than domain authentication? I'm willing to use passwords if BCM will
do everything I think it will. Thanks for any help/advice you can give.

- P. McCoy

The real issue is getting Sql Server to recognise the user and allow
them to connect to the database--because they match one of the users
listed in the database's users table. Sql is going to defer to Windows
to authenticate the users (BCM does NOT do olde style sql user
authentication). There are two types of users that can be
authenticated by Windows (someone correct me if I'm wrong here): one
is domain users, where Windows defers to the Domain Controller and the
other is local users, and local users are solely authenticated based
on username and password. So, if you have the same username and
password on both the server and the client machines, its just possible
that user may be able to connect to the database, even when the server
machine is on a domain.