We currently have a setup of three Windows NT 4 Servers running transaction enabled VB 6.0 components in MTS 2.0. Components from one machine will call methods of components from another machine using the Remote Components facility in MTS.

The problem we have is when we are trying to replicate this setup across a setup of three Windows 2000 Advanced Servers in the COM+ Services environment. We were successful in deploying the same transaction enabled VB 6.0 components in packages in COM+, but the issue arises when we had to get the components calling eachother across machine boundaries in COM+. Ie. we are looking for the analogy to MTS Remote Components in COM+ Services.

Can't you just use application proxies? You just export the COM+ package as an application proxy and then install that proxy on each remote machine which needs to call the components in the package.