In some cases, Nex Admin on a terminal computer may fail to locate the server. Here are the main causes for this issue and how to resolve them.
Nex networking is available exclusively to subscribers on the Premium plan. If your terminal computer cannot locate the server, verify your active subscription plan directly on Nex Server.
If you are not currently on a Premium plan, click here to see how to subscribe.
If your system is on the correct plan, proceed with the troubleshooting steps below.
To ensure proper network communication, both computers must be updated to the latest version of Nex.
2.1 Open Nex on the server computer and click on About Nex.
2.2 Click on Update.
If your system is outdated, the update process will begin automatically. If it is already up to date, the system will indicate that you are running the latest version, and you can move on to the next step.
To run Nex on a network, both the server and terminal computers must be connected to the exact same local network (i.e., connected to the same Wi-Fi network or plugged into the same router/modem via Ethernet cable).
3.1 If connecting via Wi-Fi, click the Wi-Fi icon in the bottom right corner of your taskbar on both computers to confirm they are connected to the same network name.
3.2 If connecting via Ethernet cable, verify network parity using the Command Prompt (CMD). Type CMD in the Windows Start menu and open the Command Prompt on both computers.
3.3 Type ipconfig and press Enter.
Windows will display details about your network connection.
3.4 Check the Default Gateway on both machines to make sure it matches identically.
If the Default Gateway IP addresses differ, the computers are on different local networks. Check which modem/router your network cables are connected to. If the Default Gateways match, move to the next step.
Sometimes, the internet modem or Windows OS may temporarily block network traffic.
4.1 Restart your modem/router. Power off the modem, unplug all cables, wait 30 seconds, and reconnect everything. Wait until your internet connection fully re-establishes, then test the connection again.
4.2 Restart both computers, the server and terminal.
If restarting the modem and computers does not restore local network communication, proceed to the next step.
Certain antivirus programs can block communication between devices on your local network, preventing Nex Admin from detecting the Nex Server.
To resolve this issue, temporarily disable your antivirus software for a few minutes and, if possible, add an exception rule for Nex. If you suspect your antivirus is causing local network interference, click here to contact our support team for assistance.
In some instances, Windows Firewall can block network traffic between computers. Disable Windows Firewall temporarily to test the connection:
6.1 Type firewall in the Windows Start menu and open Windows Defender Firewall.
6.2 Click on Turn Windows Defender Firewall on or off.
6.3 Select Turn off Windows Defender Firewall under both Private and Public network settings.
6.4 Click on Ok.
This step temporarily disables Windows Firewall. Test whether Nex Admin can now find the Nex Server. If it still cannot find the server, turn Windows Defender Firewall back on in the same settings window.
7.1 Type CMD in the Windows Start menu and open Command Prompt on both computers.
7.2 Type ipconfig and press Enter on both machines.
7.3 Locate and take note of the IPv4 Address for each computer.
7.4 On the terminal machine, type ping followed by the IPv4 address of the server computer and press Enter to test connection ping.
7.5 Windows will transmit data packets to the specified IPv4 address.
7.6 If the computers are communicating properly, Windows will display response times in milliseconds (ms) along with details showing packets sent, received, and lost (ideally 0% packet loss).
7.7 If the machines cannot communicate, Windows will return errors such as "Destination host unreachable" or "Request timed out".
In these cases, you need to check whether the computers are on the same network and whether the network is configured correctly.
If the ping test fails despite having identical Default Gateways, consult a local IT/network technician to inspect your local network setup for hidden traffic blocks.
.png){kind=spacer}
