Fortiguard Rating Error

Hi Dave, thanks for the reply! I think there is a pretty significant difference between an unrated website and an actual rating error. The problem I' m dealing with here pertains to actual rating errors occurring. I' m seeing this on all different kinds of sites but not on a consistent basis. I appreciate the feedback on how to block botnet connections but at this point I' m not really looking to take this conversation into that subject. I' m really just concerned with Fortiguard categories and how I can avoid getting rating errors in the future.

Yes I have plenty of lost packets showing on almost every IP in the list. I' m going to try setting the webfilter-sdns-server-port to 8888 and see if that helps at all.

Just curious to know if you are receiving packet lost on connections going out the WAN port? Can you perform a " diag hardware deviceinfo nic <interface name>" and check for any errors reported? (Possible duplex mismatch.)

We get this pretty consistently when the ISP of one of our locations blocks or degrades DNS queries off-network, and our Fortigate is set to use Fortinet' s DNS servers. In your Fortiguard settings, do you have your webfilter option set to regular 53, or port 8888? We have found switching it to 8888 stops all of our ' Rating Error Occurs' . EDIT: Sorry, just saw your last post attempting to switch to 8888. I' m curious to see if that solves it for you.

Dave: No errors on the interface. I assume that would degrade service to the point where we would have noticed it but you never know. ShrewLWD: Thanks for the edit - I have been using 8888 for a few days now. Here' s my output of " diag debug rating" for today: -=- Server List (Thu Sep 25 13:26:07 2014) -=- IP Weight RTT Flags TZ Packets Curr Lost Total Lost 69.195.205.101 10 44 -5 292603 0 922 66.117.56.42 10 78 -5 88467 0 328 64.26.151.36 10 93 -5 35453 0 104 64.26.151.37 10 93 -5 35320 0 103 209.222.147.43 10 57 -5 73235 0 276 209.222.147.36 10 130 -5 83185 0 232 64.26.151.35 10 91 -5 35765 0 101 66.117.56.37 10 57 -5 89184 0 307 69.195.205.102 10 45 -5 357885 0 6916 96.45.33.65 20 71 -8 38471 0 92 96.45.33.64 20 71 -8 36537 0 94 208.91.112.200 20 111 -8 35421 0 222 208.91.112.196 20 115 DI -8 36395 0 1079 208.91.112.198 20 114 D -8 36807 0 1574 80.85.69.40 60 148 0 35335 0 132 80.85.69.41 60 148 0 35333 0 130 80.85.69.37 60 148 0 35341 0 139 80.85.69.38 60 148 0 35357 0 156 62.209.40.72 70 163 1 35390 0 188 62.209.40.73 70 163 1 35424 0 224 62.209.40.74 70 164 1 35478 0 279 121.111.236.179 150 197 9 35463 0 276 121.111.236.180 150 195 9 35358 0 153 69.195.205.103 45 44 F -5 39178 38994 38995

Well a closer look at my logs showed that changing the port to 8888 for fortiguard lookups seems to have cleared up my issue afterall. Thanks for the suggestions everyone!

Rating error  may be caused by:

- An issue about the rating of the FortiGuard Web Filtering feature.
- The expiration of the Web Filtering license.

 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Web-Page-Blocked-An-error-occurred-while-trying-to/ta-p/191998