Hi,
Lot of client machines (windows 7) are showing / value in Distance to BES Relay column, and report directly to the Primary Server, instead of the relay servers defined in the seek list. Due to this Relay affiliation is not happening and primary server is getting too much clients to handle.
Please suggest the possible solution for this issue.
Regards,
Gautam Roy.
The distance missing can be related to many things, but the answer is basically the same in that the ICMP message to the relay didn’t give you back any information.
This could be because your environment has ICMP blocked, the endpoint is behind a NAT or other IP translator or several other causes.
If you want to prevent the systems defaulting to the Primary Server, you might consider configuring one or more Fail over Relays.
Hi Alan,
Thanks for the reply. Please help with the following queries in my case.
Is there any way in BigFix to determine if the ICMP is blocked on the client machines ?
Does the machines with ICMP blocked report to Primary Server instead of the relay defined in seek list ? We are not using any failover relay in our environment.
What would be the resolution to fix the machines with ICMP blocked ?
In our environment Fixlet ID 137 : BES Client Cannot Find a nearby BES Relay because ICMP is blocked showing around 3000 machines but some of those goes (around 1000) to their assigned relay with some value in Distance to BES Relay and most of the machines (around 2000) to Primary Server with unknown value in Distance to BES Relay. So, we are confused if the ICMP blockage on the machines could restrict the machines to select their assigned relays.
We are also tried with Relay Selection Control action on the machines with UNKNOWN value in Distance, (putting the value 5-20 in MAX TTL to Ping) to the machines. Some of the machines are fixed and can connect to their assigned relays according to Seek List, but again most of the machines still report to Primary Server (although their Max TTL to Ping value has been set to 5-20) with still UNKNOWN value in Distance to BES Relay properties.
Please suggest. Thanks in advance.
Hi Tim,
Thanks for the reply. We have not configured failover relay in our environment yet. Ideally machines should report to as per Seek List. But all the machines with Unknown value (almost 3000 in no.) in “Distance to BES Relay” properties report to Primary Server directly. Please suggest any workaround so that machines not report to Primary server.
ICMP being blocked is usually a networking issue so the endpoint doesn’t know other than it gets no replies back from ICMP messages.
If you have clients set to automatically find relays then ICMP has to work or they will fail over to the lists or the root server.
If ICMP is blocked in your network then you can use Manual relay settings.
Thanks for the reply. In our console the task id 137 ‘BES Clients cannot find a nearby Relay because of ICMP is blocked’ showing 4000/26000 in ‘Applicable Computer Count’ column.
What does that means ? Is this task report is reliable? Does it affect the client machine to select the nearby relays or relays according to the Seek List?
Please suggest so that we can move ahead in right direction to implement the Relay Affiliation in our environment. Almost 4000 machines are reporting to the Primary IEM Servers and relay selection method set on the client machines are Automatic.