|.NET remoting can be accessed over any protocol, including TCP, HTTP or SMTP.
|.NET web services can be accessed only over HTTP.
|It is fast.
|It is slow.
|It can be hosted either in IIS or in another container.
|It can be hosted in IIS, by default.
|It requires the client can be built using .NET, enforcing homogeneous environment.
|Web services support heterogeneous environments which means client and remote object can be built in any platform.
|It needs to maintain security on its own if it's not hosted using IIS. When hosted in IIS, .Net remoting is also as reliable as web services.
|.Net web services are hosted using IIS, they are reliable.
|In .Net Remoting, Singleton objects can share state, whereas if you don’t need to maintain state, you can use Singlecall objects.
|Web services are a stateless in nature like web application. You need to use state mechanism to retain state. You can use the session or application object to maintain the state.