Hi,
I have a problem with remoting and configuring listeners on multiple
channels (different IPs, different networks).

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.xx.xx"
          secure="true"
          authenticationMode="IdentifyCallers"
          tokenImpersonationLevel="identification"
      >
      <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"
  >
    <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.

That seems like a bug in the .NET framework, but even though I can find some
posts online refering to similar issues, I haven't found a solution yet.

Can somebody from MS confirm if this is "expected" behaviour, and what would
the fix for it be?

Thanks,

Dries