
Prestige 652H/HW
6 Troubleshooting
| Table 12 Troubleshooting |
|
|
PROBLEM | CORRECTIVE ACTION |
|
|
None of the LEDs turn | Make sure that you have the correct power adapter connected to the Prestige and |
on when you turn on | plugged in to an appropriate power source. Check all cable connections. |
the Prestige. | If the LEDs still do not turn on, you may have a hardware problem. In this case, you |
| |
| should contact your local vendor. |
|
|
Cannot access the | Check the cable connection between the Prestige and your computer or hub. Refer to |
Prestige from the LAN. | the Rear Panel Connections section for details. |
| Ping the Prestige from a LAN computer. Make sure your computer Ethernet adapter is |
| installed and functioning properly. |
|
|
Cannot ping any | If the LAN LEDs are all off, check the cable connections between the Prestige and your |
computer on the LAN. | LAN computers. |
| Verify that the IP address, subnet mask of the Prestige and the LAN computers are in |
| the same IP address range. |
|
|
Cannot ping any | Make sure the wireless card is properly inserted in the Prestige and the WLAN LED is |
computer on the | on. |
WLAN | Make sure the wireless card on the wireless client is working properly. |
| |
| Check that both the Prestige and wireless client(s) are using the same ESSID, channel |
| and WEP keys (if WEP encryption is activated). |
|
|
Cannot get a WAN IP | Check your Encapsulation, Multiplex and VPI/VCI settings (refer to section 4.3). |
address from the ISP. | You need a user name and password if you’re using PPPoE or PPPoA encapsulation. |
| |
| Make sure that you have entered the correct Service Name (PPPoE encapsulation |
| only), User Name and Password (the username and password are case sensitive). |
| Refer to section 4.3 for more information. |
|
|
Cannot access the | Verify the Internet connection settings in the WAN screen. |
Internet. | Make sure you entered the correct user name and password. |
| |
| For wireless clients, check that both the Prestige and wireless client(s) are using the |
| same ESSID, channel and WEP keys (if WEP encryption is activated). |
|
|
35