Appscan Network Error
Contents |
appscan network error; proxy; timeout; Watchfire; AppScan network error Technote (FAQ) Question When running IBM Rational AppScan Standard Edition, why do appscan communication error I encounter an error message, AppScan Network Error? This technote provides common
Failed Due To Communication Error Appscan
causes for why this error can occur, along with suggested tips for resolving it. Cause AppScan network error is displayed when AppScan Standard cannot access the Web site. This is an expected error when the network is not accessible from the AppScan host. This is a configuration error, and it is not specific to the product functionality. Answer There are a variety of known causes for this problem, which are detailed below. You can use these to help troubleshoot and resolve the network problem. Note: You may need to consult your network administrator and or third party vendor documentation for assistance. Known causes and suggested resolutions: The AppScan machine is not connected to the network. You need to confirm that it is physically connected using a network cable or, if wireless is in use, then you need to verify you are connected. AppScan needs to go through a proxy: Go to Scan Configuration > Communication and Proxy Enter the correct proxy information Click OK to save your settings Note: Be sure to remove these entries when trying to scan an internal site. A timeout issue or network latency. Try increasing the timeout in AppScan. Go to Scan Configuration > Communication and Proxy and increase the Communication Timeout (in seconds). The Web site's IP address is not resolving correctly. Connecting to this site, www.acme-hackme.com, returns the error message, but the IP address, 10.10.10.2, does not and you are unable to access the site from AppScan. You can verify that the site is accessible from the same box using Internet Explorer (IE). Open Internet Explorer and browse directly to the desired site. If you are looking at the test response or original response of a test, AppScan gets the F
TroubleshootingDocument; 1283298; Watchfire; AppScan; communication; server not responding; communication error; proxy not responding; Cannot connect to host; failed due to communication error; Connection established with host; Communication problems occurred while testing URL Technote (troubleshooting) Problem(Abstract) How do you diagnose communication problems when scanning my application using IBM Rational AppScan Standard? Symptom Symptom 1 Scan Log (from View -> Scan Log or ScanLog.log file under Logs folder of the AppScan Standard installation directory) may show errors in this format during the course of the scan: ... http://www-01.ibm.com/support/docview.wss?uid=swg21302596 Cannot connect to host: [IP/HOSTNAME]... ... Test [TEST_NUMBER] [TEST_NAME] failed due to communication error: ... ... Connection established with host: [IP/HOSTNAME] Symptom 2 Alternately, you may see errors like these in the System Log (from Help -> AppScan Log or AppScanSys.log file under Logs folder of the AppScan Standard installation directory): ... Warning: Communication problems occurred while testing URL '[PATH]' for http://www.ibm.com/support/docview.wss?uid=swg21283298 '[TEST_NAME]' You may also see these: ... System : Server [IP/HOSTNAME] is not responding... ... System : Server [IP/HOSTNAME] is responding again Resolving the problem Cause: A personal firewall and or anti-virus application is installed on the AppScan Standard host that is blocking outgoing connections. Resolution: Check the system to make sure that any such applications are disabled during the crawling and testing phases. Cause: A corporate firewall is dropping connections because it is recognizing them as attacks. Resolution: Check with your system administrator/IT to confirm if the corporate firewall is actually dropping connections. Issues have been encountered where a new proxy and or firewall gets installed on the network, which filters requests that in turn leads to poor scan performance by AppScan Standard. Cause: A slow Web server is denying the connections when AppScan Standard tries to send a large number of requests to it. Resolutions: Reduce the number of threads to 1 and increase the time-out to 30 seconds to see if this removes the communication entries. These options can be configured in Scan Configuration > Communication and Proxy. Once you
failed; connect CannotConnect; browser; plug-in Technote (troubleshooting) Problem(Abstract) Attempts to use Manual Explore plug-in in IBM Security communication error AppScan Enterprise results in "Network Error". Symptom The error message shown in the browser is: Network Error Failed to connect to the site (CannotConnect) Cause There may be a appscan network error number of causes of this error. One of them is incorrect proxy settingconfigured in the scan. Resolving the problem Correct proxy settings in Job -> Edit -> Connections -> Proxy Document information More support for: IBM Security AppScan Enterprise General Support Issues Software version: 8.8, 8.8.0.1, 9.0, 9.0.0.1 Operating system(s): Windows Reference #: 1684846 Modified date: 2014-09-26 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility