Hi,
Agent Vul Scan Connection from external through CSA is working fine, but when my Agent Connects from Internal i can't connect:
BrokerConfig tests are finde because the tests are using port 80.
The Problem is Vulscan is trying to connect with http://url:443 (witch isnt a valid https connection)
The Correct Connection string would be https://CORESERVER:443/WSVulnerabilityCore/VulCore.asmx
How Can i change the connection link to https or as workaround to http without port 443 in URL?
Maybe the Problem is befor that? CoreSignatureIsValid returned false
proxyhost.log
2018-10-31 10:40:19(164696-159056) proxyhost.exe:FIPS mode = 1
2018-10-31 10:40:19(164696-159056) proxyhost.exe:127.0.0.1:58639 EOS on request
2018-10-31 10:40:20(118824-159116) proxyhost.exe:FIPS mode = 1
2018-10-31 10:40:20(118824-159116) proxyhost.exe:IsProcessSigned succeeded - returning: 1
2018-10-31 10:40:20(118824-159116) proxyhost.exe:About to determine if we go direct: bRequestIsForCore = 1, g_core = MYSERVER, host = MYSERVER:443, headerHost = MYSERVER
2018-10-31 10:40:20(118824-159116) proxyhost.exe:Made direct (non-proxy) connection to MYSERVER:443
2018-10-31 10:40:20(118824-159116) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 1 numberofDirectConnectFailure = 0 csaName = bCsaSuccess = 1
2018-10-31 10:40:20(118824-159116) proxyhost.exe:bRequestIsForCore = 1
2018-10-31 10:40:20(118824-159116) proxyhost.exe:CoreSignatureIsValid returned false
2018-10-31 10:40:20(118824-159116) proxyhost.exe:127.0.0.1:58641 Unable to start session with MYSERVER:443 internal.proxyhost.directfailed sessionrc=20
maybe someone knows the problem.
thx
tom
Message was edited by: Paul Hoffmann (to anonymise the Core Name).