Comments
-
Sorry about the delay. I believe re-doing the Feature Key and checking the DNS Forwarding checkbox is what fixed the problem. Thank you Kevin
-
Thanks. With all your help I got it to work. Best forum I've ever been in. Seriously. Kevin
-
Did that again just now: "The changes were saved successfully" I didn't mean to indicate that the System - Feature Key only had those 2 items...below that is a list of 19 items...ie: Model Upgrade / Total Number of Authenticated Users / Branch Office VPN Tunnels / Fireware XTM / Firewall Policy Maximum ....etc. One other…
-
Under System - Feature Key I have a Serial Number Signature So that would indicate that I imported the Feature Key. Correct ? Thanks Kevin
-
Under Dashboard - Subscription Services ...it only list File Exceptions. Should it be that way? Thanks Kevin
-
Bruce, I have a blinking amber light on the front on the firebox on ETH0 and ETH1 at the 1GB level / Mode = Solid Green / Status = No light / Attn: = No light
-
Bruce, I misspoke ....the firewall is handling DHCP and am using Comcast DNS for DNS: This is the workstation ipconfig: IPv4 Address. . . . . . . . . . . : 10.0.1.20(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, December 12, 2021 11:23:24 AM Lease Expires . . . . .…
-
Case has been opened. Not sure why I would need to forward DNS and would that be related to why only one pc (hardwired into the Firebox) can get on the Internet? When I uplink an ISP cable modem port to ETH0 and then uplink ETH1 to the internal switch, no pc's can get on the Internet. Thanks for the input. Kevin
-
More details: ISP Modem Router IP = 10.1.10.1 Watchguard Firebox IP = 10.0.1.1 (default) Firebox will be handling DHCP & DNS Internal network will be pulling IP from the Firebox / previously it was using the ISP Modem - Router Trusted IP = 10.0.1.1 External IP = DHCP from the ISP When I was testing it, I took the patch…