The Aptora Mobile II server and software configuration requires some preliminary steps in order to make the program work properly and are generally required for configuration. Aptora Technical Support cannot provide any configuration assistance unless the following are obtained.
If you are using a wireless device that acts as your modem and router you will need to verify with the device’s service provider that it supports both port forwarding and a static IP address. Make sure to setup port forwarding for your device by logging into the site used to manage the device.
Anti-Virus/Security software such as AVG can block the connection to your domain. You will need to verify that IIS; Http and Https are allowed through the security program.
Trouble shoot internal connections by using ‘localhost’ to verify the site is configured properly and can connect internally.
To do so go to IIS| Application Pools| Aptora Mobile II| Right click and select “Edit Bindings”. Click the ‘Add New’ button to add a new binding, type in ‘localhost’ as the domain name, enter port 80 and click ‘OK/Save’. Select this binding and hit the browse button to ensure the site can connect internally. When it does connect using ‘localhost’, but does not with the standard settings, this usually indicates an issue with the router, firewall or antivirus/security software blocking the connection.
Obtain a Public Static IP Address
Many customers utilize different types of internet connectivity such as Dial-Up, DSL, cable internet, Fiber, and canopy fixed wireless systems. DSL, Fiber, Cable, and canopy fixed wireless are typically on a dynamic network (DHCP); every time the modem is restarted, a different public IP address is assigned. Fiber and canopy fixed wireless users periodically have their IP leases changed as well, so using a dynamic public IP address is not compatible (or recommended) with Aptora Mobile II.
Because of the dynamic nature of end-user internet connections, for ease of use and continuity, it is absolutely necessary for you to obtain a static public IP address.
Contact your ISP (Internet Service Provider) and request a static public IP address. You will need this if you wish to access your Aptora Mobile II server from outside your server’s network.
Internal Network IP Address Setup
You will need to set the server computer to an internal static IP address. Depending on the version of Windows running on the server machine (e.g. Windows Server 2003, Windows 7, Windows Server 2008, etc.), the exact location and appearance of the windows and forms to do so may vary. An internal IP address is an IP address that is only accessible from inside of your network. It is recommended that your IT professional set the Aptora Mobile II server machine to a static IP address far above the normal range of addresses used by your modem, router, or DHCP server.
- Example: Most end-user modems or routers utilize the IP range of 192.168.1.x as their default IP address range. With the assistance of your IT professional, determine what the best range is for your server.
Note: The following are suggestions. Please verify with a qualified IT professional for advice or with any questions on your particular setup.
Server Configuration on Local Area Connection
Configure the server as follows in the IPv4 interface on the Local Area Connection:
Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0
Preferred DNS Server: _____. _____._____._____
Alternate DNS Server: _____._____._____._____
The preferred and alternate DNS entries must be obtained from your ISP or IT Professional.
Most small office and home routers are set to DHCP (Dynamic Host Control Protocol) which means that when a computer is turned on or logs onto a network, the computer sends a request to the router or modem for an IP address. It is advisable to set the IP address of the server above the default range so that the other computers on the network do not attempt to steal the IP address (e.g. 192.168.1.252 from the example above) from the server hosting Aptora Mobile II. You may also want to consider assigning all of the computers on your network internal static IP addresses of 192.168.1.2 and onward. This is NOT a requirement. It simply assures that addresses are not given out on your internal network at random.