General transport failure.^M socket timeout error)

Usage and Config Platform
1

Hi All,

We have the some error message on our client machine… Both Bigfix
server and client are connected via VPN tunnel. Connectivity from Client
to Bigfix is confirmed via telnet . When we start besclient it is
syncing with the Big fix server but later getting below mentioned socket
time out error.
Bigfix server is installed on Windows server and the client ( intended to be future relay server) is SLES11SP4

besclient log

Successful Synchronization with site ‘actionsite’ (version 226) - 'http://10.64.193.182:52311/cgi-bin/bfgather.exe/actionsite’
Site ‘mailboxsite’ is not yet available on selected relay. Awaiting notification of availability.

Successful Synchronization with site ‘mailboxsite’ (version 0) -
'http://10.64.193.182:52311/cgi-bin/bfgather.exe/mailboxsite10980880’
At 19:12:55 +1030 -
SetupListener success: IPV4
Encryption: optional encryption with no certificate; reports in cleartext
At 19:14:25 +1030 -
Error posting report to: ‘http://10.64.193.182:52311/cgi-bin/bfenterprise/PostResults.exe’ (General transport failure.
socket timeout error)

However when I open the log file in Vi mode I see an ^M character after the url as shown below.

Entering service loop
Successful Synchronization with site
’actionsite’ (version 226) -
'http://10.64.193.182:52311/cgi-bin/bfgather.exe/actionsite’
Site ‘mailboxsite’ is not yet available on selected relay. Awaiting notification of availability.

Successful Synchronization with site ‘mailboxsite’ (version 0) -
'http://10.64.193.182:52311/cgi-bin/bfgather.exe/mailboxsite10980880’
At 19:12:55 +1030 -
SetupListener success: IPV4
Encryption: optional encryption with no certificate; reports in cleartext
At 19:14:25 +1030 -
Error posting report to: ‘http://10.64.193.182:52311/cgi-bin/bfenterprise/PostResults.exe’ (General transport failure.^M
socket timeout error)

We have run the dos2unix command on both actionsite and besclient.config files to ensure the files are unix compatable.

Due to this error Client is not reporting to the master server.

What can be the possible reason ? Any suggestions to fix this is highly appreciated.

  1. Telent from Client to relay server ( port 52311 works.
2

Check by making host entry of Relay on client machine. Also is it working post client re-installation.

3

Hi Ashutosh,
We use ips in actionsite.afxm and besclient config. I will try that tool
We have re installed the client multiple time still no luck…

4

Hi All ,

I could resolve this issue… The relay server has 2 interfaces, application ip and management ip. the default gateways was set with application IP vlan. I changed the default gateway to management VLAN gateway… and it started working.

5

Hi @Joyland10 For my infra we are using local IP and Public IP for relay machines, also on client config file we used public IP for communicating to Relay/Server,
so what we have to change/check from here, (we are getting the same issue for Linux endpoints )

Could you please give your input ,

Thanks,
Nagaraj,

6

Hi Nagaraj,

I assume that your Relay server is in remote location , that is the reason you are using Public IP in the config file of the nodes. If that is the case, have you added a manual route on the clients with the gateway that should be used to reach the relay.

If this does not help… Please give a brief idea about the infrastrcture setup.