Fix the failing Locator on the startup in GemFire

This fix is applicable for GemFire 6.x and 7.x.
If your terminal or command prompt fails while starting the locator for the first time in Network Discovery
Symptoms :

• When you start VMware vFabric GemFire, the locator connection begins, but fails after discovery.
• Connection can fail with cache servers, but is typically observed with locators first.

Cause :

• This occurs when UDP is blocked (such as by Windows Firewall), which vFabric GemFire uses to communicate between peer members, such as cache servers and locators.
• Since the initial connection for locator discovery is made via TCP, a firewall rule set that allows TCP, but prohibits UDP connections, allows the initial discovery while blocking the member-to-member connection.

Resolution :
To resolve this issue, allow the necessary UDP traffic.
To do so:

• Remove the firewall rule that blocks UDP traffic
  or
• Set “membership-port-range” in the gemfire.properties file to restrict the port range used for membership communication.

Not sure how to Allow / Deny the ports in Windows firewall ?
http://technet.microsoft.com/en-us/library/cc947789%28v=ws.10%29.aspx
in RedHat Enterprise Linux ?
http://www.techotopia.com/index.php/Basic_RHEL_5_Firewall_Configuration
Write to me if you get struck