Bigfix Client connection via VPN

Hello Guys,

we have a bigfix client in DMZ zone and supposed to connect to the relay but the client wont give us a public IP to configure the DMZ Architecture, so we end up having a site-to-site VPN configuration. But the result is still Bad Server Name in the client logs

I believe site-to-site vpn configuration is like we are on the same page.

The exact error message from the client logs would be helpful, but it sounds like your machine cannot resolve the hostname of any of the Relays; or has never connected, doesn’t have a relay list, and cannot resolve the root server’s name.

Try manually adding a client setting _BESClient_RelaySelect_FailoverRelayList with a (resolvable) hostname or IP address of the relay to which the client should connect.

1 Like

About Client report or sync , you should care about your dns resolve .
You can try to use nslookup ,understand which dns server resolve dns name.
You also can check the dns name in actionsite.afxm , client use http url to report and sync.

1 Like

Good morning everyone, I would love to close this case I have resolved the concern last night.
As the FQDNS of Bigfix server should be resolvable to the clients that is why created a DNS for Bigfix and it went well.

Thank you and stay negative.

1 Like

@Pogi Posts here are community driven. We do have an official “support” case portal for things that you want to raise with the support team and track to closure. support.bigfix.com will get you there.

Glad the issue is resolved with creation of the DNS. Thanks for updating so nobody else spends time trying to resolve with you.

Stay negative is an interesting tag line. Are you a photographer or a diver? :smiley: