Question Cannot access Forefront UAG portal

  • Sunday, March 17, 2013 1:18 PM
     
     

    I've just setup test a Forefront UAG SP3 portal and each time I try to access it from an external address I get nothing at all.

    I've made sure on Internal - No default gateway, DNS servers entered, Client for MS networks enabled, F&P Sharing enabled, Enable LMHosts lookup disabled and NetBIOS over TCP/IP- default.

    Also external NIC default gateway is defined, DNS servers not defined, Client for MS networks disabled, F&P Sharing disabled, Enable LMHosts lookup disabled and NetBIOS over TCP/IP- disabled.

    Test network is {CISCO Router} X.X.X.49 with a range of X.X.X.50 to X.X.X.54 usable IP's, this is plugged directly into switch (with no routing capabilities) the Forefront UAG is into the same switch and this has X.X.X.53 and 54 assigned to the external card with 192.168.3.1 on the internal card, which is then connected to another switch for the internal test network.

    Certificate has been assigned and portal setup which is browse able both from the internal test network and if I configure a PC with one of our external IP addresses assigned to the Cisco router i.e. X.X.X.52 and plug this into the switch between the Cisco and the UAG server.

    To me everything is configured properly but there seems to be no external access at all??

All Replies

  • Sunday, March 24, 2013 9:46 PM
    Moderator
     
     
    One of the main issues that i faced after the installation of the UAG 2010 SP3 was that all my users were unable to access the UAG Portal page or any published site on the UAG (Mail OWA, SharePoint............etc) and the following error is Displayed:

    Forbidden Directory, Listing Denied Error code 403.14

    Microsoft has a good KB that deals with this error (http://support.microsoft.com/kb/961172) however in my case i needed to reboot the IIS later on. The Steps done to fix this issue is as follows:


    1. Open Forefront UAG management on the UAG server.
    2. Open/Explore the Trunks under the HTTP and/or HTTPS connections.
    3. Right click each Trunk and select Disable.
    4. Save and Activate the UAG configuration.
    5. Right Click the trunks again and select enable.
    6. Save and Activate the Configuration again.
    7. Open the IIS Manager
    8. Highlight your server name and from the actions hit restart to restart the IIS. This should do the trick.

    Hopefully this should help anyone facing this problem after UAG SP3.