Nomadix Access Gateways, User Manual, Page: 306 / 330

A
CCESS
G
ATEWAY
294 Troubleshooting
Common Problems
If you are having problems, you may find the answers here.
Problem Possible Cause Solution
When using the internal AAA
login Web server, you cannot
communicate with
Authorize.Net. The internal AAA login server
communicates with
Authorize.Net on a specified
port which is not enabled
within the company’s firewall. Enable communications with
Authorize.Net on port 1111.
When a subscriber who is
enabled with DHCP logs onto
the system, they are not
assigned an IP address. The DHCP relay is enabled
with an incorrect IP address
for the external DHCP server. Check the IP address for the
external DHCP server. If
necessary, test the
communication with the “ping”
command.
The DHCP relay is enabled
with the correct IP address for
the external DHCP server, but
the DHCP server is
misconfigured. 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
The DHCP relay is disabled
and the DHCP service
settings in the Access
Gateway are misconfigured. Check the internal DHCP
service settings.
Subscribers are unable to
route to a domain name, but
they can route to an IP
address. The DNS server settings are
misconfigured. Check the DNS settings (host,
domain, and the primary,
secondary, and tertiary DNS).
The DNS server is down. Check with the service
provider. Is the DNS server
down?