Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FB700 Configuration Problems

Status
Not open for further replies.

kngmfgco

IS-IT--Management
Mar 9, 2003
2
US
Hello,

I am "NEW" to the to whole firewall thing so my questions may be simple to answer but this FB700 is sure driving me nuts!!

I recently purchased a FB700, the cable was installed and cable router delivered today. All ready (and excited) to do the "Quick Start Wizard" and deploy the FB700 in my network. I tried 6-7 times and couldn't EVEN ping the D*MN thing.

I'll provide some current and proposed network info and then ask my questions;

Current network:

3Com Dual Lan Modem (for 56K dial-up Access) IP - 10.0.0.253, 255.255.0.0

Plugged into a 3Com 10/100 24 Port Hub

3Com NBX100 Phone System - 10.0.0.254, 255.255.0.0

NT Server (used only as an RTDC Application Server)- IP -10.0.0.1, 255.255.0.0

Netware 4.11 - TCP/IP not running NW server

Workstations - NT, XP, W98, W95 - IP 10.0.0.2-33, 255.255.0.0, Currently have all workstation configured with static IP addresses and the workstation with internet access a default gateway set at 10.0.0.253 (Lan Modem)

Everthing is working fine but the acess to the internet is SLOW!!!


NEW Network - HOPEFULLY!!

Cable Router - Connected to Firebox

ISP Info:

IP Space: 24.159.195.202
Subnet Mask: 255.255.255.252
Gateway address: 24.159.195.201
Primary DNS: 24.159.193.40
Secondary DNS: 24.159.222.40
Domain: roc.mn.charter.com

Firebox 700 - Connected to Hub

NT Server - NO Changes?

Netware 4.11 server - No Changes

Workstations - NT, XP, W98, W95 - IP 10.0.0.2-33, 255.255.0.0 - What needs to change??


FINALLY, The Questions....

1) What should the TCP/IP settings be on the laptop I am using to configure the Firebox 700?

I have been able to get the configuration files to load but after they load testing the connection by pinging fails. I have reset the firebox (a lot) and have been able to ping it using the factory IP address of 192.168.253.1, 255.255.225.0.

2) Should I use the "routed" or "drop-in" configuration?

3) Can I set the trusted interface "masque" to be 10.0.0.252, 255.255.0.0 and how?

4) If #3 is Yes, what do the settings on the workstations need to be to allow access to the internet via the Firebox and Cable router?

I know these may seem like STUPID questions but "there is no such thing as a stupid question and the documentation and help from Watchguard SUCKS!! I called two days ago just to find out more about their installation service and still have not heard back.

Any help would be greatly appreciated...

kngmfgco
 
1) If you have loaded the configuration, what type of setup did you give it? Routed/Drop-in. This may have something to do with why you are not able to ping it. An example of the configuration you are trying to implement would be useful here.

2) In short, Routed configuration is used primarily when the number of public IP addresses is limited or when you have dynamic IP addressing on the External interface. Otherwise Drop-in will work for you. Just remember to use that secondary network on the trusted interface if you create a config. in Drop-in.

3) You sure can: 10.0.0.252/16

4) Set the default gateway of the workstations to 10.0.0.252
 
NtrOP,

You are correct sir!! I did get it setup and working. Do you work for Watchguard?? If not you should. Tou undoubtedly have an excellent working knowledge of their Firebox products and are extremelly more responsive!!!

THANK YOU!!!

I determined that my biggest problem was I had swithed around the IP Space and Default gateway addresses.

Thanks Again!!

kngmfgco
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top