Hi - We have a server that acts as the BES Relay for small fleet of internal servers. It also has the BES Client installed (not working). Now, the BES Relay function is working fine and the fleet of servers using it as the relay are fine (reporting into BES Console OK). The problem I am writing about is the BES Client installed as all of sudden (after it was patched on Jan 28th) it stopped checking into the BigFix console.
Looking at the C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Logs directory log files I see a bunch of the following:
(In no specific order)
Setting _BESClient_Download_FastHashVerify enabled: Off
Beginning Relay Select
GetRelayInfo: checking 'http://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=Version’
GetRelayInfo: Valid Relay
RegisterOnce: Attempting secure registration with 'https://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=4837279&SequenceNumber=2591&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=4&MaxHops=4&
GatherHashMV command ignored while registering.
GatherHash command ignored while registering.
RegisterOnce: Attempting secure registration with 'https://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=4837279&SequenceNumber=2592&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=4&MaxHops=4&
RegisterOnce: GetURL failed - General transport failure.
These are obviously truncated as they also contain internal info that I have chopped out for privacy reasons.
I have reviewed the registry keys for the configured client/relay settings and they all work fine. I can successfully telnet to the Bigfix servers via port 52311 from this machine too. From my knowledge and experience, this usually means that the relay is on the server is misconfiged or there’s a Firewall problem but I can’t anything with either and hasn’t been changed for a number of years.
Any ideas?