I have an application that I inherited from the previous programmer that uses the Remote framework to communicate between a GUI client and a server talking to specific hardware. Works fine when the two are on the same box, and even when the two are in the same intranet, but goes to *(** when its deployed across the internet. Anything in particular to look for? The program hangs when the server tries to raise an event using begininvoke to get the client's attention that the hardware has had a value change. Using TCP Channel, any parameters to set or things to make sure are cleared out in the firewalls? Are there any additional parameters to set on the connections - I have a 5 second timeout at the moment between client and server.
Hi Scott, Are the network NAT'ed? Remoting works badly over NAT'ed networks, you can read more here: http://social.msdn.microsoft.com/Forums/en-US/netfxremoting/thread/6a91626a-3c44-45a1-b0f8-dbf4042f51e4/ I hope this helps. -- Patrik Löwendahl http://www.lowendahl.net [MVP] [MCT - Enterprise Application Development] Scott Berger skrev: > I have an application that I inherited from the previous programmer that uses > the Remote framework to communicate between a GUI client and a server talking > to specific hardware. Works fine when the two are on the same box, and even > when the two are in the same intranet, but goes to *(** when its deployed > across the internet. Anything in particular to look for? The program hangs > when the server tries to raise an event using begininvoke to get the client's > attention that the hardware has had a value change. Using TCP Channel, any > parameters to set or things to make sure are cleared out in the firewalls? > Are there any additional parameters to set on the connections - I have a 5 > second timeout at the moment between client and server. >
