Existing ADVANTESCO clients can use this form to receive immediate tech support.
Looking to save money?
No one likes to be charged for an issue they could have fixed themselves. Before you fill out this form, follow this troubleshooting guide to ensure the issue is not something you can resolve yourself.
Figuring out what the problem is when something is not working right is a challenge. Our expert engineers have tons of experience and have put together some basic tips to help you solve some issues on your own. If you’re not able to get things working using these tips, contact us for assistance.
It’s funny but true: a reboot of your computer or device can fix a lot of issues. If an app is acting up, quit and open again.
Sometimes the issue is just on your computer, but not affecting anyone else in your office. Asking a co-worker to verify if they see the issue as well helps us narrow down if it may be a computer specific issue/setting or a broader issue.
Step 1: Status LED Lights
You always start with the device in front of you and as such the status lights and the display panel are a great place to start with the trouble shooting guide. On the smaller Balance devices and the MAX devices there are a variety of status lights that can help understand the basics of what is happening with the device, this can be the first thing checked by the user on a site in order to confirm if the device is available to access, If the cable is connected or if the wifi is available. The status lights and info panel on the larger Balance devices can act as the first line in providing diagnosis on a router before even logging on to it.
Step 2: Dashboard WAN status
There are various states that may find the WAN in and what each of these states can means:
No cable detected - cable isn’t detected
Connecting - cable is detected and port negotiation is occurring
Obtaining IP address - obtaining DHCP from provider and that can be either an ISP device or the ISP directly.
WAN failed ping test - Health check failed. Message will be based on the 3 types of health check which are Ping, DNS and HTTP
No SIM card detected - Sim card isn’t inserted of the Sim card needs cleaning, reseating or replacing.
No device detected - This occurs when the cellular module is reset. Inserting a new sim or swapping sim cards should trigger this message as the device will reset the cellular module.
Connected - The connection is working, health checks are successful.
Connected to - This is a WI-FI as WAN connection and the SSID and signal strength is known.
Step 3: Dashboard - SpeedFusion Status
There are five states that the tunnel can be in and each can give a clue as to why the tunnel won’t fully establish.
Starting - The system knows about the profile and is either waiting for a connection or is trying to connect to the remote peer. If stuck here then checking the remote device ip addresses are set correctly is first on the list followed by external firewall closely in second.
Authenticating - The devices can see each other and begin Authentication. If stuck here then check Encryption setting and Peer ID settings is usually where you will find the issue.
Creating Tunnel - Authentication is successful and the tunnel is now being configured. Stuck at this state means that no tunnel can be established and checking that the UDP data port on 4500 can get through any external firewalls often yields good results.
Updating routes - The tunnel is now created and the devices exchange routes. If stuck here then it is likely there is a route conflict meaning the connection can’t be created.
Established - The tunnel is authenticated, established and routing info has been exchanged.
Step 4: Wi-Fi Access Point
This either shows the local AP status on devices where this is available or if you are using the device as an AP controller it shows information regarding the online status of the managed access points as well as showing the number of connected clients.
Step 5: Device information
The device information panel gives the best overview of how the system is performing by showing live overall throughput and CPU usage along with the uptime which can help figure out if a reboot event has recently occurred. The temperature is also shown and in applicable models the fan speed is also shown.
Step 6: Event logs
Better and clearer information, for instance:
DHCP - option to see the service status (available IP, consumed IP) and the ability to stop/start the service if it is suspected of having or causing an issue.
PepVPN - More logging info regarding when the connection is trying to establish and a clear message to tell the user what happened during the connection attempt such as “bad shared password” etc.
More information about changes made - not just “Changes applied”
Step 7: Routing Conflicts
If nothing of the above helps, please open support ticket.