Manualshelf

User guide

ManualsBrandsZoneAlarm ManualsComputer equipmentZ100G
401402403404405406407408409410
Connectivity
390 Check Point ZoneAlarm User Guide
• Check if you have defined firewall rules which block your Internet connectivity.
• Check with your ISP for possible service outage.
• Check whether you are exceeding the maximum number of computers allowed
by your license, by viewing the My Computers page.
I cannot access my DSL broadband connection. What should I do?
DSL equipment comes in two flavors: bridges (commonly known as DSL modems) and
routers. Some DSL equipment can be configured to work both ways.
• If you connect to your ISP using a PPPoE or PPTP dialer defined in your
operating system, your equipment is most likely configured as a DSL bridge.
Configure a PPPoE or PPTP type DSL connection.
• If you were not instructed to configure a dialer in your operating system, your
equipment is most likely configured as a DSL router. Configure a LAN
connection, even if you are using a DSL connection.
For instructions, see Configuring the Internet Connection on page
55.
I cannot access my Cable broadband connection. What should I do?
• Some cable ISPs require you to register the MAC address of the device behind
the cable modem. You may need to clone your Ethernet adapter MAC address
onto the ZoneAlarm router. For instructions, see Configuring the Internet
Connection on page
55.
• Some cable ISPs require using a hostname for the connection. Try reconfiguring
your Internet connection and specifying a hostname. For further information, see
Configuring the Internet Connection on page
55.
I cannot access http://my.firewall. What should I do?
• Verify that the ZoneAlarm router is operating.
• Check if the LED for the LAN port used by your computer is green. If not,
check if the network cable linking your computer to the ZoneAlarm router is
connected properly.
• By default, unencrypted HTTP access is not allowed from the wireless LAN to
http://my.firewall. Therefore, if you are connecting from the wireless LAN, try
connecting to https://my.firewall instead.
• Try surfing to 192.168.10.1 instead of to my.firewall.