FortiManager having error logs saying cannot receive response from FDS server

[#1]

Hi I guess prob lies here: 4 2007-09-03 10:09:01 debug n/a FWMANAGER (1260): FR_http_recv_response_header: line = Anyone have any idea how to resolve this? Or wat causes this?

[doshbass]

Check obvious things like internet connectivity and DNS resolution. a simple " exec ping google.com" from teh CLI should answer those questions

[#3]

Hi doshbass FYI, my web proxy is blocking ping to external sites. Therefore, I will not be able to ping to anywhere not within my LAN. However, I had configured the web proxy at the FDN settings and is able to sychronised the AV/IS connection status. Any ideas?

[rwpatterson]

You should be able to ping the Internet directly from the Fortigate. If you can' t, there' s a clue for you. If the proxy server is outside the Fortigate, make an exception in it for the Fortigate to pass through.

[#5]

Hi Thanks for the advice. However, due to security reasons, I am not able to bypass the proxy for the FortiManager. Any more ideas? Becos, I know that most companies do have web proxy and it should not be a prob for the updates to occur via the proxy

[doshbass]

Has your proxy been configured to allow teh IP address of teh FortiManager out, or are you attempting to use user name and password to authenticate to teh proxy. The last time I tried to use authentication, it would not work because teh Fortigate only supports basic (clear text) authenticationj and the proxy required something more elaborate.

[#7]

Hi Doshbass Yes, the proxy had been configure for the FortiManager IP to go outside.... And I input the username and password at the fields and is able to receive signal from FortiGuard. Thats why the connection status can be synchronised. But why the error logs appear, thats a big question mark.

[doshbass]

AFAIK AV and IPS updates should work. If however you are trying to do URL filtering then this needs to be initialized. Could this be the issue?

[#9]

Yo friend Thanks for being so helpful. ANYWAY the logs are as below: 2007-08-30 17:58:03 error n/a FWMANAGER (1260): DES=LOGTP_COMM:linkdlib_send_and_recv: Failed to recv response from fds server 2007-08-30 17:58:03 error n/a FWMANAGER (1260): DES=LOGTP_COMM:FCP_recv_response: Failed to receive response header 2007-08-30 17:58:03 error n/a FWMANAGER (1260): DES=LOGTP_COMM:FR_http_recv_response_header: Missing Content-Length in head. If you have any ideas whats gg on, keep me posted. Thanks,

[#10]

Hi I guess prob lies here: 4 2007-09-03 10:09:01 debug n/a FWMANAGER (1260): FR_http_recv_response_header: line = Anyone have any idea how to resolve this? Or wat causes this?