There was an error downloading 'http://10.144.64.27:83/FetchManager.svc '. Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.144.64.27:83 Metadata contains a reference that cannot be resolved: 'http:xyz/../abc.svc'. There was no endpoint listening at 'http:xyz/../abc.svc' that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond http:xyz If the service is defined in the current solution, try building the solution and adding the service reference again.
Quote:If you can access the .svc endpoint and ?wsdl page correctly from remote client machine(while the other users cannot), I'd suggest you try putting a simple ASP.NET aspx page in the same application to see if the same access issue also occurs for that user. If the same issue occurs for web page, the problem is not WCF specific, but is related to the remote access of the IIS web directory from remote client. Is there any authentication enabled on IIS or have you checked if anonymous authentication is enabled? Also, another thing you can check is if you have enabled "multipleSiteBindingsEnabled" setting. This can help make your IIS hosted WCF service be able to accept requests under various host names(local servername and external DNS names...). This setting is WCF 4.0 specific
var
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
Submit an article or tip