Ken,

Thanks for your reply.  I am a newbie in this area, and do not know about
named objects.  I haven't found a clear sample on the Web.  Could you point
me to a sample of this technique?

Thanks again!

Rob

Ken,

I tried using RemotingServices.Marshal() as you suggested.  It worked!

In the server, I replaced:
RemotingConfiguration.RegisterWellKnownServiceType (typeof (Clock), "Clock",
WellKnownObjectMode.SingleCall);
with:
Clock serverClock = new Clock();
serverClock.Number = 99;
ObjRef serverClockRef = RemotingServices.Marshal(serverClock,
"ServerClockURI");

In the client, I replaced:
RemotingConfiguration.RegisterWellKnownClientType (typeof (Clock),
"tcp://localhost:1234/Clock");
with:
RemotingConfiguration.RegisterWellKnownClientType (typeof (Clock),
"tcp://192.168.1.29:1234/ServerClockURI");

The client application happily reported that it was using clock number 99.

Next question:  For my application as it is currently designed, this will
suffice, since there will never be more than a single client communicating
with a server.  But what happens when we decide that a single server
application will manage an unknown number of printers?  In that case, I
would want my objects to be client-activated, but I still want the server to
know what objects it created.  How do I do that?

Thanks again!

Rob