I have several Office 2003 Pro BCM XP SP2 systems that are running. I want
to share the databases across my LAN. The LAN uses static IPs.

When I try to find a Computer by name from the Business Tools Create or
Share Option page the connection is refused with a general reference to the
request not being allowed.

I have checked several things:

o No firewalls are active on the desktops.
o The databases are setup for sharing by BCM.
o The users are setup as valid users on the Remote systems.
o The SQL Configuration Manager and Surface Area settings are correct for
the Instances and the SQL browser.

When I added BCM there were exisiting instances on the SQL servers on the
PCs. These support another Business app. I suspect the issue may be there
somewhere.

Any ides, tips, pointers, URLs.

Thanks.

On Sep 20, 6:17 am, dpminusa discussions.microsoft.com>
wrote:

I disabled the Firewall on the two systems. They are both on a LAN behind a
Server Firewall so we are not concerned.

By using the yourserver\mssmlbiz,5356 I am able to get connected from A to B
but not B to A. The difference is that A is on a system that has Instances
of an application on it as well. I was surprised to see the BCM was
installed into MICROSOFTSMLBIZ on A even though an instance of MSSMLBIZ was
also created.

When I try the sqlcmd you suggest (in a related post) from the cmd line o B
I can see that even changing the values for the Node, Istance and data base
name to those needed on A the failure message refers to the instance name on
the system I am attempting the commection from B.

Is BCM only capable of sharing if both servers have exactly the same
instance name?

I am stuck at the moment. I was thinking of removing the Apps from A and
installing BCM first then adding them back to see if BCM ends up in MSSMLBIZ
so it matches the B instance name. Assuming this is the root of the problem.

Also, the reports do not run on either system. I get a cannot produce
message try again when running them locally on either system, not when
remotely sharing.