dotnet remoting: I'm working on a project which involves clients calling into=
server and server calling back to the clients=2E I use =2ENet=
Remoting to do that (setting TypeFilterLevel to Full and=
creating the client and server sink providers on both sides)=2E It=
works great and fine within my intranet=2E

However, problem occurs when I start running the same thing over=
the internet so that the server and clients are on different=
domains=2E Now the client can invoke methods on the server but the=
server cannot call back to the clients=2E It just timed out=2E

I've been searching through the net and trying different settings=
but still don't have a clue on how to get it to work=2E Any helps=
are appreciated=2E Sorry for the bad English since I'm not a=
native speaker=2E

--------------------------------
From: John Chan

-----------------------
Posted by a user from =2ENET 247 (http://www=2Edotnet247=2Ecom/)

[quoted text, click to view]

The standard .NET Remoting channels are not bidirectionals, which means
that whenever the server needs to callback into the client, it needs to
open a new channel to the client application. The client application
therefore becomes the server and the server application becomes the client.
If your client application is behind a firewall, the server application
won't be able to open this new channel since the client's firewall will
deny the connection.

There are 2 possible solutions to your problem:
- Specify a port when creating the channel in the client application and
open this port in the client application computer's firewall. Not the best
solution since this opens a potential security hole and some users may not
know how to open ports in their firewall. And you'll still have problems
with NAT routers.
- Use Genuine Channels (http://www.genuinechannels.com). It provides
bi-directionnal channels that work like a breeze through firewall and NAT
routers. It also provides loads of other usefull features. Once you'll have