[Mono-bugs] [Bug 78596][Maj] New - Certain remoting server functionality fails on PCs with dual network cards

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by admin at svwebhosting.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78596

--- shadow/78596	2006-06-07 03:58:38.000000000 -0400
+++ shadow/78596.tmp.24253	2006-06-07 03:58:38.000000000 -0400
@@ -0,0 +1,45 @@
+Bug#: 78596
+Product: Mono: Runtime
+Version: 1.1
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: remoting
+AssignedTo: lluis at ximian.com                            
+ReportedBy: admin at svwebhosting.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Certain remoting server functionality fails on PCs with dual network cards
+
+Description of Problem:
+Remoting methods fails when server has more than 1 network card.
+- The remoting server is configured to bind to eth1.
+- The server has a method that returns an object A.
+- Client receives the reference to object A correctly.
+- When executing A.foo() the request times out.
+
+After playing around with a packet sniffer I found that when the server
+sends the reference to object A it includes an the IP configured on eth0 (I
+assume this is because the object is created locally at first but then it's
+sent to the client), so when I execute the A.foo() the client actually
+tries to connect to the ip on eth0 but it times out because it should try
+to connect to eth1.
+
+
+Steps to reproduce the problem:
+I will attach an client and server example.
+
+Actual Results:
+Object reference sent to the remoting client has the wrong ip (eth0 instead
+of eth1) causing the client to timeout when executing methods
+
+Expected Results:
+Should use the ip I bind to in the remoting configuration file.
+
+How often does this happen? 
+Every time.