N OMADIX AG-2000 W ™ / AG-2000 WA ™Troubleshooting 225Common ProblemsIf you are having problems, you may find the answers here. An updated version ofthis list can be found at: http://www.nomadix.com/techsup.Problem Possible Cause SolutionWhen using the internalAAA login Web server, youcannot communicate withAuthorize.Net.The internal AAA loginserver communicates withAuthorize.Net on a specifiedport which is not enabledwithin the company’sfirewall.Enable communicationswith Authorize.Net on port1111.When a subscriber who isenabled with DHCP logsonto the system, they are notassigned an IP address.The DHCP relay is enabledwith an incorrect IP addressfor the external DHCPserver.Check the IP address for theexternal DHCP server. Ifnecessary, test thecommunication with the“ping” command.The DHCP relay is enabledwith the correct IP addressfor the external DHCPserver, but the DHCP serveris misconfigured.Check the external DHCPserver settings (for example,is it configured to a routableclass of IP addresses? Arethere enough IP addressspecified? If you specified asubnet, is it correct?). If yoususpect the subnet, try using255.255.255.0The DHCP relay is disabledand the DHCP servicesettings in the AG-2000ware misconfigured.Check the internal DHCPservice settings.Subscribers are unable toroute to a domain name, butthey can route to an IPaddress.The DNS server settings aremisconfigured.Check the DNS settings(host, domain, and theprimary, secondary, andtertiary DNS).The DNS server is down. Check with the serviceprovider. Is the DNS serverdown?