Common Issues With Nomadix


Nomadix offers a line of access gateways that allow multiple users to connect to the Internet. The gateways work in small locations, such as coffee shops, or large ones, such as airports and hotels. If a user has problems connecting to the Nomadix gateway, check the device's settings. Incorrect settings or an non-operational server commonly prevent users from accessing the Internet.

Home Page Redirection

  • When a user connects to the Internet through the Nomadix gateway, he normally sees the home page you have specified. If this does not happen, you may not have enabled home page redirection. If you have enabled this feature, check the home page URL to ensure that it is correct. If the problem continues, the DNS settings may not be configured properly. Check and correct the settings. The server hosting the home page may not be working at the moment. Wait a few minutes and try to access the home page again.

No IP Address

  • Dynamic Host Configuration Protocol (DHCP) is a protocol that assigns users a different IP address when they connect to the Nomadix gateway. If a user does not receive an IP address, the gateway's DHCP relay may be configured improperly. Check the external DHCP server's IP address, and use the "ping" command to test for communication errors. If the server's IP address is correct, make sure that you have entered the correct subnet address. Use as the default subnet. Ensure that the internal DHCP settings are correct -- if they are incorrect, the DHCP relay service will not work.

No Communication with Authorize.Net

  • allows you to bill users for the ability to connect to the Nomadix gateway and the Internet. If you attempt to use the AAA internal Web server to log in to, you may be unable to connect. needs to communicate with the server through port 1111. If your firewall has blocked or disabled this port, you cannot access the site. Open port 1111 and allow to use it.

Cannot Route to Domain Name

  • If Nomadix users can receive an IP address but they cannot access any websites, reconfigure the DNS settings. Make sure that the primary, secondary and tertiary DNS settings are correct. Also check the domain and host settings. If you know that the settings are correct, the problem is most likely the DNS server. Call the Internet service provider and ask whether the server is down. If it is, you must wait for your service provider the restore the server.

Related Searches


  • Photo Credit Polka Dot RF/Polka Dot/Getty Images
Promoted By Zergnet


Related Searches

Check It Out

Geek Vs Geek: Robot battles, hoverboard drag race, and more

Is DIY in your DNA? Become part of our maker community.
Submit Your Work!