A CCESS G ATEWAY362 TroubleshootingCommon ProblemsIf you are having problems, you may find the answers here.Problem Possible Cause SolutionWhen using the internal AAAlogin Web server, you cannotcommunicate withAuthorize.Net.The internal AAA login servercommunicates withAuthorize.Net on a specifiedport which is not enabledwithin the company’s firewall.Enable communications withAuthorize.Net on port 1111.When a subscriber who isenabled with DHCP logs ontothe system, they are notassigned an IP address.The DHCP relay is enabledwith an incorrect IP addressfor the external DHCP server.Check the IP address for theexternal DHCP server. Ifnecessary, test thecommunication with the “ping”command.The DHCP relay is enabledwith the correct IP address forthe external DHCP server, butthe DHCP server ismisconfigured.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 AccessGateway are 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 the primary,secondary, and tertiary DNS).The DNS server is down. Check with the serviceprovider. Is the DNS serverdown?
