Since we made the last PCT-updates for EOF V.4, we cannot send any documents via EOF, only get the error message "TunnelProxy connect error". We made this updates on 24/02/2009 and did no other changes in configuration of our server.
We have installed V.4 on Windows Server 2003.
Also a re-installation of EOF-Server brought no success.
New Installation on a single machine brought error "forbidden".
Please help!
TunnelProxy connect error
Re: TunnelProxy connect error
Dear Sille,
The Tunnel proxy error is mostly brought about by the absence of , or the incorrect entry of proxy server information
within online filing. Please check the settings section of the Server Manager and check your installations guide on how
to , or contact support for further help.
Secondly, the error 'forbidden' is unclear. This seems like an error received at sending, and has to do with the actual
URL/server of the receiving office you are attempting to send to. It has to be the right receiving office for which the
particular smart card you are using is valid/authenticated. If unsure, contact support pls.
Martin Adu
Installations
Please help!
Since we made the last PCT-updates for EOF V.4, we cannot send any documents via EOF, only get the error message "TunnelProxy connect error". We made this updates on 24/02/2009 and did no other changes in configuration of our server.
We have installed V.4 on Windows Server 2003.
Also a re-installation of EOF-Server brought no success.
New Installation on a single machine brought error "forbidden".
Please help!
The Tunnel proxy error is mostly brought about by the absence of , or the incorrect entry of proxy server information
within online filing. Please check the settings section of the Server Manager and check your installations guide on how
to , or contact support for further help.
Secondly, the error 'forbidden' is unclear. This seems like an error received at sending, and has to do with the actual
URL/server of the receiving office you are attempting to send to. It has to be the right receiving office for which the
particular smart card you are using is valid/authenticated. If unsure, contact support pls.
Martin Adu
Installations
Please help!
Since we made the last PCT-updates for EOF V.4, we cannot send any documents via EOF, only get the error message "TunnelProxy connect error". We made this updates on 24/02/2009 and did no other changes in configuration of our server.
We have installed V.4 on Windows Server 2003.
Also a re-installation of EOF-Server brought no success.
New Installation on a single machine brought error "forbidden".
Please help!
Re: TunnelProxy connect error
Hi,
Recently we started installation and testing of Epoline. We also get the "TunnelProxy connect error". We checked the settings and everyting related to the proxy-entries. Can I ask how you solved the problem, maybe that can help us?
Best regards,
Paul
Recently we started installation and testing of Epoline. We also get the "TunnelProxy connect error". We checked the settings and everyting related to the proxy-entries. Can I ask how you solved the problem, maybe that can help us?
Best regards,
Paul
Re: TunnelProxy connect error
At last we made a reset on our router, that worked.
Re: TunnelProxy connect error
We (paberg and I) were able to reproduce the error on another system and found a possible workaround.
The thing is that after setting the proxy settings to a non-authenticating proxy, I run as test overhere, the submission of the file
towards EPO worked flawlessly. Apparently the application won't work properly once connecting to our BlueCoat authenticating
proxy. We've choosen to ask our service-partner to exclude authentication for urls matching epoline.org and this seems
to have done the trick for now.
Hope this gives some info for the technical guys at EPO to come with a patch or something; I think this application is used in other enterprise networks and this problem is not uncommon.
Good luck,
Leon
The thing is that after setting the proxy settings to a non-authenticating proxy, I run as test overhere, the submission of the file
towards EPO worked flawlessly. Apparently the application won't work properly once connecting to our BlueCoat authenticating
proxy. We've choosen to ask our service-partner to exclude authentication for urls matching epoline.org and this seems
to have done the trick for now.
Hope this gives some info for the technical guys at EPO to come with a patch or something; I think this application is used in other enterprise networks and this problem is not uncommon.
Good luck,
Leon