Page 176 / 240 Scroll up to view Page 171 - 175
ProSafe VPN Firewall 200 FVX538 Reference Manual
7-2
Troubleshooting
v1.0, March 2009
Check that you are using the 12 V DC power adapter supplied by NETGEAR for this product.
If the error persists, you have a hardware problem and should contact technical support.
LEDs Never Turn Off
When the firewall is turned on, the LEDs turns on for about 10 seconds and then turn off. If all the
LEDs stay on, there is a fault within the firewall.
If all LEDs are still on one minute after power up:
Cycle the power to see if the firewall recovers.
Clear the firewall’s configuration to factory defaults. This will set the firewall’s IP address to
192.168.1.1. This procedure is explained in
“Restoring the Default Configuration and
Password” on page 7-7
.
If the error persists, you might have a hardware problem and should contact technical support.
LAN or Internet Port LEDs Not On
If either the LAN LEDs or Internet LED do not light when the Ethernet connection is made, check
the following:
Make sure that the Ethernet cable connections are secure at the firewall and at the hub or
workstation.
Make sure that power is turned on to the connected hub or workstation.
Be sure you are using the correct cable:
When connecting the firewall’s Internet port to a cable or DSL modem, use the cable that was
supplied with the cable or DSL modem. This cable could be a standard straight-through
Ethernet cable or an Ethernet crossover cable.
Troubleshooting the Web Configuration Interface
If you are unable to access the firewall’s Web Configuration interface from a PC on your local
network, check the following:
Check the Ethernet connection between the PC and the firewall as described in the previous
section.
Page 177 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
Troubleshooting
7-3
v1.0, March 2009
Make sure your PC’s IP address is on the same subnet as the firewall. If you are using the
recommended addressing scheme, your PC’s address should be in the range of 192.168.0.2 to
192.168.0.254.
If your firewall’s IP address has been changed and you don’t know the current IP address,
clear the firewall’s configuration to factory defaults. This will set the firewall’s IP address to
192.168.1.1. This procedure is explained in
“Restoring the Default Configuration and
Password” on page 7-7
.
Make sure your browser has Java, JavaScript, or ActiveX enabled. If you are using Internet
Explorer, click Refresh to be sure the Java applet is loaded.
Try quitting the browser and launching it again.
Make sure you are using the correct login information. The factory default login name is
admin
and the password is
password
. Make sure that CAPS LOCK is off when entering this
information.
If the firewall does not save changes you have made in the Web Configuration Interface, check the
following:
When entering configuration settings, be sure to click the APPLY button before moving to
another menu or tab, or your changes are lost.
Click the Refresh or Reload button in the Web browser. The changes may have occurred, but
the Web browser may be caching the old configuration.
Note:
If your PC’s IP address is shown as 169.254.x.x: Recent versions of Windows
and MacOS will generate and assign an IP address if the computer cannot
reach a DHCP server. These auto-generated addresses are in the range of
169.254.x.x. If your IP address is in this range, check the connection from the
PC to the firewall and reboot your PC.
Tip:
If you don’t want to revert to the factory default settings and lose your
configuration settings, you can reboot the router and use sniffer to capture
packets sent during the reboot. Look at the ARP packets to locate the router’s
LAN interface address.
Page 178 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
7-4
Troubleshooting
v1.0, March 2009
Troubleshooting the ISP Connection
If your firewall is unable to access the Internet, you should first determine whether the firewall is
able to obtain a WAN IP address from the ISP. Unless you have been assigned a static IP address,
your firewall must request an IP address from the ISP. You can determine whether the request was
successful using the Web Configuration Manager.
To check the WAN IP address:
1.
Launch your browser and select an external site such as www.netgear.com
2.
Access the Main Menu of the firewall’s configuration at http://192.168.1.1
3.
Under the Monitoring menu, select Router Status
4.
Check that an IP address is shown for the WAN Port
If 0.0.0.0 is shown, your firewall has not obtained an IP address from your ISP.
If your firewall is unable to obtain an IP address from the ISP, you may need to force your cable or
DSL modem to recognize your new firewall by performing the following procedure:
1.
Turn off power to the cable or DSL modem.
2.
Turn off power to your firewall.
3.
Wait five minutes and reapply power to the cable or DSL modem.
4.
When the modem’s LEDs indicate that it has reacquired sync with the ISP, reapply power to
your firewall.
If your firewall is still unable to obtain an IP address from the ISP, the problem may be one of the
following:
Your ISP may require a login program.
Ask your ISP whether they require PPP over Ethernet (PPPoE) or some other type of login.
If your ISP requires a login, you may have incorrectly set the login name and password.
Your ISP may check for your PC's host name.
Assign the PC Host Name of your ISP account as the Account Name in the Basic Settings
menu.
Your ISP only allows one Ethernet MAC address to connect to the Internet, and may check for
your PC’s MAC address. In this case:
Inform your ISP that you have bought a new network device, and ask them to use the
firewall’s MAC address; or
Page 179 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
Troubleshooting
7-5
v1.0, March 2009
Configure your firewall to spoof your PC’s MAC address. This can be done in the Basic
Settings menu. Refer to
“Manually Configuring Your Internet Connection” on page 2-4
.
If your firewall can obtain an IP address, but your PC is unable to load any Web pages from the
Internet:
Your PC may not recognize any DNS server addresses.
A DNS server is a host on the Internet that translates Internet names (such as www addresses)
to numeric IP addresses. Typically your ISP will provide the addresses of one or two DNS
servers for your use. You may configure your PC manually with DNS addresses, as explained
in your operating system documentation
.
Your PC may not have the firewall configured as its TCP/IP gateway.
Troubleshooting a TCP/IP Network Using a Ping Utility
Most TCP/IP terminal devices and firewalls contain a ping utility that sends an echo request packet
to the designated device. The device then responds with an echo reply. Troubleshooting a TCP/IP
network is made very easy by using the Ping utility in your PC or workstation.
Testing the LAN Path to Your Firewall
You can ping the firewall from your PC to verify that the LAN path to your firewall is set up
correctly.
To ping the firewall from a PC running Windows 95 or later:
1.
From the Windows toolbar, click
Start
and select
Run
.
2.
In the field provided, type “ping” followed by the IP address of the firewall; for example:
3.
Click
OK.
A message, similar to the following, should display:
Pinging <
IP address
> with 32 bytes of data
If the path is working, you will see this message:
Reply from <
IP address
>: bytes=32 time=NN ms TTL=xxx
If the path is not working, you will see this message:
Request timed out
If the path is not functioning correctly, you could have one of the following problems:
Page 180 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
7-6
Troubleshooting
v1.0, March 2009
Wrong physical connections
Make sure the LAN port LED is on. If the LED is off, follow the instructions in
“LAN
or Internet Port LEDs Not On” on page 7-2
.
Check that the corresponding Link LEDs are on for your network interface card and
for the hub ports (if any) that are connected to your workstation and firewall.
Wrong network configuration
Verify that the Ethernet card driver software and TCP/IP software are both installed
and configured on your PC or workstation.
Verify that the IP address for your firewall and your workstation are correct and that
the addresses are on the same subnet.
Testing the Path from Your PC to a Remote Device
After verifying that the LAN path works correctly, test the path from your PC to a remote device.
From the Windows run menu, type:
PING -n 10
<
IP address
>
where <
IP address
> is the IP address of a remote device such as your ISP’s DNS server.
If the path is functioning correctly, replies as in the previous section are displayed. If you do not
receive replies:
Check that your PC has the IP address of your firewall listed as the default gateway. If the
IP configuration of your PC is assigned by DHCP, this information will not be visible in
your PC’s Network Control Panel.
Check to see that the network address of your PC (the portion of the IP address specified
by the netmask) is different from the network address of the remote device.
Check that your cable or DSL modem is connected and functioning.
If your ISP assigned a host name to your PC, enter that host name as the Account Name in
the Basic Settings menu.
Your ISP could be rejecting the Ethernet MAC addresses of all but one of your PCs. Many
broadband ISPs restrict access by only allowing traffic from the MAC address of your
broadband modem, but some ISPs additionally restrict access to the MAC address of a
single PC connected to that modem. If this is the case, you must configure your firewall to
“clone” or “spoof” the MAC address from the authorized PC. Refer to
“Manually
Configuring Your Internet Connection” on page 2-4
.

Rate

4 / 5 based on 1 vote.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top