RegisterOnce Fail when deploying new clients "Behind" Relay

Usage and Config Platform
1

(imported topic written by ken@gracenote91)

I have a dev network that has a bastion host (windows) acting as a router.

I installed BigFix Client and Relay (v 8) on the “router”. That went fine. The BigFix Server on my production network can see it.

I copied the client installer (V8) to a share on that “router” and then consoled into a server (TestExchangeServer) on the dev network. I was able to see that share on the “router” and install the client on TestExchangeServer.

However, when I look in the client log on TestExchangeServer. I see

t 17:12:04 -0700 -
RegisterOnce: Attempting to register with 'http://bigfix.gracenote.gracenote.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=8.0.584.0&Body=0&SequenceNumber=3&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://bigfix.gracenote.gracenote.com%3A52311&AdapterInfo=02-50-56-b3-49-0d_169.254.0.0%2F16_169.254.2.69_0&AdapterInfo=00-50-56-b3-49-0d_10.10.10.0%2F24_10.10.10.20_0&AdapterIpv6=02-50-56-b3-49-0d^fe80%3A%3A44aa%3A3367%3A28c2%3A291f%2F64_0’
At 17:12:28 -0700 -
RegisterOnce: GetURL failed - General transport failure. - winsock error -6

Clearly, the new client is trying to “RegisterOnce” with the server BigFix Server - which it (intentionally) can not see from a routing perspective.

I was hoping that it was going to “registeronce” with the relay.

Is BigFix designed to work that way? What do I need to do to make it so ?

TIA

Ken

2

(imported comment written by Lee Wei)

Ken,

Yes, you are seeing the correct behavior.

By default, the new Client has to contact the BigFix Server once to download the list of relays.

However, in the case such as yours where the Client does not have access to the BigFix Server, you can assign the Relay upon install.

Here is the KB article describing the steps to do that.

Basically, you provide a file clientsettings.cfg in the Client installation directory.

The fill will contain a line such as:

Relay IP=http://your_router_relay:52311/bfmirror/downloads

Lee Wei

3

(imported comment written by ken@gracenote91)

Lee Wei

Ken,

Yes, you are seeing the correct behavior.
By default, the new Client has to contact the BigFix Server once to download the list of relays.

However, in the case such as yours where the Client does not have access to the BigFix Server, you can assign the Relay upon install.

Here is the KB article describing the steps to do that.
Basically, you provide a file clientsettings.cfg in the Client installation directory.
The fill will contain a line such as:
Relay IP=http://your_router_relay:52311/bfmirror/downloads

Lee Wei

cool… will give it a shot now

4

(imported comment written by ken@gracenote91)

ken@gracenote

{quote:title=Lee Wei}Ken,

Yes, you are seeing the correct behavior.
By default, the new Client has to contact the BigFix Server once to download the list of relays.

However, in the case such as yours where the Client does not have access to the BigFix Server, you can assign the Relay upon install.

Here is the KB article describing the steps to do that.
Basically, you provide a file clientsettings.cfg in the Client installation directory.
The fill will contain a line such as:
Relay IP=http://your_router_relay:52311/bfmirror/downloads

Lee Wei

cool… will give it a shot now{quote}

NOPE… no luck.

I copied the client install folder down to the local computer (in the dev network)

I added a folder called clientsettings.cfg with the only content being:

http://evl-router-dev.exdev.gracenote.com:52311/bfmirror/downloads

I uninstalled the previous installed agent and even deleted the BigFix Enterprise folder manually

I click on the installer… it completes… but then I go into the log file and I just see that it is still trying to go to the bigfix server and it is failing registeronce.

I check under actionsite and there is no relays.dat file… not sure if there is supposed to be one with V8

advice ?

5

(imported comment written by Lee Wei)

Sorry, I meant to include the KB article link in my earlier post:

http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244

I spot 2 issues:

  • The clientsettings.cfg is a file, not a folder. It should be added in the Client installer folder.
  • The single line should start with Relay IP=http://…

Please double-check with the info in the article.

6

(imported comment written by ken@gracenote91)

Lee Wei

Sorry, I meant to include the KB article link in my earlier post:
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244

I spot 2 issues:

The clientsettings.cfg is a file, not a folder. It should be added in the Client installer folder.

The single line should start with Relay IP=http://…

Please double-check with the info in the article.

naw… that is just my error in typing in the forum…

HEre I will cut and paste:

It is a text file, not a folder: clientsettings.cfg

here is the contents:

Relay IP=http://evl-router-dev.exdev.gracenote.com:52311/bfmirror/downloads

BTW… I notice that when I open IE and past in http://evl-router-dev.exdev.gracenote.com:52311/bfmirror/downloads I get an error message back from IE saying

Network Access Message: The page cannot be displayed

Explanation: There is a problem with the page you are trying to reach and it cannot be displayed.

Try the following:
Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion.
Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped.
Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.
If you are still not able to view the requested page, try contacting your administrator or Helpdesk.

Technical Information (for support personnel)
Error Code: 502 Proxy Error. Forefront TMG denied the specified Uniform Resource Locator (URL). (12202)
IP Address: 10.10.10.2
Date: 8/18/2010 1:52:24 AM GMT
Server: EVL-ISA01-DEV.exdev.gracenote.com
Source: proxy

Looks like the Exchange guy has this running thru an ISA server…