Common Problems - Nomadix AG 2100 User Manual

Wireless gateways
Hide thumbs Also See for AG 2100:
Table of Contents

Advertisement

AG 2100

Common Problems

If you are having problems, you may find the answers here. An updated version of this list can
be found at:
www.nomadix.com/techsup.
Problem
When using the internal AAA
login Web server, you cannot
communicate with
Authorize.Net.
When a subscriber who is
enabled with DHCP logs onto
the system, they are not
assigned an IP address.
Subscribers are unable to
route to a domain name, but
they can route to an IP
address.
Troubleshooting
Possible Cause
The internal AAA login server
communicates with
Authorize.Net on a specified
port which is not enabled
within the company's firewall.
The DHCP relay is enabled
with an incorrect IP address
for the external DHCP server.
The DHCP relay is enabled
with the correct IP address for
the external DHCP server, but
the DHCP server is
misconfigured.
The DHCP relay is disabled
and the DHCP service
settings in the AG 2100 are
misconfigured.
The DNS server settings are
misconfigured.
The DNS server is down.
Solution
Enable communications with
Authorize.Net on port 1111.
Check the IP address for the
external DHCP server. If
necessary, test the
communication with the "ping"
command.
Check the external DHCP
server settings (for example,
is it configured to a routable
class of IP addresses? Are
there enough IP address
specified? If you specified a
subnet, is it correct?). If you
suspect the subnet, try using
255.255.255.0
Check the internal DHCP
service settings.
Check the DNS settings (host,
domain, and the primary,
secondary, and tertiary DNS).
Check with the service
provider. Is the DNS server
down?
301

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents