GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290

Usage and Config Platform
1

Hello Folks,

I have few servers which are on different subnet, when I deployed client on them following error occurs.

RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://BigfixServer:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.6.63&Body=0&SequenceNumber=172097&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://BigfixServer%3A52311&AdapterInfo=00-50-56-81-41-1a_IPAddress%2F23_IPAddress_0&AdapterIpv6=00-50-56-81-41-1a^fe80%3A%3A9dd0%3Ac51%3A15cf%3A3575%2F64_0
At 00:02:44 -0400 -

Telnet is happening , but when i do nslookup it is not able to resolve the DNS as well as the IP.

Also when i try to ping my bigfix server from problematic client i am getting RTO.

Any leads how i can take it further?

P.S : Bigfix Server is in different domain and clients are in different domain DMZ.

Thank You
Mayank

2

You answered your own question, if you can’t resolve or reach the BES or a Relay, then it won’t connect.

Is the issue DNS where it cannot resolve the FQDN? Can you ping by IP?

To test firewall connectivity, from any client to the BES or Relay, enter the following in a browser. It should immediately return the version of your relay:

http://BES-or-Relay.FQDN-or-IP.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=Version

If not, then you have an infrastructure issue. You need to place a relay in the DMZ/Cloud with ports open for the clients to reach it. Maybe include a clientsettings.cfg file with the BF Client installer so that you are pointing to a reachable relay instead of the default BES.

Example of a clientsettings.cfg file*:
__RelayServer1=http://DMZ-Relay.FQDN-or-IP.com:52311/bfmirror/downloads/
__RelayServer2=http://10.23.1.3:52311/bfmirror/downloads/
_BESClient_RelaySelect_FailoverRelay=http://DMZ-Relay.FQDN-or-IP.com:52311/bfmirror/downloads/
__RelaySelect_Automatic=0

In addition, Domain (Windows) and Telnet, have nothing to do with BigFix in your example.

*Assumes that after an initial connection is made that a Policy exists to set relay selection to automatic.

2 Likes
3

@Mayank As the communication in bigfix happens only on Hostname and not on IP adress. Thus you need to check if your DNS is getting resolved or no.
Are you using the same config file which is been used for the internal clients for client installation ?

4

Thank You Alexa.

Resolved by creating manual host entry on the agent machine. Alternatively one create a DNS record with other domains within an organisation.

5

Is it correct that bigfix doesn’t work with IP Address?

6

You may find it helpful to use the option, BES Relay Setting: Name Override (ID 155). The clients will then use the IP address of the relay instead of the FQDN. There are pros and cons to each.

1 Like
7

Yes that’s a good option but for that you need an active endpoint reporting to bigfix :slight_smile:

8

Yes the communication in Bigfix happens only on the hostname, and i am talking the communication. Thats the reason we always put the hostname in the configuration file.

Eg: The IP address of the main IBM BigFix server can be changed you wont find any issue, but if the hostname is changed there will be communication issue for the clients.

9

No that is not true , the communication can also happen with IP address.

If your organisation doesn’t have any future plans to change the IP addresses/Subnet/Vlans in that case you can request a license with IP address as well and if you have taken license against FQDN then only you are using hostname in the config file.

Hope that helps

10

ok thanks i might have missed that part!!! :grinning: