Any EPiServer support team can take a look of this issue? 

If you want to have support to look at an issue, then just open a source case. Support might look at the forums from time to time but you can't expect an action by just adding a forum thread.

Geolocation works by passing the IP address from your browser through to the server (where your EPiServer instance is hosted). The IP address is then checked against the geolit.dat database for a match. I'm pretty certain that IP address values will be the key to solving this.

1. Is this problem happening on your local development environment or a production server?
2. If its on your local machine have you tried something like this (http://www.david-tec.com/2011/06/Using-the-IIS-rewrite-module-to-test-EPiServer-geo-IP-look-up-personalisation/)
3. If its on production, have you tried logging the IP address that the server receives in each case (HK and AUS) (IIS should allow you do do this - the IP is passed in the request headers)

Hi Mark

Thanks for your suggestion and qucik reply.

My test is done through our staging server which is hosted in Australia. I will ask our administrator to help me check the incoming ip address tomorrow as I can't login to that box.

The reason I think it is a bug of episerver because HK vistor group works fine as I mentioned eariler, since I switched to a HK proxy server in the browser and open the staging site, I can see the HK content, however if I turn off the proxy, I suppose to see AUS content, surpisingly both visitor group contents are disappeared. 

There is another issue I addressed in my original thread, I am not too sure it's the episerver bug or I didn't use it properbly. 

As I mentioned in the first thread, rather than spending too much time reflector the code to figure out what's going wrong, I tried to use the fallback feature to make my work done quickly. I set the fallback personalization group within HK vistor group, the fallback value is set to the AUS visitor group. Unfortunately, it didn't work either.

Hi Linus

Thanks for your suggestion, I tried last time, however it took me a week to get the first response back, I am afraid I can't be that patient this time.

I put my question here is expecting to get help from both community and episerver team, I think it will be much faster than open the case, and also if the problem can be resolved here, it will help other community members isn't it?

No problem,

Here's my guess. It's network configuration, when looking at your internal staging server, your machine is passing through an internal IP address which isn't found in the geolite dtabase (as its internal) so you never match in the AU group. When you are on VPN you are routed externally and so the correct HK IP address is passed.