to route all internal traffic through UAG as if the connection was external to the network
It depends on what you mean with the above. It is not supported to use UAG as a forward proxy by using the underlying TMG's functionality. If your leaves the internal network through another proxy/firewall/egress then it is supported. I would ask myself why you do this but that is another discussion.
If it doesn't work either internally (through internal namespace?) or externally then you have configuration issue.
Review this article and see if you can resolve it.
Thanks for your reply. The underlying setup is the following and this should clarify things a bit:
UAG is load balancing SharePoint farm.
Internal DNS is the same as the Public DNS to access SharePoint. (For example sp.domain.com)
At this point Office Web Apps works normally for both internal and external users.
Since we want users to experience the same login steps, the following was done:
A DNS record was created internally, so that sp.domain.com resolves to the public IP of the UAG. This way everyone is going through the UAG for access regardless if they are internal or external users. This is when we started having issues. It seems that there is a loop somewhere when office web apps tries to send the document back to SharePoint.
- Edited by Vader86 1 hour 18 minutes ago
Thanks for your reply. The underlying setup is the following and this should clarify things a bit:
UAG is load balancing SharePoint farm.
Internal DNS is the same as the Public DNS to access SharePoint. (For example sp.domain.com)
At this point Office Web Apps works normally for both internal and external users.
Since we want users to experience the same login steps, the following was done:
A DNS record was created internally, so that sp.domain.com resolves to the public IP of the UAG. This way everyone is going through the UAG for access regardless if they are internal or external users. This is when we started having issues. It seems that there is a loop somewhere when office web apps tries to send the document back to SharePoint.
- Edited by Vader86 Tuesday, January 14, 2014 10:31 AM
Thanks for your reply. The underlying setup is the following and this should clarify things a bit:
UAG is load balancing SharePoint farm.
Internal DNS is the same as the Public DNS to access SharePoint. (For example sp.domain.com)
At this point Office Web Apps works normally for both internal and external users.
Since we want users to experience the same login steps, the following was done:
A DNS record was created internally, so that sp.domain.com resolves to the public IP of the UAG. This way everyone is going through the UAG for access regardless if they are internal or external users. This is when we started having issues. It seems that there is a loop somewhere when office web apps tries to send the document back to SharePoint.
- Edited by Vader86 Tuesday, January 14, 2014 10:31 AM