Best Solutions: Troubleshooting LG Localhost:7100 Unavailable


During your load test, you may experience issues of having your load generator localhost:7100 become unavailable. This article provides best practices and serves as guidance for you to attempt to resolve this issue.

The Best Solutions for you to Consider

  1. Eliminate a conflicting process: The first question is whether this problem happens intermittently or reliably. If it’s intermittent, it might be something else running that’s taking over port 7100 on your computer. An antivirus suite or firewall rule could be the cause of this issue. To better understand if it is an antivirus suite or firewall rule, open a command prompt and run a netstat command to find the process ID (PID) that could be using the same port as that of the NeoLoad load generator (7100).
    1. netstat -na | find “7100” > 7100.txt (Find the PID for port 7100 and then kill this process to see if NeoLoad now functions properly.): netstat -aon | find “7100” > 7100.txt
  2. Refresh the localhost load generator: An easy way to re-connect to your localhost load generator is to click “Refresh” in the “Runtime” section of NeoLoad. 
  3. Remove the localhost load generator, add back in: A different approach could be to select the localhost:7100 load generator (“Runtime” and delete it).
    1. Click Refresh, and NeoLoad will use its ability to search for load generators and will put the localhost:7100 back on the list. 
  4. Change the NeoLoad port: Another option is to change the default port of the NeoLoad load generator to something other than 7100. This can be accomplished by making an edit to two different core NeoLoad files:
    1. Open “” file and change the following line to have a different port like maybe 7150 (port=7100)
    2. Open “” file and change the next line to have a different port like maybe 7150 (server.port=7100)

These files are located in your NeoLoad installation directory in the “conf” folder. Make sure that both changes have the same port number that you choose. You will need to have NeoLoad closed to work on these files and then restart NeoLoad for the new changes to take effect.

Additional Considerations

  1. Add a Windows firewall rule: In Windows Firewall Rules, you might see some entries for NeoLoad (Controller as process NeoLoadGUI.exe) and the load generator, labeled as Java SE Runtime and has an executable of “java.exe.” Try adding port 7100 into a new Windows Firewall rules.
  2. Close antivirus: Validate there is no antivirus causing issues.
  3. Install a new NeoLoad to a separate folder: Try a fresh installation of NeoLoad into a new folder location.
  4. Check for a conflict with another Java process: Start a virtual check user and look in task manager for a “java” process that is started. It’s possible it could be blocked.

NeoLoad Port Information

To use NeoLoad with a firewall, it may prove necessary to open some ports on the network interface of the controller, load generator, and monitoring agent.

Next Steps: Review Documentation or Talk to Us

  • Check out all of the content included within NeoLoad documentation.
  • Want to discuss further, contact support.

Learn More about Performance Testing & Load Testing

Discover more load testing and performance testing content on the Neotys Resources pages, or download the latest version of NeoLoad and start testing today.

Leave a Reply

Your email address will not be published. Required fields are marked *