Facebook page not displaying correctly

[Nephtali]

Hello guys! Users on a regular IP based firewall policy with no UTM profiles applied to it, are having problems when trying to access Faceboo. On IE the page appears as text only and on Google Chrome, the pictures are blank. If there is no UTM feature applied to this rule, what can be the cause of this behaviour? Thanks in advanced guys!

[rwpatterson]

What' s the firmware version?

[Nephtali]

It is the latest version 4 MR3 patch 8. v4.0,build0632,120705 (MR3 Patch 8) Also I noticed that the traffic is https to website www-slb-12-03-frc1.facebook.com. Thanks for the reply!

[billp]

This is a bit of a wild guess, but have you tried temporarily changing DNS to something like 8.8.8.8 (Google)? The only time we' ve had oddball problems like you' ve described is when our DNS went wonky. And, I assume, everything works fine if you bypass the firewall?

[Nephtali]

Thanks for the suggestion. I will verify by changing the DNS. Also, what I have noticed so far is that the problem occurs with https sites. Thanks again!

[billp]

Good luck. Just some general hints. . . The Fortigate has many potential settings that can cause subtle issues if configured incorrectly on the command line. If you' ve done any tweaking to the config, you might peruse your config file to see if any old/odd settings are still hanging around.

[Nephtali]

One question Bill, in the DNS problem you mentioned, how did you solve the issue? Do you troubleshooted the DNS or it just went away?

[billp]

Well, we had a problem with our DNS provider. They eventually fixed it. But if you' ve isolated the problem to a particular service (DNS, for example), you' re a lot closer to solving the problem. It' s definitely a long shot here, but the general troubleshooting approach would be to start isolating possible causes. DNS would be simple to try. The next step would be to bypass the firewall completely to insure it' s a problem with the Fortigate.

[rwpatterson]

Another step might be to put a single host in a policy that bypasses everything, and then add UTM features until FB breaks.

[Nephtali]

When changing DNS to lets say google DNS, it worked fine. Then we switched back to the internal cleint DNS and it kept working fine, so definately it must be a DNS issue. Also, the client had an electrical outtasge and all servers went down and after that it was when the problem started when redirected to https web pages. Thanks again for the help!