Ok, Windows Remoting (the predecessor to WCF) is quite limiting as there are firewalling issues...basically, it will not work with a firewall, even though you have punched a hole in the firewall, the problem is the NAT'ting of the IP addresses, hence likely, you're getting a connection timed out socket error message. It might help you and re-assure that the problem may easily be remedied by allowing the traffic to be redirected, I have written an article on CodeProject which may help you. What you can do is put the application on the end point where the firewall is, put in the IP address that is facing publicly to the internet, and put the in the IP address that is to be redirected to the remoting server Feel free to contact me anytime if you so wish, Hope this helps, Best regards, Tom.
Ok, Windows Remoting (the predecessor to WCF) is quite limiting as there are firewalling issues...basically, it will not work with a firewall, even though you have punched a hole in the firewall, the problem is the NAT'ting of the IP addresses, hence likely, you're getting a connection timed out socket error message. It might help you and re-assure that the problem may easily be remedied by allowing the traffic to be redirected, I have written an article on CodeProject which may help you. What you can do is put the application on the end point where the firewall is, put in the IP address that is facing publicly to the internet, and put the in the IP address that is to be redirected to the remoting server.
Feel free to contact me anytime if you so wish, Hope this helps, Best regards, Tom.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.