tag:blogger.com,1999:blog-27232680.post8641340995430867854..comments2024-03-20T06:54:32.435+01:00Comments on Plastic SCM blog: Troubles in .NET remoting when IP changesF3RD3Fhttp://www.blogger.com/profile/11524626976811746062noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-27232680.post-25456076590773959722009-06-05T12:19:25.940+02:002009-06-05T12:19:25.940+02:00We have a slightly different setup but the same is...We have a slightly different setup but the same issue. We're also using .NET 2.0. Our client devices have a docking station they can use for hard-wired network access but they also have a wireless module they use when lifted from the docking station. When switching from hard-wired to wireless or vice versa the NIC and IP address they use to connect to the server changes. The client device still gets its message sent to the server but the server seems incapable of figuring out where to send the return message. It seems it's still trying to send the return message to the previously used (now invalid) network card of the client and doesn't notice the message it just received didn't originate from there... Hopefully we can fix this by reinitializing the objects on the client side when the connection status of its network adapters changes.mtijnhttps://www.blogger.com/profile/08339010177289479677noreply@blogger.comtag:blogger.com,1999:blog-27232680.post-71650643181354665432008-11-08T17:25:00.000+01:002008-11-08T17:25:00.000+01:00Yes, the problem is still in .NET 2.0 as I have ru...Yes, the problem is still in .NET 2.0 as I have run into it also, in a situation where the server has a dynamic address. I am planning on handling this scenario by detecting the failure to connect, and re-establishing a new connection, if necessary by doing the DNS lookup myself and connecting by IP address.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-27232680.post-83208467486186460312008-10-29T00:58:00.000+01:002008-10-29T00:58:00.000+01:00Interesting article! I'm currently developping a "...Interesting article! I'm currently developping a "quick" client/server solution to administer and run some batch-work run by night, using Remoting for the communication. <BR/><BR/>I'll do the tests tomorrow to see if the problem is still present in framework 2.0 and let you know ! :PAnonymousnoreply@blogger.com