In its initial set-up .NET remoting uses no authentication/authorisation mechanism at all. If all clients of your remoting services are members of a Windows Domain Controller (DC), you can host your remoting services on IIS 5.x and rely on Window's integrated security (this will be an easy to set-up solution for your company's intranet). But if you do not want to store all your remoting service clients on a DC and/or your clients will not have access to this DC (e.g. you're offering an internet service), then you might have a look at our Remoting Security Solution.

With the help of this solution you gain the ability to silently print PDF documents (i.e. without the need to interact with the Adobe Acrobat Reader) from within any application capable of instantiating ActiveX objects (e.g. Microsoft Office, Internet Explorer, .NET). The PDF documents may be referred to either by an absolute file path or by an http URL. Proxy authentication is supported by default. Additionally, you gain access to all printers (local and network) installed on the local machine.