NeoRouter Free

Troubleshooting NeoRouter Free: Common Issues and Fixes

NeoRouter Free provides a lightweight way to create virtual private networks for remote access and file sharing. Below are the most common problems users encounter with NeoRouter Free and clear, step-by-step fixes.

1. Can’t connect to NeoRouter network (client fails to join)

Possible causes: network/server offline, incorrect server address, firewall/NAT blocking, or incorrect credentials.

Fix:

1. Check server status: Verify the host running the NeoRouter server (Relay or Server) is powered on and the NeoRouter service is running.
2. Verify server address: Use the server’s public IP or DNS name configured in the client. If using the built-in Relay/Server name, confirm it hasn’t changed.
3. Test connectivity: From the client, ping the server IP (or run tracert/traceroute) to confirm basic reachability.
4. Firewall/port check: Ensure TCP/UDP ports NeoRouter uses (default TCP 32976 and UDP 32976 for peer connections and relays) are open on server and any intermediate routers. Temporarily disable host firewall to test.
5. NAT traversal: If both endpoints are behind strict NATs, enable port forwarding for the server or configure a public Relay. Check UPnP on routers.
6. Credentials: Re-enter the network name, user name, and password. If using certificates or keys, confirm they match.
7. Logs: Examine client and server logs for specific error messages and search NeoRouter documentation for those messages.

2. High latency or poor performance

Possible causes: slow internet link, relay fallback, encryption overhead, or misconfigured MTU.

Fix:

1. Check link speed: Run speed tests on both ends to confirm available bandwidth.
2. Avoid relays: Ensure a direct peer-to-peer connection is used. If the connection is relayed through NeoRouter servers, configure proper port forwarding or use a public Relay with better bandwidth.
3. Reduce encryption overhead: If encryption is optional and you can accept reduced security for speed, test with encryption disabled (only on trusted networks).
4. Adjust MTU: Lower MTU on the virtual adapter (e.g., to 1400) to reduce fragmentation.
5. Prioritize traffic: Use QoS on local routers to prioritize NeoRouter traffic if available.
6. Server capacity: Ensure the server/relay machine has enough CPU and RAM; offload relays from low-powered devices.

3. Devices show as offline even when reachable locally

Possible causes: incorrect virtual adapter bindings, DNS issues, or NeoRouter service not bound to the correct interface.

Fix:

1. Confirm local reachability: Ping the device’s local IP address to verify it’s on the LAN.
2. Restart NeoRouter service: Restart the NeoRouter Client/Server service on the device showing offline.
3. Virtual adapter check: Ensure the NeoRouter virtual network adapter is enabled and has a valid IP assigned by NeoRouter.
4. DNS/name resolution: If you rely on hostnames, flush DNS caches (ipconfig /flushdns on Windows) and confirm NeoRouter’s internal name resolution is working.
5. Rejoin network: Remove and re-add the device from the NeoRouter network to refresh its state.

4. File sharing or remote desktop not working over NeoRouter

Possible causes: Windows firewall, file sharing settings, RDP configuration, or permissions.

Fix:

1. Enable file sharing/RDP: On the remote machine, enable file sharing and Remote Desktop (or the specific remote tool you use).
2. Windows Firewall: Add inbound rules to allow SMB (TCP 445), RDP (TCP 3389), or your application ports on the NeoRouter virtual adapter.
3. Use IP directly: Connect using the NeoRouter-assigned virtual IP rather than hostname to bypass name resolution issues.
4. Permissions: Confirm user accounts and file permissions allow remote access.
5. Test local access: From another device on the NeoRouter network, attempt to connect to the service to isolate the issue.

5. NeoRouter client crashes or won’t start

Possible causes: corrupted installation, conflicting software, or driver issues for the virtual adapter.

Fix:

1. Reboot: Restart the system to clear transient errors.
2. Run as admin: Start NeoRouter with administrative privileges.
3. Reinstall: Uninstall NeoRouter, reboot, then download the latest NeoRouter Free installer and reinstall.
4. Check for conflicts: Disable VPNs, other virtual adapters, or security software temporarily to test for conflicts.
5. Driver issues: Remove and reinstall the NeoRouter virtual network adapter via Device Manager (Windows) or equivalent.
6. Logs: Capture application logs and Windows Event Viewer entries for crash details.

6. Authentication or permission errors

Possible causes: user account mismatch, expired tokens, or incorrect network roles.

Fix:

1. Confirm account: Ensure the username and password are correct and match the network administrator’s records.
2. Recreate user: Delete and recreate the user account in the NeoRouter management console.
3. Sync time: Make sure system clocks are reasonably synchronized; large clock drift can cause token/credential issues.
4. Roles/permissions: Verify the user has sufficient rights to join the network and access resources.

7. Relays not functioning or excessive relay usage

Possible causes: relay server down, misconfigured relay, or blocked ports.

Fix:

1. Check relay status: Ensure the relay service is running and reachable.
2. Open relay ports: Confirm ports used by the relay are open and forwarded properly.
3. Monitor usage: Use server logs to see why peers fall back to relays—likely NAT traversal failures.
4. Use a stable public relay: If self-hosted relay is unreliable, consider a well-connected public relay.

When to collect logs and what to include

If basic fixes fail, gather:

• NeoRouter client and server logs
• Operating system event logs
• Virtual adapter configuration and IP details
• Ping/traceroute outputs to server/peers Provide timestamps and exact error messages when seeking help.

Quick checklist (useful summary)

• Confirm server/service running
• Verify server address and credentials
• Open/forward NeoRouter ports (default 32976 TCP/UDP)
• Restart NeoRouter services and devices
• Test direct IP connections over the virtual adapter
• Check firewalls and permissions
• Reinstall client if corrupted

If you want, provide the specific error message or a log snippet and I’ll suggest targeted steps.