Troubleshooting; Table 59 Troubleshooting The Start-Up Of Your G-1000; Table 60 Troubleshooting The Ethernet Interface - ZyXEL Communications ZyXEL ZyAIR G-1000 User Manual

G-1000 User's Guide
This appendix covers potential problems and possible remedies. After each problem
description, some instructions are provided to help you to diagnose and to solve the problem.
Problems Starting Up the G-1000

Table 59 Troubleshooting the Start-Up of Your G-1000

PROBLEM CORRECTIVE ACTION
None of the LEDs Make sure you are using the supplied power adaptor and that it is plugged in to an
turn on when I plug in appropriate power source. Check that the power source is turned on.
the power adaptor.
If the problem persists, you may have a hardware problem. In this case, you should contact
your local vendor.
The G-1000 reboots The supplied power to the G-1000 is too low. Check that the G-1000 is receiving enough
automatically power.
sometimes.
Make sure the power source is working properly.
Problems with the Ethernet Interface

Table 60 Troubleshooting the Ethernet Interface

PROBLEM CORRECTIVE ACTION
Cannot access the If the ETHN LED on the front panel is off, check the Ethernet cable connection
G-1000 from the between your G-1000 and the Ethernet device connected to the ETHERNET port.
LAN.
Check for faulty Ethernet cables.
Make sure your computer's Ethernet adapter is installed and working properly.
Check the IP address of the Ethernet device. Verify that the IP address and the subnet
mask of the G-1000, the Ethernet device and your computer are on the same subnet.
I cannot ping any If the ETHN LED on the front panel is off, check the Ethernet cable connections
computer on the between your G-1000 and the Ethernet device.
LAN.
Check the Ethernet cable connections between the Ethernet device and the LAN
computers.
Check for faulty Ethernet cables.
Make sure the LAN computer's Ethernet adapter is installed and working properly.
Verify that the IP address and the subnet mask of the G-1000, the Ethernet device and
the LAN computers are on the same subnet.
136
Appendix A

Troubleshooting

Troubleshooting