Check a Virtual User validity with NL-NETWORK-03 errors
Problem
When checking a User Path validity, I get NL-NETWORK-03 errors.
Solution
The User Path activity has been correctly recorded and an NL-NETWORK-03 error is displayed with the message Failed to connect to the server. This indicates that NeoLoad cannot connect to the server when the scenario is played.
If the error details are java.net.ConnectException: Connection timed out: connect for all the requests, then it would suggest that the Load Generator is using an incorrect network interface. It is necessary to edit the Load Generator settings in the Runtime > Scenario section to make sure the selected network interface allows access to the web server.
For other error details, typical causes are:
- The server is not running or is running on another port.
- A firewall or anti-spyware programmer is blocking NeoLoad access to the server.
- Incorrect proxy settings within NeoLoad. In the Proxy section of the NeoLoad preferences, it is necessary to check the proxy settings used by NeoLoad to connect to the web server.
If the error is not caused by the listed causes, it is advised to carry out a short recording on a public Internet site such as www.google.com, create a User Path and check its validity using NeoLoad. Then send all log files (all files in the NeoLoad 5.5/logs directory) to the Neotys Support team.
Home