To clarify, clients inside on wifi, can get to OWA when using the internal IP. But not when using the url that resolves to the external IP.
The problem is that the clients device (In this case an iPhone 3g) must remain configured to attach to the external server hostname. But when in the building on wifi (instead of ATT Edge) it says unable to connect to server. This is an issue that like the individual i linked, we have tracked down to a lack of a specific routing rule that allows for this.
You see this rule implemented in most home routers but lacking in most corporate routers that do not come with some kind of prebuilt firewall rules managed by a caked over webgui.
Main Topics
Browse All Topics





by: hkunnanaPosted on 2009-11-03 at 12:45:07ID: 25733394
What I understood from your explaination is the following:
Clients inside your network (through Wifi) can connect to the url which has the IP address , but can't reach the same when it contains a name instead of IP.
If I understood right, then you have the following issue:
- your DNS resolves the ip of the "<companydomain>.com" to the external IP, and it seems you can't reach it for some reason.
So, the resolution can either be:
1- Allow the communication from your inside clients to the OWA via its external address.
or (which I prefer)
2- configure your local clients to use an internal DNS that translates the OWA address to its local IP.