dotnet remoting:
Hi,
I have a strange problem with remoting on a project I am working on
currently.
There's 2 problems really, not sure if they are related.
Basically, the setup we have is 2 web servers (different networks)
connecting to one application server. So we have:
A: webserver on network 1
B: application server on network 1
C: web server on network 2
Firewall has only port 443 open between network 1 and 2.
We have a configuration like this on the app server:
<system.runtime.remoting>
<application name="AppServerName">
<channels>
<channel ref="tcp"
authorizationModule="
Application.RemoteConnectionAuthentication, Application"
name="NetworkOneFacingListener"
port="443"
bindTo="192.168.89.xx"
secure="true"
authenticationMode="IdentifyCallers"
tokenImpersonationLevel="identification"
[quoted text, click to view] >
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
<channel ref="tcp"
authorizationModule="Application.RemoteConnectionAuthentication,
Application"
name="NetworkTwoFacingListener"
port="9090"
bindTo="10.84.xxx.xx"
secure="true"
authenticationMode="IdentifyCallers"
tokenImpersonationLevel="identification"
[quoted text, click to view] >
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
This works, but the odd thing is it only works for the first client
channel configured. So in the above example, the client connecting to
NetworkOneFacingListener will work, but the other won't, and when the
config swapped and server restarted it will work for the other.
This is the first problem.
The second problem is that we get intermittent issues when connecting
from C to B (different network). I added "ping" functionality to our
app server to send back objects of a certain size. For example for 1Mb
(approx), this usually sends it back within 100-200ms, but sometimes,
this only returns in over a minute. Once it starts doing this, it
continues until we restart the server and client. Sometimes it does it
straight away, sometimes it doesn't do it for a while. We can see the
application responding to the ping pretty much straight away, but the
message isn't getting back to the client for ages. When this happens,
the CPU of both servers very low.
Anybody any idea?
Thanks,
Dries.
