VoloAccess™ User Manual
Copyright © Vololink Pty Ltd 2006-2010 V1.43 July 2010 Page 70 of 78
Advanced Data Features
Port Forward
I have configured Port Forwarding for my Web Server but still cannot access the site. Why?
First, check that the configuration settings are correct on the Admin > LAN > Port Forward page.
The Server IP address is the IP address of your machine which is running the Web Server. The
Protocol is TCP.
The second thing to check is the firewall settings on the Web Server machine. Make sure that you are
not filtering (blocking) the traffic and the port.
VPN
I have configured VPN but still cannot connect to the remote VPN server. How do I fix this?
Verify that your 3G service provider provides an externally linkable (routable) IP address. This is the
WAN IP Address which you can see on the Admin > WAN > 3G Embedded page. This address
cannot be in the following (non-routable) ranges for VPN to operate:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
These IP addresses have been reserved by the Internet Assigned Numbers Authority (IANA) for
use by private (internal) networks.
It is a known issue that some ISPs do provide internal (non-routable) IP addresses, in which
case your VoloAccess cannot be configured as a VPN host.
VPN has strict rules for security reasons. The credentials on both the remote server and your local
client have to match for VPN to work. You need to provide your WAN IP Address to your VPN Server
administrator and obtain the Server's host and network details and the authentication key to be
configured in Admin.
Each time you turn your VoloAccess off and on, your service provider allocates a new WAN IP
Address unless your account has a static address. (A static IP address can be arranged with your 3G
service provider) If your WAN IP Address is dynamic (changes each time), you will need to notify your
VPN Server's administrator to update the connection details on the Server side.
Time Server
The VoloAccess displays incorrect date and time. Why?
If after 15 minutes, the VoloAccess still doesn‟t display the correct date and time, check that a Time
Server has been enabled in Admin.
If NITZ is selected as the Time Server, the Date/Time update should occur in a matter of seconds;
however, an NTP Time Server can take considerably longer to respond.
Refer to Setting the Date and Time in the User Manual for further information.
VoloAccess fails to start normally
If the VoloAccess has been started, but the WiFi Protected Setup, Signal Strength and Mobile Network
indicators repeatedly flash at 1 second intervals, the software is trying to load but failing.
Perform the following actions to solve the problem:
Turn the VoloAccess off, wait for 30 seconds, then turn it on – the WiFi Protected Setup, Signal
Strength and Mobile Network indicators flash at 1 second intervals until ready to enter normal
operation.
While the unit is in the flashing sequence, push the reset button for more than 10 seconds – this
performs a hard reset.
Wait for the VoloAccess to restart and check its operation.
If the VoloAccess fails to start normally, return the unit for repair.
