GetURL failed - General transport failure. - winsock error -6

(imported topic written by snoczp91)

I have had a number of clients get this error in the BF logs when they are not able to connect/synch to our BES server. The individual systems end up not listed in BigFix.

Reinstalling the agent does not resolve the issue. We are running v 8.0.584 currently.

Any ideas what causes it, or a resolution? It occurs on machines on our LAN, WAN connected, and remote systems.

Thanks,

(imported comment written by snoczp91)

No ideas? No response?

Note we are not running IPv6 anywhere.

Thanks,

(imported comment written by NoahSalzman)

When it happens, do this:

  1. Pull up a browser on the box in question

  2. Grab the URL out of the BigFix client log – the one listed next to the GetURL failed error

  3. Try the URL out in the browser

Odds are that the machine does not have basic connectivity back to the BigFix server. Common reasons are proxies, client firewalls, and network devices in between the client and server interfering with HTTP or blocking port 52311.

Also, if you can, please update to the latest 8.1 release… just 'cause. :slight_smile:

(imported comment written by snoczp91)

URL:

http://shqbfrly03.na.sas.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=8.0.584.0&Body=5581252&SequenceNumber=38414&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MinHops=2&MaxHops=2&Root=http://shqbfbes01.na.sas.com%3A52311&AdapterInfo=00-05-9a-3c-7a-00_172.16.0.0%2F16_172.16.19.28_0&AdapterInfo=00-23-ae-90-7b-fd_192.168.1.0%2F24_192.168.1.5_0&AdapterIpv6=00-05-9a-3c-7a-00^fe80%3A%3Aa182%3A2835%3A380d%3Aa205%2F64_0&AdapterIpv6=00-23-ae-90-7b-fd^fe80%3A%3A1c6%3A5b09%3A2f1d%3Aaad%2F64_0

on my machine with no connectivity issues I get:

Success

5581252

18595

52311

8.0.584.0

0

19186

18896

No WakeOnLAN adapter selected

Machines in question are generally remote workers, but now always.

Thanks,

(imported comment written by snoczp91)

Machine in question returns:

“Invalid Sequence Number”

As does my machine now, which is properly synching with the BES server.