Unable to Access UAG Login Page after Deployment

[Super6VCA]

Just trying to replace my security server with UAG 3.9.  After deployment i try to login to url Https://IPADDRESS:9443/admin and get "Cannot Connect to this Page".  IP is alive and well so not sure what the hold-up is.  Any help or suggestions are welcome. 

[a_p_]

Only a thought. When I did this last week, I used the Powershell method to deploy the UAG, and forgot to add the defaultGateway in the .ini file.
If you have a system in your DMZ (i.e. in the same subnet as the UAG management), try whether you can access the Login page from this system.

André

[Super6VCA]

I'm sure i put teh gateway in.  Used 10.0.90.1 for the public side and 90.1 for the gateway.  Do I need any static routes?

[sjesse]

Logon with the console and use the vami_config_net command to check the settings,usually for me its a typo somewhere

https://docs.vmware.com/en/Unified-Access-Gateway/3.2.1/com.vmware.uag-321-deploy-config.doc/GUID-53...

If you are not able to access the Admin UI login screen, check to see if the virtual machine has the IP address displayed during the installation of the OVA. If the IP address is not configured, use the VAMI command mentioned in the UI to reconfigure the NICs. Run the command as "cd /opt/vmware/share/vami" then the command "./vami_config_net".

[a_p_]

Assuming that the UAG has been deployed in a DMZ, can you confirm that port 9443 (TCP) is open for traffic from the system on which you try to access the UAG to the DMZ?

André

[a_p_]

Out of curiosity. Do you have a special reason why you deploy version 3.9 instead of the latest one (2009/2009.1)?

André

[Super6VCA]

This is located in the DMZ and it appears that 9443 is not accepting connections.

I am running 3.9 since that is what i had downloaded.  Still going to be running Horizon version 7.13 for a bit.  

[a_p_]

According to your previous question, you're still running a Security Server. Is this server in the same DMZ/subnet as the UAG's management? If so, please see whether you can access the UAG's login page from the Security Server.

André

[Super6VCA]

Not able to access from there either

[a_p_]

That's indeed unusual.
So the IP address shows up on the VM Summary page, and you can confirm that the IP address is unique, the subnet mask is correct, and the gateway has been configured too.

How did you do the deployment? By deploying the OVA manually, or using the Powershell method? In case of using Powershell, is there a chance that you compress/zip the .ini file, and attach it to a reply post?

André

[Super6VCA]

That is correct.  I used the Deployment Utility.  The IP is unique and once deployed i can ping it.  If i shut it down i cannot.  The IP shows up correctly in vCenter and the gateway is set to the DMZ Nic which is 90.1. 

[Super6VCA]

The only thing that i see odd in the config is the DNS server address.  I can input my DNS but it's a diff subnet than the DMS or the private address.  So it shows as a 127.0.0.53.   I tried to change it but still says 127... At this point i don't think that should matter since im using the IP address

[a_p_]

What makes me think is "Used 10.0.90.1 for the public side and 90.1 for the gateway." The same address for UAG, and gateway??
Can you please provide the IP settings that you have configured, i.e. IP address, subnet mask and default gateway address?

André

[Super6VCA]

[sjesse]

Whats your internal address, thats the one where the 9443 address should be.

[sjesse]

https://docs.vmware.com/en/Unified-Access-Gateway/3.9/com.vmware.uag-39-deploy-config.doc/GUID-FFC6B...

[Super6VCA]

The 10.0.10.99 is the internal and that one doesn't work either.  I tried that one.  Even changed the gateway to match that.  This is the video i watched prior to depoloying and looks like it's a 2 nic setup and the Gateway and IP used was the external.

https://www.youtube.com/watch?v=fbOtcCqbRYw 

[sjesse]

I'm pretty sure itshould be the internal one, look at the images I took from the video. Eth1 is the one he is accessing the admin interface with.  Its been a bit since I installed my last one I'll find my notes to be sure, but the kb I shared before says management should be on the internal one and the video is looking to be like it should be the internal one.

[sjesse]

Review some of these resources too, one of the videos has a graphic that shows the same

https://techzone.vmware.com/mastering-unified-access-gateway#deploy

[Super6VCA]

The way i follow it is that the the External IP (10.10.174.x) NIC is using the Gateway that he adds (10.10.174.254).  The internal  is on 172.16.x.x