> We found that adding binto="127.0.0.1" to our channel resolves our problem
> but I will look into this new IPC channel.
>
> Thanks
>
> "James Westgate" wrote:
>
>> 1. In .NET there is a new IPC channel for inter process communication.
>> This may bypass the network layer..
>> 2. You may want to try installing a loopback adaptor.
>>
>> RF wrote:
>> > Hi,
>> >
>> > We built two application that communicate with each other using .Net
>> > remoting on the same machine, essentially replicating what we used to
>> > be able
>> > to do with DCOM when one application controls another on the same
>> > workstation.
>> >
>> > Everything works fine until the Network card is not active anymore
>> > (WiFi
>> > connection). The odd thing is that we have another application the
>> > communicates through sockets and that one keeps working.
>> >
>> > Is there a way to configure .Net remoting or the workstation to make
>> > this
>> > work?
>>

RF wrote:
> Hi,
>
> We built two application that communicate with each other using .Net
> remoting on the same machine, essentially replicating what we used to be able
> to do with DCOM when one application controls another on the same workstation.
>
> Everything works fine until the Network card is not active anymore (WiFi
> connection). The odd thing is that we have another application the
> communicates through sockets and that one keeps working.
>
> Is there a way to configure .Net remoting or the workstation to make this