difficult CAO remoting problem -- dotnet remoting

allen
10/29/2003 8:41:52 PM

please don't answer this without reading the entire message. I'm not
asking about machinename.

I am trying to figure out a way to have my remoting system deal with
being behind a firewall, a NAT router or other various network
devices.

the problem is that when using a CAO will force the server to send
back the 'address' to the client. Because the people using this
particular product may not be very computer savvy,, I can't rely on
them entering an external IP (for that matter they may be behind a
dynamic IP so they would have to enter it every time which is
untenable).

what I need to know, is how exactly do I intercept where the server is
sending back the 'unique address' to the client so I can put the IP
that the CLIENT sees the server as, not what the SERVER sees itself
as?

machinename isn't a workable solution as most NAT routers available
these days won't re-route the IP from internal back to internal if the
external address is machinenamed in. Also, machinename isn't workable
for the entry reasons stated above. I need to intercept the call and
change the address sent back to the client on the fly.

dimatut2 NO[at]SPAM mail.ru
10/30/2003 1:45:38 AM

Hi Allen,

You can simply use Genuine Channels.
www.genuinechannels.com

Regards,
Dmitry.

[quoted text, click to view]

Matthew Doll
12/19/2003 1:47:09 PM

I am running into exactly the same problem. I want a client to create a
CAO (hosted in IIS) that is on a server that is behind a Cable Gateway
router. The url that is returned to the client has the internal IP
address of my server PC (ex. 192.168.0.34) not the WAN address that the
client would need to make subsequent calls to the CAO.

I tried to override the CreateObjRef function exposed in the
MarshalByRef class, but it appeared to have no effect.

*** Sent via Developersdex http://www.developersdex.com ***

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet remoting

dotnet remoting : difficult CAO remoting problem