Comments
-
WSM 12.6.3 and the Fireware is not older than the 11.8 threshold. It is at 11.10
-
Still refuses to save, same error
-
Current is v12.1.3 but backup is only v11.10.5 - not compatible?
-
I tried pasting the key into the backup and it kinda took it but still refuses to save the config with the same error "Please update your feature key"
-
Will this not brick the current firewall?
-
I am not following this, Bruce. Delete "the" feature key and paste "the" feature key?
-
Never mind. User error.
-
1) Once again, no DHCP is involved here, just two computers with static IPs. 2) Of course, hence why I said I can access the firewall UI on the new IP and ping the external interface IP. 3) In IT this is frequently the first step in troubleshooting inexplicable problems so I did it multiple times. 4) I tried importing it…
-
I did not make any changes besides the IP of internal interface port 1. Those settings you mention are still there in the three private subnets 192.168.0.0/16 Any-External 172.16.0.0/12 Any-External 10.1.0.0/16 Any-External
-
Never mind on the notifications issue, I found another path to get in there
-
Bruce, I'm not even trying any name resolution yet. I'm only pinging IPs.
-
By the way, I'm not getting notified of replies to my posts so I tried to check in my profile which I can "view" but when I try to "edit" I get "Permission Problem - You don't have permission to do that"
-
1) I'm not on site right now so I can't check this until later today 2) Normally DHCP but for troubleshooting I'm using static IPs, manually defined. Took the device off the LAN so it's only two other devices besides the firebox. One computer on the internal and one on the external. 3) It's an existing network in that…
-
TcpDump taken and I do see a bunch of RST bits. But I will have to wait for support that can figure out what this means because I can't read packet captures so well.
-
I am able to connect locally from within the LAN. Coming from outside, the client log just says it can't connect by http. The failure is instant, almost as if I was using the wrong IP, but if I give it the wrong IP, the error number is 12007 while when the IP is correct, the error is 12029.
-
I seriously doubt an ISP issue. The same thing is being experienced on three different ISP, even different countries. USA and India.
-
In that case the external IP is not being denied because it doesn't show at all. I see a bunch of other Deny packets but not the one I'm testing from. Not very useful bit of information, is it?
-
At first I thought it just wasn't showing the VPN connection with the external IP. But now I see it's not showing ANY traffic from the external IP, even though I am refreshing OWA and using TeamViewer to connect to an internal workstation where I can actually view the log. My IP is invisible. Am I missing some obvious…
-
Reboot did not help. Turned on Informational logging for VPNSSL. Where do I actually view the log?