General transport failure

(imported topic written by jclark91)

Can anybody explain what is happening on this endpoint. It repeadtedly gets a “winsock error -21”.

I have searched diligently for a description of the winsock -21 error, but cannot find it anywhere.

Here is section of the BES log from the failing endpoint:

At 11:25:14 -0400 -

RegisterOnce: GetURL failed

At 11:25:27 -0400 - actionsite (http://bigfix.someserver.com:52311/cgi-bin/bfgather.exe/actionsite)

Relevant - Assign and Revoke Management Rights For fccavservice (fixlet:423)

At 11:25:37 -0400 -

ActionLogMessage: (action 423 ) starting action

At 11:25:37 -0400 - actionsite (http://bigfix.someserver.com:52311/cgi-bin/bfgather.exe/actionsite)

Command succeeded setting “__Group___AdminBy_fccavservice”=“True” on “13 Feb 2006 19:11:06 gmt” for client (fixlet 423)

Command succeeded administrator delete “fccavservice” on “13 Feb 2006 19:11:06 gmt” (fixlet 423)

Command succeeded (evaluated true) continue if { exists true whose (exists (if (exists key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client\AV_Service” of registry) then (value of setting “AV_Service” of client) as string else (“No”)) whose (it as string is “Yes”)) } (fixlet 423)

At 11:25:37 -0400 -

Adding operator site (fccavservice)

At 11:25:37 -0400 - actionsite (http://bigfix.someserver.com:52311/cgi-bin/bfgather.exe/actionsite)

Command succeeded administrator add “fccavservice” on “13 Feb 2006 19:11:06 gmt” (fixlet 423)

Not Relevant - Assign and Revoke Management Rights For fccavservice (fixlet:423)

At 11:26:08 -0400 - opsite16 (http://bigfix.someserver.com:52311/cgi-bin/bfgather.exe/opsite16)

FAILED to Synchronize - General transport failure. - winsock error -21

At 11:26:10 -0400 -

RegisterOnce: Attempting to register with ‘http://bigfix.someserver.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=6.0.15.7&Body=1190816573&SequenceNumber=40&MinRelayVersion=6.0.0.0

At 11:26:31 -0400 -

RegisterOnce: GetURL failed

(imported comment written by BenKus)

Hey jclark,

Winsock errors are listed here: http://support.bigfix.com/cgi-bin/kbdirect.pl?id=273

But you are correct that we don’t list -21, which is a “proxy connect” error that indicates that the agent can’t connect to the proxy… This should only be an error if you are using the proxy connection code in the BES Client (which is pretty rare for most people, but I know you guys are one of the few people that use the client through proxies).

Here are some other winsock codes that we don’t expect anyone will hit:

#define err_PROXY_CONNECT -21

#define err_THREAD_STARTUP -22

#define err_THREAD_EXCEPTION -23

#define err_THREAD_STARTUP2 -24

#define err_THREAD_STARTUP3 -25

Ben