Hello Everyone,
It is my normal practice to manually deploy non-windows clients. previously I’ve successfully deploy many non-windows clients in my BigFix infrastructure. Recently I tried to deploy an Agent to Red Hat Linux and to Mac Pc. I’m facing an strange problem that client has successfully installed and service is running in an endpoint, But client doesn’t appear in the console as it is supposed to. I checked the logs of both endpoint same error in the both logs that is :
At 03:31:03 -0700 -
Beginning Relay Select
RegisterOnce: Attempting secure registration with 'https://primarytem:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.2.0.363&Body=0&SequenceNumber=4&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://primarytem%3A52311&AdapterInfo=00-0c-29-62-1f-a1_128.1.0.0%2F24_128.1.0.168_0&AdapterIpv6=00-0c-29-62-1f-a1^fe80%3A%3A20c%3A29ff%3Afe62%3A1fa1%2F64_0’
At 03:31:08 -0700 -
RegisterOnce: GetURL failed - General transport failure. - winsock error -6 - registration url - http://primarytem:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.2.0.363&Body=0&SequenceNumber=4&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://primarytem%3A52311&AdapterInfo=00-0c-29-62-1f-a1_128.1.0.0%2F24_128.1.0.168_0&AdapterIpv6=00-0c-29-62-1f-a1^fe80%3A%3A20c%3A29ff%3Afe62%3A1fa1%2F64_0
Installer package that I’ve used is downloaded from here :
http://support.bigfix.com/bes/release/9.2/patch0/
Can anyone help please?
The GetURL failed error makes me wonder if the computers can successfully resolve the BES Server DNS name.
What happens if you try to ping the server by name?
ping by server name shows
Ping: unknown host
Did you setup your BigFix server with just a host name and not a fully qualified DNS entry? i.e. server or server.subdomain.domain.net?
yeah I just installed with a hostname.
It is primarytem:52311
Well if you don’t have a FQDN and your client can’t resolve the hostname then you need to resolve the resolution issue before you can continue.
You may have to add the IP of the BigFix server to the hosts file or figure out why your endpoint cant resolve the BigFix server.
well I’ve also tried editing the hosts file as well
Can you ping the IP address of the BigFix server?
Yes I can Ping to BigFix from IP address. And I’ve deployed several of non windows client manually to this server but never faced such kind of problem.
If you can ping the IP but not the hostname then there is an issue with hostname resolution and you should check the hosts file on the endpoint.
Yeah adding the IP and host name of both (server and client) works. But I don’t think that this is the solution.
Well Thanks for your interest.
Adding to the hosts file is probably never really the desired solution but in this case people have been asking you to try it to see if it connects. Since you have stated that it does, then you need to figure out why the system is not using DNS correctly. It sounds like other systems you have worked with have a properly configured DNS. Check the resolv.conf and see what is there. Also are your clients and bigfix server in the same domain? Maybe it has a different domain than other systems. For example abc.com and def.com.
From all the replied above, this is not a bigfix issue but a configuration issue on your client systems.