About atkinsonr

I actually have the exact same problem (using 3.1.6), however what I found is that ping does work to a regular Layer 3 interface, it does not work on any of my  logical interfaces (sub-interface). I do have an interface management profile for 'ping only' applied to all regular and logical Layer 3 interfaces. ... View more

It still does not work for me with 3.1.2. Our DNS is fine and the IP addresses are correct for service.brightcloud.com, database.brightcloud.com and www.brightcloud.com. I have also tried to use both an L3 interface and management with the same results. The traffic is making it out to the Internet fine, however this is an example of what the PAN device logs. Jun 24 08:01:08  ip 64.87.3.54 message RT time 0.075 Jun 24 08:01:08  ip 94.236.25.159 message RT time 0.108 Jun 24 08:01:08 Best IP for service.brightcloud.com is 64.87.3.54 Jun 24 08:01:23 Cannot receive data from  'service.brightcloud.com:80' to download BrightCloud URL database Jun 24 08:01:23 Error downloading latest URL database Sometimes it uses the 64 address, other times the 94 one, however the same error occurs for either. The devices have been rebooted several times too, plus I flipped them (running HA) and both have the same issue. I do not know how the PAN device does it's check for the best IP, however I did a test last week and specifically blocked the IP that was favored (was the 64 address), and even though it did not get a response from and did from the other, the PAN device still said the Best IP was the one that it could not reach. I have since put everything back to normal again and it still fails downloading the URL database. Ron ... View more

Has there been a solution for this yet? I still have the same problem with 3.1.2. Ron ... View more