Back to
DB / setup

What to do when Nex Admin in the terminal does not locate the server?

In some cases, Nex Admin may not be able to locate the server. Here are the main reasons that can cause this problem and how to solve them.


  • This feature is available to Nex subscribers. Learn more about our program subscription plans.
  • Click here to see the tutorial on how to install Nex on a local network.

1. Nex plan

The use of Nex in a local network is available to Premium plan subscribers. If your Terminal computer is not finding the Server computer, check your Nex plan. You can check this information in the top right corner of the Nex Server.

If your plan is not the Premium Plan, see here how to subscribe to Nex.

If you are using Nex with the Premium Plan, check the following steps to try communication between the two computers:

2. Updated Nex

Make sure your Nex is running on the latest version.

2.1 Click on ABOUT NEX.

2.2. Click on UPDATE.

If your Nex is out of date, the program will start the update process. If it is already updated, Nex will indicate that it is on the latest version of the program. See here how to update your Nex.

If Nex is updated, check the next step.

3. Local network

The Server and Terminal computers must be on the same local network to use the same Nex in more than one computer, connected. In other words, they need to be receiving exactly the same internet signal.

3.1 If you use computers connected via WI-FI NETWORK, check that they are both on the same network by clicking on the Wi-Fi symbol in the bottom right corner.

3.2 If you use computers via a network cable, you need to check whether they are on the same network using Command Prompt (CMD).

3.2.1 Type CMD in the start menu and open COMMAND PROMPT (CMD) on both computers.

3.2.2 Type IPCONFIG and press ENTER.

Windows will list some information regarding your network.

3.2.3 Check that the DEFAULT GATEWAY is exactly the same for both computers.

If the Default Gateway has different numbers on each computer, that means they are not connected to the same local network. It is necessary to check which modem the signal is coming from via the network cable.

If the computers are connected to the same local network, check the next step.

4. Restart modem and computer

In some cases, it may be the Internet Modem itself or Windows that is blocked.

4.1 Restart your internet modem. To do this, turn off the modem, remove all cables, wait 30 seconds and connect everything again. Wait for the internet signal to be reestablished and try again.

4.2 Restart the Server and Terminal computer.

If when restarting the modem and computers there is still no communication over the local network, check the next step.

5. Antivirus

Some antivirus program can interfere with communication between computers over your local network, preventing Nex Admin from being able to locate the NexServer.

To fix this problem, it is necessary to disable the antivirus for a few minutes and, if possible, create an exception in it for Nex to work correctly. If you suspect that the antivirus is interfering with communication over your local network, you can contact us so we can try to help you, by clicking here.

6. Windows Firewall

In some cases, Windows Firewall may prevent computers from communicating over the local network. In this case, it is necessary to disable the Firewall to try again.

6.1 Type FIREWALL in the start menu and select WINDOWS DEFENDER FIREWALL.



6.4 Click on OK.

This procedure disables the Windows Firewall. Verify that the Nex Admin can locate the NexServer. If you still can't find it, turn Windows Firewall back on in the same window where you turned it off.

7. Check the communication between the two computers

You can check communication between the two computers if they are on the same network.

7.1 Type CMD in the start menu and click on COMMAND PROMPT.

7.2 Type IPCONFIG and press the ENTER key on both computers.

7.3 Check and write down the IPv4 ADDRESS of each computer.

7.4 Type PING and the IPv4 ADDRESS number of the other computer and click the ENTER key to start a communication test.

7.5 Windows will send information packets to the reported IPv4.

7.6 If the computers are on the same network and communicating through it, there will be a response with time in ms (milliseconds) for return. Additionally, Windows will indicate how many packets were sent, received and lost. Ideally, no packet of information is lost in this process.

7.7 If the computers are not communicating, Windows will return “Destination host unreachable” or “Request timed out”. In these cases, it is necessary to check that the computers are on the same network and that it is configured correctly.

If the computers have the same Default Gateway and are still not communicating over the local network, it is necessary to check with a local network technician to analyze what could be causing the blockage.

See also:

See more Tutorials of  

DB / setup