Hi everyone
Some background info: I was required to create a wcf windows-hosted service for which I inherited from ServiceBase and created a Project installer along with an installer for the service. I have the endpoints for the service and metadata in my app.config like this(I use basicHttpBinding) :
endpoint address="http://localhost:8000/LauncherHost"
binding="basicHttpBinding"
contract="LauncherService.ILauncherService"
name="HttpConsumer"/>
endpoint address="http://localhost:8000/LauncherHost/MEX/"
binding="mexHttpBinding"
bindingConfiguration=""
contract="IMetadataExchange" />
I am testing with both a propietary app that connects to the service and is able to access methods and with the VS tool WcfTestClient; testing locally and in a test server the whole process works flawlessly (Windows 7 and Windows Server 2003)
Now, they took the package to a better secured site running Windows Server 2008 and the service is installed correctly, the problem comes when testing with a proxy. The propietary app gets stuck waiting for the channel to open and the WcfTestClient does the same, stays at "Adding service..." and it sends no error when typing the ip address instead of localhost; I remember it once worked and I could add the service but then I tried again with no luck.
The weird thing here is that if I access to the service like "http://localhost:8000/LauncherHost" it says that metadata is not available... the service is running under windows, it says started and is set to automatic and it works fine in my machine and the test server.
However, if I access the service like "http://ip:8000/LauncherHost" the test client waits forever without response.
My bet is something firewall related, I'm not in the test site, I can only access remotely at times and they've been telling me the port used for the service is open but seems to me like there's something blocking the requests... although... why can't I access the service locally either(localhost) ????
Any help would be greatly appreciated!
Submit an article or tip