Central Quarantine - Unable to connect to the Gateway
Updated: 06 Nov 2010 | 1 comment
I am receiving this message in the Application log every day on My SEPM server. I xxxed out some information due to my inherent paranoia. This machine connects to Liveupdate fine and does not use a proxy to connect to the Internet. Server is running Windows 2003 SP2, new SEP install.
Event Type: Error
Event Source: Central Quarantine
Event Category: None
Event ID: 34054
Date: 11/13/2007
Time: 6:24:57 PM
User: N/A
Computer: SVR-SEPTEST
Description:
A general error was detected with Central Quarantine.
[Error Connecting to Gateway - Unable to connect to the Gateway]
Quarantine Server: SVR-SEPTEST
Address: 10.x.x.x DNS name: svr-septest.xxx.local
Event Source: Central Quarantine
Event Category: None
Event ID: 34054
Date: 11/13/2007
Time: 6:24:57 PM
User: N/A
Computer: SVR-SEPTEST
Description:
A general error was detected with Central Quarantine.
[Error Connecting to Gateway - Unable to connect to the Gateway]
Quarantine Server: SVR-SEPTEST
Address: 10.x.x.x DNS name: svr-septest.xxx.local
download: QServer cannot connect to the gateway to download definitions.
Ensure QServer has access to an adequate Internet connection
Ensure QServer has access to an adequate Internet connection
Thnaks,
Ned
discussion Filed Under:
Comments
Central Quarantine - Unable to connect to the Gateway
Hi,
Please check out this article. http://service1.symantec.com/support/ent-security..... It appears this is all working as designed and this message gets logged when the server is busy and has to wait before it becomes available again.
Also, in the Q-server properties, uncheck the secure connections check boxes with IE7 or IE8, there seems to be an issue.
Go to the Central Quarantine console, right click the q-server, choose properties.
Under Web communication tab, uncheck both boxes under the security section, save, and try again.
This looks to be helping in getting over the issue.
Regards,
Ketan Karnick
Would you like to reply?
Login or Register to post your comment.