My problem is that I have three objects (two are remotable and one is
not) on the same server that cannot talk to each other without crossing
remote boundaries. I would like the non-remoting object to talk to the
other two who are remoting objects without crossing remote boundaries.

Is this possible and if so, what design could I use to make this
effective? The only way I know how to get an instance of the remote
object is to cross remote boundaries and use the
RemotingServices.Connect(method) or the Activator to get the instance
on the server. Any help would be appreciated!

Thanks,
Justin

Are all of these object located in the same AppDomain? If no - then
Remoting is the only way to make them "connected"

Yes, they are in the same appdomain and running in the same windows
service.

the most simple and straightforward way is to use some kind of static
registry to store pairs<object name - access point to object (like
reference to object or object factory/pool etc). This solution can be
applied in small applications. Without additional information about
application design it is impossible to provide more elegant solution