Forum Discussion

jasonmiles_2057's avatar
jasonmiles_2057
Icon for Nimbostratus rankNimbostratus
Sep 03, 2015

Big-IP LTM - VMware View - HTTP Error 404 - Object not found

I have deployed 2 F5 Big-IP LTM appliances and added the iApp template for VMware Horizon View (f5.vmware_view) and configure the Application Service for Horizon View following the Deployment Guide v17. We are not using Security Servers from VMware. Only direct connection is required. No tunnelling, or SSL offloading required.

 

However, when opening the Horizon View Client and attempting to access the single URL Namespace (mydesktop.customerdomain.com) -- the following error occurs: VMware Horizon Client - Error: HTTP error 404

 

And secondly, when navigating to the URL (mydesktop.customerdomain.com) shows the following result Object not found! The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again. Error 404

 

Accessing VMware Horizon View Connection Servers directly is OK when going direct to server name.

 

Inside the F5, the nodes for Horizon View - View Connection Severs show as available.

 

Any tips or pointersf or next step troubleshooting?

 

APM
application delivery
availability
devops
iApps
iRules
performance
security

2 Replies

Sort By
  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account
    Sep 03, 2015

    Couple troubleshooting thoughts:

     

    Try accessing the virtual server address to see if you have a response (you will have cert warnings, but this is just a connection test). If you have a response, then verify your DNS is setup correctly. If you do not see a response then verify ports 443/4172 are available from the horizon client to the BIG-IP virtual server address. Tcpdump/capture would be useful on the big-ip/client to verify connection requests are making it to the BIG-IP. If the request is making it to the BIG-IP VS address, then check out the server side also using tcpdump/capture to verify the horizon client request was properly proxied to server. You should see the server response going back to the big-ip, if not then verify the virtual servers snat setting is setup correctly. If your servers are not using the big-ip as a gateway, then you should have snat setup to automap or pool. If you are using automap, verify you have a self-ip address on the network in which the pool members reside. If using a pool, then verify the ip address pool is on the same network as your pool members.

     

    • Greg_Crosby_319's avatar
      Greg_Crosby_319
      Historic F5 Account
      Sep 03, 2015
      A little more information/correction: The snat ip address does not have to be on the same network as your connection servers, but the big ip needs to have a known route from the snat network to the connection server network.