c# - What could cause .NET remoting to fail but only if message sent from code running in IIS? -


have app uses remoting on tcp channel send message web app (the client) central server.

tcpclientchannel channel = new tcpclientchannel(); channelservices.registerchannel(channel, true); ipc message = (ipc)activator.getobject(typeof(ipc), remotingurl);                 // ipc class being 'remoted' message.somemethod(....); 

for part works fine on 1 particular set of web servers errors on .somemethod :-

system.io.ioexception: unable read data transport connection: connection closed. @ system.net.security.negostate.processauthentication(lazyasyncresult lazyresult) @ system.net.security.negotiatestream.authenticateasclient(networkcredential credential, string targetname, protectionlevel requiredprotectionlevel, tokenimpersonationlevel allowedimpersonationlevel) @ system.runtime.remoting.channels.tcp.tcpclienttransportsink.createauthenticatedstream(stream netstream, string machineportandsid

of course according ops there no differences between server works, , 1 doesn't...

there no hardware or software firewalls between/on sending (client) web server , receiving server.

i've put same code in console app , works fine when running on problematic sending server (even when running under app pool account).

therefore conclude fails when sending code ran in context of iis on of servers.

any idea of settings (perhaps aspnet.config or web.config or iis metabase) or else cause this.

key parts

  • works when sending web app on servers fails on others
  • on servers fail works fine when running console app
  • problem has on sending side

(one more key part googling error message - haven't done ;) - secure channel setting same on receiving , sending servers).


Comments

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - Cannot secure connection using TLS -