.Net Remoting: Can the server reference an interface rather than the object?

Question

Hi all,

I am using .Net Remoting in an unusual manner whereby a single client will access many servers (this is unavoidable). To increase maintainability, it would be handy to have the server code reference an interface rather than the remoting object itself so that if a change to the remoting object is needed only the client needs to be updated.

Is this possible or is it built in that the server must reference the remote object dll directly? All of the interface examples I have found show how to allow the client to reference an interface (which makes sense as this is how remoting should be used) but I need it the other way around. Any advice or small examples would be appreciated.

Thanks,

James