I've got a WPF application that does a very simple image playlist. It needs to be controlled by a web browser, so I opted for ASP.NET MVC, being familiar with it.
If I publish and install the WPF app to my local computer, and run the MVC web app through VS2010 locally, it works perfect. I can control the WPF app via a web browser. However, when I install the WPF app on the production box and change my endpoint address in my web.config to the production box, I get the following:
The remote server returned an error: (503) Server Unavailable. [WebException: The remote server returned an error: (503) Server Unavailable.]
System.Net.HttpWebRequest.GetResponse() +6038435 System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +48[ServerTooBusyException: The HTTP service located at http://192.168.10.74:8000/ServiceModelSamples/Service/PlaylistMan is too busy. ]
As noted, it works fine if both the installed app and the MVC web app are on my development box (using full internal IPs rather than http://localhost)
Just to be sure, all firewalls are disabled.