If client and server belongs to same operation system then 
we have to go with remoting services..............

when the word iteranet comes in pic we should prifer 2 use 
with condistion that saring with lot of pc

if the two systems are in dotnet platform

I don't know what Sisir is talking about... Remoting is 
something like web services. You might decide to opt for 
Remoting instead of web services in following cases...

1) Client and server platform is fixed
2) Protocol is NOT fixed. (Like web services strictly work 
on HTTP protocol)
3) Where object serialization is to be done strictly 
through CLR.
4) Where platform is fixed i.e. .Net framework.

when both the server and client r under our control then we 
use .net remoting.

Remoting can be prefered 
1. Both server and Client sit in different machine.
2. Both server and client are .NET applications
3. The state of the objects transfered accross the network 
should be maintained.
4. The objects of the IDictionary interface should be 
transfered accross the network.

Remoting can be used for .net to .net communication in
distributed environment

Remoting is used for .Net to .Net communication and in case 
of Remoting we can use protocol other than 
HTTP.Serialization in .Net remoting is handled by CLR 
in .net Remoting.