Proxy prevents access to Exchange


When setting the Exchange connection in Pronestor Display, an error shows telling that the it can't connect to the Exchange server.
When calling the Exchange Web Services (ews) from a web browser on the same server, it does reply without any issues, but the same URL fails from within Pronestor Display.


If access to the Exchange goes through a PROXY, it might be necessary to directly indicate in the settings for PRONESTOR, that a specific PROXY must be used.


Open the web.config file for Pronestor Display(c:\inetpub\wwwroot\pronestordisplay\web.config)

<defaultProxy enabled = "true" useDefaultCredentials = "true">
<proxy autoDetect = "false" bypassonlocal = "false" proxyaddress = "http://<host>:<port>" usesystemdefault = "false" />




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • Avatar
    Mark Topshøj

    Error message as seen in logfile:
    |SMSService|ERROR|Failed to validate SMS account. System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: 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
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    Fix to the error message above was to add the following in the file.

    <proxy usesystemdefault = "false" proxyaddress="http://address:port" bypassonlocal="false"/>

    Edited by Mark Topshøj
Powered by Zendesk