Troubleshooting
369
ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N

LAN or WAN Port LEDs Not On

If either the LAN LEDs or WAN LEDs do not light when the Ethernet connection is
made, check the following:
•Make sure that the Ethernet cable connections are secure at the wireless VPN firewall
and at the hub, router, or workstation.
•Make sure that power is turned on to the connected hub, router, or workstation.
•Be sure that you are using the correct cables:
When connecting the wireless VPN firewall’s WAN ports to one or two devices that
provide the Internet connections, use the cables that are supplied with the devices.
These cables could be standard straight-through Ethernet cables or Ethernet crossover
cables.
Troubleshoot the Web Management Interface
If you cannot access the wireless VPN firewall’s web management interface from a
computer on your local network, check the following:
•Check the Ethernet connection between the computer and the wireless VPN firewall as
described in the previous section (LAN or WAN Port LEDs Not On).
•If your computer’s IP address is shown as 169.254.x.x:
Windows and Mac operating systems generate and assign an IP address if the computer
cannot reach a DHCP server. These autogenerated addresses are in the range of
169.254.x.x. If your IP address is in this range, check the connection from the computer
to the wireless VPN firewall and reboot your computer.
•If your wireless VPN firewall’s IP address has been changed and you do not know the
current IP address, reset the wireless VPN firewall’s configuration to factory default
settings. This sets the wireless VPN firewall’s IP address to 192.168.1.1. This procedure
is explained in Restore the Default Configuration and Password on page 376.
Tip: If you do not want to revert to the factory default settings and lose your
configuration settings, you can reboot the wireless VPN firewall and use
a sniffer to capture packets sent during the reboot. Look at the ARP
packets to locate the wireless VPN firewall’s LAN interface address.
•Make sure that you are using the SSL https://address login rather than the http://address
login.
•Make sure that your browser has Java, JavaScript, or ActiveX enabled. If you are using
Internet Explorer, click Refresh to be sure that the Java applet is loaded.
•Try quitting the browser and launching it again.
•Clear the browser’s cache.