ePO agent can't connect to server after deployment

[Former Member]

I just installed FramePkg.exe on 13 PCs. 12 of it working fine. But 13s dont want to connect to server. It has the following messages in McAfee Agent Activity Log:

26 июня 2008 г. 10:32:24 Error Internet Manager Failed to connect to server vlgserver.realrussialimited.local. Check the agent log for more details.
 26 июня 2008 г. 10:32:24 Error Agent Agent failed to communicate with ePO Server

In the Agent log:

20080626092112 I #2368 InetMgr Failed connecting to site = ePO_VLGSERVER,
20080626092112 I #2368 InetMgr No failover site available.
20080626092112 I #2368 InetMgr Connecting to site = ePO_VLGSERVER,
20080626092112 I #2368 InetMgr Connecting to ePO Server using DNS name: vlgserver.realrussialimited.local
20080626092112 I #2368 InetMgr HTTP Session initialized
20080626092112 I #2368 InetMgr Connecting to HTTP Server in socket-mode
20080626092112 I #2368 InetMgr Connecting to Real Server: vlgserver.realrussialimited.local on port: 8880
20080626092112 I #2368 InetMgr Connected to Real Server: vlgserver.realrussialimited.local on port: 8880. No Proxy used!
20080626092112 I #2368 InetMgr Uploading package to ePO Server...trial 1 / 6
20080626092112 I #2368 InetMgr Uploading file C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Unpack\pkg00128589420726710000_32580.spkg to ePO Server...
20080626092112 I #2368 InetMgr Connecting to Real Server: vlgserver.realrussialimited.local on port: 8880
20080626092112 I #2368 InetMgr Connected to ePO Server: vlgserver.realrussialimited.local
20080626092112 I #2368 InetMgr Uploading SPIPE HTTP header
20080626092112 I #2368 InetMgr Uploading data in bytes: 718
20080626092112 I #2368 InetMgr Reading acknowledgement from ePO Server
20080626092112 I #2368 InetMgr Could not recognize the HTTP return code: HTTP/1.1 400 Bad Request

And its constantly appearing in log.

I reinstalled epo agent many times but the result is the same.
This PC has Windows XP Media Center with all Latest updates.

Any Ideas what to do?

[Former Member]

Any ideas? I tried everything exept reinstalling windows.

[tonyb99]

no idea..

but that http code indicates bad packets or not expected data, is there a firewall or other security software in the way?

[Former Member]

Can you see the mcafee agent activity log from http://localhost:8081?

Can you see the mcafee agent activity log from the epo server http://PC13***:8081?

Atleast you'll know if the agent is working correctly and then can look at firewalls etc

Have you forced an uninstall rather than install it over the top?

[Former Member]

Yes it was completly uninstalled and only than installed again. There is windows MCE 2005 from Packard Bell with some stupid patches and also there was Norton 2003 Security stuff. Norton was uninstalled by official Norton Uninstaller.

[tonyb99]

can you successfully resolve the dns name vlgserver.realrussialimited.local from that pc?

[Former Member]

Yes its resolves dns name.

[tonyb99]

is there anything else using the ports it should be talking on?
(check it with netstat)
Im not sure if there are any diff with media centre version of XP as its not something I would ever come across.

[Former Member]

There no connection between communicating ports and this error, cause software on server works fine, and communication port on client is allocating randomly. I have compared network packet dumps (created with Microsoft sniffer), and there no difference in POST messages between normal machine and broken. But on normal machine it sends POST and then sequence of binary data. On broken one it sends POST, one binary packet and then SERVER refuses connection with 403 error.

[Former Member]

And one more strange thing - both normal and broken PCs on wakeup notice says Source=Agent_3.0.0, but there 3.6.0 Agent.